translation pattern based on partition, even with extension mobility

[thomascollins]

Hello,

Running CUCM 10.5.2, with Informacast.  We have 10 sites, each with a unique extension for overhead paging.  Let's say 2001, 2002, 2003.  

Our end users would like to use a single number for overhead paging.  Let's say 2000.  So I was thinking we could use a translation pattern in the CSS for that site.  So 2000 would translate to 2001 at site 1, translate to 2002 at site 2, etc. 

But our end users use extension mobility.  So they may log into a device at any site.  If we pre-program one of their buttons to be a speed dial to 2000, will it still use the correct translation pattern for that site (based on the physical phone CSS)

Thanks!

[Chris Deren · Accepted solution]

It depends on how your CSSes are setup.  If you have CSS only on device (phone user logs onto) then when user logs onto another site 2000 will point to the local paging. If the CSS is assigned to line then it will always go to home location. If the CSS is on both device and line then it depends on what partitions both of them have access, if both have access to 2000 in different partitions then the line setting will take precedence.

[thomascollins]

Thanks guys, perfect explanation.  +5.

[Vivek Batra · Accepted solution]

Since line CSS checks first before device CSS, you might prefer assigning desired CSS to line instead of device.

Now even if you don't use speed dial button, each site user can have access to their specific partition (/translation pattern) for dialing 2000.

If you use button as speed dial to dial 2000, again you need to ensure line CSS can see the desired translation pattern. Also ensure that since button template is assigned to Device, each device which end user is logging to has access to that phone button template.

- Vivek