Topic Last Modified: 2010-11-07
If you provide branch-site resiliency, if a branch site’s WAN connection to a central site fails or if the central site is unreachable, the following voice features should continue to be available:
- Inbound and outbound PSTN calls
- Enterprise calls between users at both the same site and
between two different sites
- Basic call handling, including call hold, retrieval, and
transfer
- Two-party instant messaging
- Call forwarding, simultaneous ringing of endpoints, call
delegation, and team call services, but only if the delegator and
delegate (for example, a boss and the boss’s administrator), or all
team members, are configured at the same site
- Call detail records (CDRs)
- PSTN dial-in conferencing with Conferencing Auto-Attendant
- Voice mail capabilities, if you configure voice mail rerouting
settings. (For details, see Branch-Site Resiliency
Requirements.)
- User authentication and authorization
The following features will be available only if your resiliency solution is a full-scale Microsoft Lync Server 2010 deployment at the branch site:
- IM, web and A/V conferencing
- Presence and DND-based routing
- Updating call forwarding settings
- Response Group service and Call Park
- Provisioning new phones and clients, but only if Active
Directory Domain Services (AD DS) is present at the branch
site.
- Enhanced 9-1-1 (E9-1-1)
If E9-1-1 is deployed, and the SIP trunk at the central site is not available because the WAN link is down, then the Survivable Branch Appliance will route E9-1-1 calls to the local branch gateway. To enable this feature, branch-site users’ voice policies should route calls to the local gateway in the event of WAN failure.