Single Number Reach

[bulakeno]

Hi,

I have been working on Single Number Reach feature for a bit now and hasn't been able to make it work. I have a call Manager 6.1, using a device profile. Below is the procedure that I did.
1 - User management - end user - enable mobility and enable mobile vocie access checked
2 - Created a Remote Destination Profile - added my DN, added my cellphone as remote destination number, checked line association with my dn.
There no more steps needed according to the documentation.

When I try to call my extension, the CUCM does not dial the remote destination.

Anybody have this working ?

Thanks.

 

[HmmG3]

What did you select as the Rerouting CSS under the Remote Destination Profile? This is the CSS used to contact the cell phone number that you entered in the Remote Destination. If you entered your straight 10 digit cell phone number, then you'll need a translation pattern to adjust it to match your existing route patterns. We used a dedicated CSS and partition for this feature. The translation patterns were in the partition that took a cell phone number of 408-555-1234 and convert it to 9-555-1212 and assigns it a CSS of the local San Jose office. Doing it this way insures that the system can match the incoming CallerID of the cell phone to the extension (allowing for the other features of Mobile Connect).

 

[pndscm]

This was copied from a previous post. I won't take credit for it.

Single number ring

Step 1.- End User configuration, Enabling Mobility
Go to the Cisco Unified Communications Manager Administration page
Select User Management
Select End User
Click ADD NEW and proceed to create an End User, for the purposes of this document I will be creating user named mobilityuser
You may create the end user as usual with the exception that you must check the enable mobility check box and select SAVE, great you have just created an End user with the mobility feature enabled

Step 2.-Creating a mobility SoftKey template
Go to the Cisco Unified Communications Manager Administration page
Select Device
Select Device Settings
Select Softkey Template
Select ADD New
The system will ask you as to what sofktey template to be used as your new template to be based on, I will select for the purposes of this document the "Standard User" template then select Copy, here you will need to change the name of the Standard User Softkey Template for something that is appropriate, in my case I will change the name to Mobility_SK, select SAVE.
-Click the GO button that have the related link option "Configure Softkey Layout"
-Add the following options to the following states:
*On Hook Mobility
*Connected Mobility


Step 3.-Proceed to build a phone
Go to the Cisco Unified Communications Manager Administration page
Select Device
Select Phone
Select ADD NEW (in my case I will be building and configuring a Cisco 7961 using SIP as a protocol, you can configure your phone with SCCP protocol if you like)
Select the appropriate settings for your phone such as Device pool, CSS, MRGL's, device security profile, location, etc although you need to select the newly configured mobility SoftKey Template and select the newly created end user as the Owner User ID and Click the SAVE button
Proceed to set up a DN for this phone and configure things like a Partition, Calling Search Space, Voice mail profile if any, then Select and click the SAVE Button

Step 4.-Configure a Remote Destination Profile
Go to the Cisco Unified Communications Manager Administration page
Select Device Settings
Select Remote Destination Profile
Select and Click the Add New button
Configure the following settings
Name: mobilityuser_RDP
Description: Mobilityuser Remote Destination Profile
User ID: [your mobility user]
Device Pool: [an appropriate device pool]
Calling Search Space: [an appropriate CSS]
User Hold Audio Source: [your option of preference]
Network Hold MOH Audio Source: [your option of preference]
Privacy: [off]
Rerouting Calling Search: [preferably a CSS that have access to the pstn] *although I will suggest you to configure an special CSS for mobility to avoid fraud
Calling Party Transformation CSS: [none]
Leave all the rest as default
Select Save
Proceed to a new DN by clicking on the Line[1] – Add a new DN link
For this example I have created DN 0621, and it's the same DN that I am using in the Cisco 7961 IP Phone that I created above, so by entering the DN and selecting the a partition it should auto populate
-Click Save

If you want all calls to ring both phones, proceed to Step 6.

Step 5. – Create an Access-List
Go to the Cisco Unified Communications Manager Administration page
Select Device Settings
Select Access List
Click the Add New button
Enter the following Settings
Name: mobilityuser_name
Description: Give clear description
Owner: Select user
Click Allowed box (If these are going to be allowed)
-Click Save
Click Add Member
Select DN’s that you want to be able to ring both phones
-Click Save when all allowed numbers are entered

Step 6.- Create a new Remote Destination
Go to the Cisco Unified Communications Manager Administration page
Select Device
Select Remote Destination
Click the Add New button
Enter the following Settings

Name: mobilityuser_mobilephone
Destination Number: 9+[mobile phone number] (please refer to your dialplan)
Answer too Soon Timer: leave as default
Answer too Late Timer: leave as default
Delay Before Ringing Timer: leave as default
Remote Destination Profile:[select the newly created remote destination profile]
Allowed Access List: Select the list if created in Step 5
Select the mobile phone check box
Click Save
Next select the Line association check box and click Save
You may need to reset the phone that is associated with the mobile connect user
Your user is now ready to begin using the mobile connect feature

While connected on a call the user will need to press the mobility softkey select
Send call to Mobile Phone and the call will sent to his/her mobile phone, to reverse back to his/her Cisco IP phone he/she will need to simply hang up their mobile phone

 

[bulakeno]

Thanks you guys for your responses, I finally got it working, made some adjustment to the RDP CSS.