Extension mobility and Local Route Group

[fran19422]

In a centralized CUCM topology, if a user travels to another city location and uses Extension Mobliity to log in to a phone there, would his calls use the Local Route Group of his original phone (home city) or that of the currently accessed phone ?

I am thinking of the problems that might incur if he made an emergency call at this foreign city location, and the dial pattern referred back to the Local Route Group egress gateway of his original phone (in his home city) rather than that of his current location's phone. You may have emergency services turn up to the wrong location.

Thanks for any insight.

[Jagpreet Barmi · Accepted solution]

Hi,

If you dial plan is configured with Local Route group, the calls will be routed through the route group configured under Local route group in a Device Pool.

Users log into Extension Mobility using User Device Profile and there is no option to configure device pool for the user device profile. The Device pool is selected from the base phone (Phone and not the profile) to which the user logs in.

With correct configuration, the call would be routed through the local gateway where the phone is registered/located (the current location).

HTH,

Jagpreet Singh Barmi

[jugalkansal90]

Hi Jagpreet,
What about user's ext phone number mask, if line settings will remain the same from user's original location, PRI at new location won't send that number out. Is there any workaround for that instead of updating the ext phone number mask manually?

[TONY SMITH]

That depends on what you want to achieve.  If your PRIs won't accept calling number out side their own range, then you could add a voice translation rule on each gateway to convert any unrecognised numbers into your preferred CLI.