EasyUC
4.8.7

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.

EasyUC · Version 4.8.7

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 cucm and an active CUCM connection.
  • Role ROLE_APP_VIEW_ENDUSER_PROFILE_RD for the tab, ROLE_APP_CREATE_RD for Create, ROLE_APP_UPDATE_RD and ROLE_APP_DELETE_RD for 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

  1. First create the softphone for iPhone or Android if it is still missing. You do this in the profile on the Phones & Phone numbers tab through Create and the Soft Phones card.
  2. In the profile, switch to the Single Number Reach tab.
  3. Click Create and select Mobile Identity.
  4. In the Create Mobile Identity dialog, check the Mobile Number. EasyUC prefills it with the mobile number of the user.
  5. Select the Location and then the Package.
  6. Select the Template. With Template 2.0 this selection is omitted.
  7. Under Device, select the dual-mode device of the user.
  8. Set Delay Before Ring, Answer to Soon Timer and Answer to Late Timer.
  9. In the Ring Schedule section, define when the mobile number rings in parallel, or leave All The Time ticked.
  10. Click Save. The card shows an entry Mobile Identity with destination, device and lines.

Step by step: Create a template in the proven template model

  1. Open EasyUC Cisco → Templates → Mobile Identity. The menu item appears only in the proven template model.
  2. Click Create NEW Mobile Identity Template.
  3. In the list, select an existing Mobile Identity from CUCM as a pattern and create the template from it.
  4. Assign the template to location and package, as with other templates.
  5. Use Out Of Version Templates to check whether templates need to be renewed after a CUCM upgrade.

Fields and options

Fields and options
Field / actionMeaning and use
Mobile NumberMobile number of the Mobile Identity. Mandatory field. Prefilled with the mobile number of the user.
Location / PackageDetermine the template or the Template 2.0 section. Location is mandatory.
TemplateTemplate of type Mobile Identity. Only in the proven template model.
DeviceDual-mode device of the user (iPhone or Android). Mandatory field. Devices that already have a Mobile Identity are missing from the list.
Delay Before RingSeconds until ringing over the mobile network starts. Default 4.0.
Answer to Soon TimerProtection against the mobile voicemail. Default 1.5.
Answer to Late TimerMaximum ring duration over the mobile network. Default 19.0.
Ring ScheduleAll The Time or weekdays with All Day or Start Time and End Time, plus Timezone.
recommendedNote at the menu entry when the user has a dual-mode device for iPhone or Android.
MI Template / DeviceDefaults 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.

Related chapters