Local Route Group

• Decouple the selection of the PSTN gateway from the route pattern used to access the gateway
• It can affects the whole dial plan, including features components such as AAR, CFUR, TEHO and partitions and CSS
• It reduces the complexity in the following scenario
  • Tail End Hop Off
  • Global Transformation
  • Automated Alternate Routing (AAR)
  • Call Forward Unregistered
  • Calling Search Space
  • Global Emergency Number Dialing
• For forwarded or redirected call, Cisco Unified Communications Manager uses the Local Route Group that is provisioned in the device pool settings that are associated with the redirected party to find the provisioned local route group. i.e. the originating party.
• Many supplementary services can originate calls. When this happens, the local route group gets skipped.
  • CallBack
  • MWI
  • Mobility (FollowMe)
  • Path Replacement

<note>The Device Mobility feature allows the device pool to be assigned to an endpoint based on the current subnet to which it has roamed. This permits assignment of the local route group to be based on the site where the phone is currently located.</note>

• Under the Route Pattern for our PSTN
• Add “Standard Local Route Group” to route lists

• Configure local gateway and add gateway to local route group
• Configure device pools with local route groups

• Assign device pool to devices