Logical Partitioning/Geolocation and Device Mobility

[James Hawkins]

Hello,

I have a customer with a CUCM 8.6 cluster that supports a number of countries including India.

They have the Logical Partitioing feature enabled to make the system comply with Indian regulations for telecoms that forbid toll bypass etc.

They have now started using Jabber for Windows and have a number of users who are based in India but often travel to other countries.

When they do this they are not allowed to use voice gateways in the country they are visiting to place calls because of the geolocation configuration applied to their Jabber CSF device.

In CUCM 8.6 the geolocation seems fixed to the device (or device pool) and cannot be updated using the Device Mobility feature.

Is this feature supported/roadmapped for any later versions of CUCM? (or is there a reason why this would not be possible?)

[Muhammad Al-Hussein]

Hello James,

I hope You are doing well, probably You have found the answer by now, but, I just saw that your post is not answered, so wanted to answer to it :-)

Although they are not specified under Roaming Sensitive Settings, but Geo-locations are inherited from the Roaming/Visiting DP (if Physical Location is changed regardless they are in the same DMG Group or not), we deployed a similar setup in our network and it is working as mentioned, also, please find the following Cisco Reference:
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/10_0_1/ccmfeat/CUCM_BK_F3AC1C0F_00_cucm-features-services-guide-100/CUCM_BK_F3AC1C0F_00_cucm-features-services-guide-100_chapter_011100.html#CUCM_RF_G3E1AF2D_00

Source of Geolocation Information

The following logic determines the geolocation value:

1. Read the value for geolocation from the device window. If it is not configured on device page, for phone device in roaming, read the device pool (DP) from the roaming configuration. For phone device that is not in roaming, read the DP from the device configuration.

2. For trunk, ICT, or MGCP port device, read the DP from the device configuration.

3. From the selected DP, read the value of geolocation from DP configuration window.

4. If DP is not configured with a value for Geolocation, use blank value.

5. If available geolocation value is blank, call processing uses the configured value that the Default Geolocation enterprise parameter specifies.

Thanks and Best Regards,

Muhammad Al-Hussein