We would like to see a system option added to Additional Features > EMCC > EMCC Feature Configuration ... or ... Extension Mobility Service Parameters ... or ... CallManager Service Parameters ...
To permit the same kind of Adjunct CSS + Line CSS + [Device Profille] EMCC CSS construction, using Geolocation data from the Device, to locate a matching Device Pool for the above settings ... when an EM Device Profile is logged-in at the Home Cluster ... in the same way that EMCC constructs CSS today when an EM Device Profile is logged in from a Remote Cluster.
We have a legacy "PSTN" calling restriction standard that carries forward "8" (0-7) "Class of Restriction" levels (sometimes called "Facility Restriction Levels") and, outside of Extension Mobility, we are able to use a "Line/Device" Calling Search Space approach to much more efficiently manage our CSS(es): PSTN restrictions (Block Patterns) in the Line CSS combined with client-based, "abbreviated" dial plans. Approaching ~100 internal divisions / clients in the Device CSS(es).
We have the capability to use EAN and E164 long-form dialing to permit Global OnNet dialing, but our scale and divisional structure requires us to provide and maintain a large number of (4-5-digit) client-internal dial plans.
The original Extension Mobility feature "breaks" that Line/Device CSS model by utilizing the Line CSS from the logged-in user profile, and the "Device" CSS from the underlying physical device, wherever that phone happens to be.
Extension Mobility Cross Cluster has an existing mechanism to specify "EMCC Calling Search Space" on the User Device Profile, which is essential for the Home Cluster to have when a device from a Remote Cluster registers to it.
That combined "Adjunct/Line/EMCC-CSS" construction works great for the matrix-CSS design described above: (A) 112/911/999 Emergency Call routing is tied to the Adjunct CSS and based on the Geolocation of the calling device, (B) Line CSS, contains "PSTN-level" blocking patterns depending on the User Device Profile's Line settings, and (C) EMCC-CSS at a lower priority level from Adjunct and Line permits the User to "bring" their department's "short" dial plan with them when they log into a "Remote" Cluster.
But this only works when logging in at a Remote Cluster.
If a user logs in at an alternate phone within their Home Cluster, EMCC passes the EM service login through to the legacy "EM" feature, which takes the Device CSS of the phone (which could be a completely different department dial plan) and mixes it with the logged-in User's Line CSS.
In the current environment, to provide the granularity needed in our CSS(es) will require on the order of 800 named CSS(es) to fully migrate our legacy POTS and PBX users over to Call Manager. (8x100)
It would be a huge help to bring the Adjunct+Line+EMCC CSS feature construction to "Local" Extension Mobility logins, as a system-level feature, andwould bring our CSS(es) down an order of magnitude to ~108. (8+100)
Also a benefit, as Geolocation features on Devices become more robust and 911 2.0 more prevalent, locating a matching Device Pool with its particular Emergency Location Group setting based on Geolocation data from the phone on the local cluster will add robustness to the Native Emergency Call Routing feature where EMCC is active.