Mobility and Single Number Reach – quick config instructions

Configuring a Single number reach in Cisco Call Manager

Getting your mobile phone to ring when your desk phone does is pretty easy, but before walking through it you should understand what makes this functionality work.

The common ground to all the phone numbers is a user account, we need a user account that is allowed to use mobility and is associated with the desk phone and the mobile phone, and this tells the system to link a desk phone to a mobile phone.

There can be more then one mobile phone per user, in fact you can have up to ten external phones per user and those phone numbers are made of a remote destination profile (one per user) and a remote destinations (up to ten per user, four by default).

The process of single number reach is as follows:

  1. A call comes in to the User's desk phone.
  2. The remote destination profile and the remote destinations are triggered.
  3. The phone numbers which are in the remote destinations are dialed.
  4. The user answers the call on his mobile phone.
  5. The call is bridged via Communication Manager for its entire duration.
  6. Optionally - the user comes in to the office and pick up the call from his desk phone.
  7. Optionally - the user selects the mobility soft key and sends the call to his mobile phone again.
  8. The user hangs up from his mobile phone, the call remains active for a few seconds more and then terminates (until the call terminates, anyone standing next to your desk phone can take the call, which is why you want to make sure the other side disconnected before you).

Now the config is a lot simpler to understand, first create a user (if it's not already there), associate her to a device and enable mobility:

Then associate the user to his directory number:

Now create a remote destination profile and assign it to the user's directory number.

Add remote destinations which are pointer to your mobile/home phone numbers.

Add the mobility soft key to the user's soft key template (no pic for this one ...). That should be it, when all this is done; the single number reach functionality should work.

 It's easy and does not require much, yet I don't see it being used a lot, not sure why. My assumption is that VAR's are reluctant to config it because it makes the deployment more time consuming and then the end users are not aware of this or prefer not to touch it because it's too complicated to config.

Hopefully this blog post will take some of the 'why not' reasons away.

Join the Network World communities on Facebook and LinkedIn to comment on topics that are top of mind.
Related:
Now read: Getting grounded in IoT