EasyUC for Cisco
Mobile Identity for dual-mode devices
Bind the mobile number to Jabber on iPhone or Android so that calls also arrive over the mobile network.
In EasyUC: EasyUC Cisco → Users → Users → User profile → Single Number Reach → Create → Mobile Identity
What it is for
A Mobile Identity is the mobile number that is attached directly to a dual-mode device in CUCM. Dual-mode devices are Jabber or the Webex App on the iPhone (device type TCT) and on Android (device type BOT). This allows CUCM to also deliver calls to this number over the mobile network.
The difference from the Remote Destination: The Mobile Identity does not need its own Remote Destination Profile. It uses the lines of the dual-mode device. If a user has such a device, EasyUC therefore marks the Mobile Identity entry in the Create menu as recommended.
Timers and ring schedule work as with Single Number Reach.
Prerequisites
- License module
cucmand an active CUCM connection. - Role
ROLE_APP_VIEW_ENDUSER_PROFILE_RDfor the tab,ROLE_APP_CREATE_RDfor Create,ROLE_APP_UPDATE_RDandROLE_APP_DELETE_RDfor changes and deletion. - The user has a dual-mode device for iPhone or Android that does not carry a Mobile Identity yet. Only such devices are available for selection in the Device field.
- Proven template model: A template exists for location and package under Templates → Mobile Identity.
- Template 2.0: The Remote Destination & Mobility section is Active for the location. It applies to Remote Destination Profile and Mobile Identity together.
Step by step: Create a Mobile Identity
Step by step: Create a template in the proven template model
Fields and options
| Field / action | Meaning and use |
|---|---|
| Mobile Number | Mobile number of the Mobile Identity. Mandatory field. Prefilled with the mobile number of the user. |
| Location / Package | Determine the template or the Template 2.0 section. Location is mandatory. |
| Template | Template of type Mobile Identity. Only in the proven template model. |
| Device | Dual-mode device of the user (iPhone or Android). Mandatory field. Devices that already have a Mobile Identity are missing from the list. |
| Delay Before Ring | Seconds until ringing over the mobile network starts. Default 4.0. |
| Answer to Soon Timer | Protection against the mobile voicemail. Default 1.5. |
| Answer to Late Timer | Maximum ring duration over the mobile network. Default 19.0. |
| Ring Schedule | All The Time or weekdays with All Day or Start Time and End Time, plus Timezone. |
| recommended | Note at the menu entry when the user has a dual-mode device for iPhone or Android. |
| MI Template / Device | Defaults in the automatic user provisioning. There the Mobile Identity can be planned together with the softphones for iPhone or Android. |
Check the result and troubleshoot
- Success: The entry carries the abbreviation MI and shows the Destination, the Device and its Lines.
- The Device field is empty: The user has no dual-mode device for iPhone or Android, or every device already has a Mobile Identity.
- Save stays gray: Mobile Number, Location or Device is missing.
- “This feature is not configured or is disabled in Template 2.0 for the selected location. Please check the location configuration.” Activate Remote Destination & Mobility for the location.
- You change timers and schedule later through the menu with the three dots: Update Timers and Update Schedule. Delete removes the Mobile Identity.
- After the dual-mode device is deleted, the note recommended disappears as well.