Mobile Connect Phone Support

Tuesday, March 10, 2009

10:12 AM

Mobile Connect
The Mobile Connect feature allows an incoming call to an enterprise user to be
offered to the user's IP
desk phone as well as up to 10 configurable remote destinations. Typically a user's
remote destination
is their mobile or cellular telephone. Once the call is offered to both the desktop and
remote destination
phone(s), the user can answer at any of those phones. Upon answering the call on
one of the remote
destination phones or on the IP desk phone, the user has the option to hand off or
pick up the call on the other phone.
Mobile Connect Phone Support
Mobile Connect is supported on any of the following phone models:
• Cisco Unified IP Phone 7906G
• Cisco Unified IP Phone 7911G
• Cisco Unified IP Phones 7941G, 7941G-GE, 7942G, and 7945G
• Cisco Unified IP Phones 7961G, 7961G-GE, 7962G, and 7965G
• Cisco Unified IP Phones 7970G, 7971G-GE, and 7975G
All phones listed above support Mobile Connect remote destination pickup via the
Mobility softkey,
with both Skinny Client Control Protocol (SCCP) and Session Initiation Protocol (SIP).
The following phones support Mobile Connect with SCCP only:
• Cisco Unified IP Phone 7905G
• Cisco Unified Wireless IP Phones 7920, 7921G, and 7925G
• Cisco Unified IP Phone 7931G
• Cisco Unified IP Phone 7940G
• Cisco Unified IP Phone 7960G
Mobile Connect calls that are answered at a remote destination phone can be
handed off to any of the IP phone models listed above, regardless of remote
destination phone type, because pickup at the IP desk phone requires only that the
user hang up the remote destination phone. All pickup functionality in these
scenarios is handled by Unified CM and the enterprise PSTN gateway that handled
the outgoing call to the remote destination.

Unified CM Service Parameters for Mobile

Connect
Sunday, March 15, 2009
8:11 PM

Unified CM Service Parameters for Mobile Connect

The following items represent a partial list of Unified CM service parameters for the
Cisco CallManager
service that are related to Mobile Connect functionality:
• Enterprise Feature Access Code for Hold (Default value: *81)
This parameter indicates the feature access code used for the hold mid-call feature.
This code is
either manually keyed by the user or programmed as a key on a Smart Phone. This
code is sent as a
DTMF sequence from the remote destination phone back to the enterprise gateway
and is relayed to
Unified CM.
• Enterprise Feature Access Code for Exclusive Hold (Default value: *82)
This parameter indicates the feature access code used for the exclusive hold mid-
call feature. When
exclusive hold is invoked at the remote destination phone, the call cannot be picked
up or resumed
at the user's desk phone. This code is either manually keyed by the user or
programmed as a key on
a Smart Phone. This code is sent as a DTMF sequence from the remote destination
phone back to
the enterprise gateway and is relayed to Unified CM.
• Enterprise Feature Access Code for Resume (Default value: *83)
This parameter indicates the feature access code used for the resume mid-call
feature. This code is
either manually keyed by the user or programmed as a key on a Smart Phone. This
code is sent as a
DTMF sequence from the remote destination phone back to the enterprise gateway
and is relayed to
Unified CM.
• Enterprise Feature Access Code for Transfer (Default value: *84)
This parameter indicates the feature access code used for the transfer mid-call
feature. This code is
either manually keyed by the user or programmed as a key on a Smart Phone. This
code is sent as a
DTMF sequence from the remote destination phone back to the enterprise gateway
and is relayed to
Unified CM.
• Enterprise Feature Access Code for Conference (Default value: *85)
This parameter indicates the feature access code used for the conference mid-call
feature. This code
is either manually keyed by the user or programmed as a key on a Smart Phone.
This code is sent as
a DTMF sequence from the remote destination phone back to the enterprise
gateway and is relayed
to Unified CM.
• Inbound Calling Search Space for Remote Destination (Default value: Trunk or
Gateway Inbound
Calling Search Space)
This parameter determines the nature of inbound call routing for calls coming into
the enterprise
from configured remote destination phones. By default, the inbound calling search
space (CSS) of
the PSTN gateway or trunk on which the call is coming in will be used to route the
inbound call. If
the value of this parameter is set to Remote Destination Profile + Line Calling
Search Space, the
Remote Destination Profile CSS (in combination with the line CSS) will be used to
route the
inbound call. This parameter has no affect on inbound call routing from non-remote
destination
phones.
• Enable Enterprise Feature Access (Default value: False)
This parameter determines whether Enterprise Feature Access is enabled for the
system. This
parameter must be set to True in order for users to invoke mid-call features such as
hold, resume,
and transfer from remote destination phones as well as to use the two-stage dialing
feature.

Mid call feature key sequence

Sunday, March 15, 2009
8:18 PM
Things to know:
Sunday, March 15, 2009
8:23 PM

Things to know:
• Mobile Connect features are not supported for T1 CAS, FXO, FXS and BRI
• Mobile Connect users can enable or disable mobile connect from their Cisco IP
Phone.
• Before implementing this feature consider DLU's consumption
• Depending on the Cellular carrier Answer too Soon/Late timers will need to be
adjusted accordingly
• If unity is configured calls sent to the user mobile phone that go unanswered will
be answer by Unity, please test this feature with multiple cell phone carriers
 before rolling out this great feature in your cluster, you will want to avoid calls to
be answered by the user cell phone voicemail, instead you want the unanswered
calls to be answered by Unity, if unity is configured.

Pasted from <http://www.tek-tips.com/viewthread.cfm?qid=1530927&page=2>

Configuration Guide with screenshots

Sunday, March 15, 2009
9:12 PM
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
 Step 5.- 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
• 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

Configuration Guide without screenshots

Sunday, March 15, 2009
8:40 PM

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

Step 5.- 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]
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

you need to assign a css to Rerouting Calling Search