We want an option to be able to use concatenated Adjunct/Line/DeviceProfile CSS (alternatively just Line/DeviceProfile CSS) for Home Cluster Extension Mobility (EM).
Rather than the current EM concatenation of Line/Device CSS when an EM user is logged in at the device.
This already works with EMCC logging in at a Visiting cluster in the ILS network, but not at the Home cluster itself, where EMCC login is redirected to “legacy” EM function.
In other words, we want to use [optionallyAdjunct]/Line/DeviceProfile CSS — not Line/Device CSS — for Home cluster EM users so they route identically to an EMCC user logged in as a Visitor.
OR
A way to permit EMCC login to occur on the Home cluster without reverting to the legacy EM mode. Which would have similar impact.
The reason we want [Adjunct]/Line/DeviceProfile CSS is because our internal “abbreviated” dial plans do not conform to Physical Locations (where Device Mobility CSS could be utilized), but instead by Enterprise “Division” entities — and users from disparate org Divisions (thus disparate abbr dial plans) share and overlap in the same physical office spaces. Think Retail, Mortgage, and Credit Card divisions all with a presence in the same building (shared tenants), and replicated in the same building arrangements across multiple parts of the country. Each division has a (Device CSS) dial plan for short dialing within its Division, combined with a Line CSS for common format, long form PSTN dialing.
When a user “hotels” in a foreign (to them) space, they should be able to utilize their org’s short dialing while EM’d to the device. The underlying Device CSS won’t know, in current function, which short dial plan to use, which for our environment, the DeviceProfile CSS (“EMCC CSS”) is needed when EM is active.
In the past, Device CSS was thought to be needed to route emergency number calls to a local gateway (overriding any Line or Device Profile CSS in EM mode, but that is no longer necessary when using Local Route Groups to handle those emergency calls based on NECR or CER routing and physical location detection.
"Please provide additional information on what is the problem that this solves. For PSTN access from EM devices, there already is the LRG configuration which makes sure that the correct gateway, based on logged in device location, is used for PSTN access.
For assigning device pool based on location, we do that for EMCC login, but not for EM.. For EM, device pool/Emergency LRG is assigned based on the IP address of the logged in device, not the location. In general, not all devices support sending the location information"
The short answer is that our "abbreviated 5-digit" or AccessCode+ESN (internal dial plans) are unique on company "Divisions" not site/building location.
Think Retail, Mortgage, and Credit Card divisions all with a presence in the same site/building/ERL subnet so Device CSS is used to partition those dial plans (in a Line/Device CSS arrangement).
When a user is "hoteling", using Extension Mobility to sign into the phone, they are expecting their Department aligned abbreviated dial plan, not a site based one which would be triggered by either the underlying Device CSS or a Device Pool - Device Mobility determined Device CSS.
Device Profiles have an existing Device Profile CSS field ("Extension Mobility Cross Cluster CSS" but it is only in play when a user is EM logging into a Visiting Cluster.
We would like to see this work, or have an option to work) at the Home Cluster as well.
Attachments Open full size