Since the phone
configuration doesn't exist in HC, phone parameters will be obtained as follow:
- Common Device Configuration & Common Phone Profile - Bulk Administration => EMCC => EMCC Template
- Region settings (codec selection) - Advanced features => EMCC => EMCC Feature Configuration
- EMCC Region settings override normal region configuration
- All EMCC Region parameters MUST be configured with same values in ALL clusters. If they are different, RSVP Agent for that cluster will be disabled by Remote Cluster Update operation
- EMCC Roaming Device Pool - Determined via Geolocations & EMCC Geolocation Filter
- HC configures at least one Roaming DP per remote cluster. Each DP uses distinct geolocation characterizing that cluster
- Phones enabled for EMCC in VC must have be assigned a Geolocation at Device Pool or Phone Device level
- Login process sends phone’s Geolocation from VC to HC
- Phone’s Geolocation is filtered by ‘EMCC Geolocation Filter’ on HC (Advanced features => EMCC => EMCC Feature Configuration)
- Using filtered geolocation, HC finds the most suitable DP for roaming DP
- HC uses Roaming DP to build EMCC Phone configuration in database
- Phone Parameters (date-time group, Adjunct CSS, CUCM-Group, etc) - EMCC Roaming Device Pool
Note: If Roaming DP isn't
present in HC, VC Phone will inherit UDP DP configured in HC
No comments:
Post a Comment