[This is pre-release documentation and subject to change in future releases. This topic's current status is: Milestone-Ready]

Topic Last Modified: 2010-06-09

We recommend creating a separate voice over IP (VoIP) policy for users at branch sites. This policy should contain routes to egress from the Survivable Branch Appliance gateway or the Survivable Branch Server external gateway and backup routes to egress from a gateway at the central site. Regardless of where the user is registered, either on the Registrar on the Survivable Branch Appliance or Survivable Branch Server or on the backup Registrar cluster at the central site, the user’s VoIP policy is always in effect.

To configure the VoIP routing policy for branch users

  1. Create a user-level dial plan and assign it to branch users. (See Create a Dial Plan, in the Communications Server Control Panel Help.)

  2. Assign normalization rules corresponding to the dialing habits of users at that site. If the Survivable Branch Appliance or Survivable Branch Server user fails over to the backup Registrar pool at the central site, the same dial plan will be in effect. (See Create a Dial Plan, in the Communications Server Control Panel Help.)

  3. Configure a voice route that egresses from the the Survivable Branch Appliance gateway or the Survivable Branch Server external gateway. (See Create a Voice Route, in the Communications Server Control Panel Help.)

  4. Set a backup call route on the Survivable Branch Appliance or Survivable Branch Server gateway to point to the backup Registrar pool (collocated with Mediation Server) at the central site. (See your Survivable Branch Appliance or Survivable Branch Server vendor documentation.)

    Note:
    This backup call route setup helps ensure that inbound calls to the branch user will work when the Survivable Branch Appliance or Survivable Branch Server is not available (for example, if it is down for maintenance). If the Registrar and Mediation Server on the Survivable Branch Appliance or Survivable Branch Server are not available, and the user is registered with the backup Registrar pool at the central site, inbound calls can still be routed to the user.

Next step: Configure Voice Mail Rerouting Settings