CUCM Mobility

Overview

There are three distinct types of mobility in CUCM:

1. Device Mobility
2. Extension Mobility
3. Unified Mobility

Device Mobility

Device mobility allows users to roam between sites with their phones.  There are two type of phone configuration parameters; roaming-sensitive and device mobility related. Roaming-sensitive settings do not have an impact on call routing.  Device mobility settings do because they modify the device CSS, AAR group and AAR CSS.

Operation

The following occurs when a Device Mobility-enabled phone registers with CUCM with an IP address that matches an IP subnet configured in a DMI:

• The current device pool is chosen as follows:
  • If the DMI is associated with the phone’s home device pool, the phone is considered to be in its home location. Therefore, Device Mobility does not reconfigure the phone.
  • If the DMI is associated with one or more device pools other than the phone’s home device pool, one of the associated device pools is chosen based on a round-robin load-sharing algorithm.
• If the current device pool is different from the home device pool, the following checks are performed:
  • If the physical locations are not different, the phone’s configuration is not modified.
  • If the physical locations are different, the roaming-sensitive parameters of the current roaming device pool are applied.
  • If the Device Mobility Groups are the same, in addition to different physical locations, the Device Mobility-related settings are also applied, along with the roaming-sensitive parameters.

  Golden Rules

• DIFFERENT physical locations forces the “roaming  sensitive” setting from the roaming device pool to be load unto the device
• SAME device mobility group forces “device mobility information” from the roaming device pool to be loaded on the roaming device.

Configuration Steps

1. Configure physical locations
2. Configure Device Mobility Groups
3. Configure Device Pools
4. Configure Device Mobility Info (D MI – subnet)
5. Set the device mobility mode at either the service parameter or at individual phones

Verification

I’m using the IPXexpert workbooks.  Here is their process that I customized to my environment:

1. Power off the physical phone
2. Change the MAC of the  physical phone to 111111111111 (IP Blue MAC)
3. Change the device type of the IP Blue phone as needed

The ANI for calls made from this IP Blue phone should be from br1ph2

You can also verify by looking on the Device Mobility Setting under the phone in CUCM

Extension Mobility

Overview

Extension Mobility provides the ability for users to move from phone to phone while keeping their extensions.

Configuration Steps

• Ensure that the Cisco Extension Mobility service is running
• From Device > Device Settings > Phone Services – add new
• Get the extension mobility URL from the “features and Services” guide:

http://<IP Address>:8080/emapp/EMAppServlet?device=#DEVICENAME#

• Subscribe the phones to the EM service

• Create a Default Device Profile for each type of phone that you have – Device > Device Settings > Default Device Profile

• Create a User Device Profile (UDP) – Device > Device Settings > Device Profile

• Associate the UDP to a user – User Management > End User

Verification

Unified Mobility

Overview

Unified Mobility includes many different features and options.  For the CCIE lab, there are two that we need to be concerned with:

Mobile Connect (SNR) – use remote destinations for shared lines

Mobile Voice Access – 2 stage dialing – DISA (Direct Inward System Access)

Mobile Connect

Operation

With Mobile Connect, when a call comes into CUCM for a user that has mobile connect enabled and is away from their desk, the call is forwarded to a PSTN number (normally a cell phone).  This is normally invoked through the use of a softkey on the phone.

Configuration Steps

1. Ensure that the Unified Mobile Access Service is running
2. Configure the user accounts – make sure that the Enable Mobility checkboxes are clicked
3. Create access-lists for Mobile Connect
4. Create Remote Destination Profiles (RDPs).
5. Associate the DNs for the users
6. Add the Remote Destinations

Very important! – the rerouting calling search space is used by the remote destination profile to route a call  to the remote destination when the onsite phone is rung.  If you forget to set this, the mobile phone will not ring!

Verification

From the phone that is simulating the mobile phone, make a call to an internal phone.  Verify that the calling number that is presented is the number of the phone onsite.

Mobile Voice Access (MVA)

Operation

With Mobile Voice Access, a remote user can call into a Feature Access Number, enter a pin and can place calls as if being on the enterprise network

Configuration Steps (CUCM)

1. Ensure that the Unified Mobile Access Service is running
2. Configure the user accounts – make sure that the Enable Mobility checkboxes are clicked
3. Create access-lists for Mobile Connect
4. Create Remote Destination Profiles (RDPs).
5. Associate the DNs for the users
6. Add the Remote Destinations
7. On the Service Parameter page, select ‘true’ for Enable Mobile Voice Access and enter the MVA number.  Also select ‘true’ for the Enable Enterprise Feature Access to enable mid call features.
8. Configure media resources for MVA.  Add the MVA pilot number here

Configuration Steps (Gateway)

1. Load the vxml application

Application service MVA

http://<CUCM address>:8080/ccmivr/pages/IVRMainpage.vxml

1. Create inbound dial-peer

Dial-peer voice 100 pots
service  MVA
Incoming called-number 3600 (where 3600 is the MVA number)
No digit strip

1. Create dial-peer to transfer the calls to MVA DN

Dial-peer  voice 101 voip
Preference 1
Destination-pattern <MVA DN>
Sess target ipv4:<CUCM IP address>
Codec g711ulaw
Dtmf-relay h245-alpha
No vad

Verification

MGCP Hairpin

Since MVA requires the use of an H.323 Gateway, if one is being already used one can be created and hairpinned.    This solution is my notes from the IPExpert solution.

Here is what I think the call flow looks like (5010 is MVA number):

PTSN –> MGCP GW –> UCM (simple enough here) then

UCM with RP to MVA number — routes call to 5010 -> H.323 GW then

H.323 — dial-peer to 5010 to UCM –> UCM then

UCM has MVA number in partition that only MVA and H.323 Gateway can see

Configuration

1. Add an H.232 gateway in UCM
2. Create a route-pattern for the MVA pilot number.  The partition must be reachable by the MGCP Gateway.
3. Create a PT and CSS to isolate the MVA number.  pt-mva and css-mva
4. Add the MVA under system.  Make sure to use the mva parition on the MVA number and the css-mva on the H.323 Gateway CSS.

The H.232 config is here:

! this translation fixes the caller id back the the pstn number.  The hairpinning overwrites the CLID.

voice translation-rule 5002
rule 1 /^5002$/ /2123942123/
!
voice translation-profile MVA
translate calling 5002

application
service CCM http://10.10.210.10:8080/ccmivr/pages/IVRMainpage.vxml

dial-peer voice 50100 voip
translation-profile incoming MVA
service ccm
destination-pattern 5010
session target ipv4:10.10.210.10
incoming called-number 5010
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad

Other Features

Limiting what numbers can ring the mobile number

Create an ACL from the ‘call routing’, ‘class of control’ tb.  Assign the ACL to a the user involved in the blocking. Also apply the ACL to the remote destination under

Media Resources

URL during the lab:

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/admin/configuration/guide/cmeadm.html

Overview

Media Resources Types

There are five types of media resources available in Cisco IP telephony:

Annunciator

An annunciator, an SCCP device that uses Cisco media streaming application service, enables call manager to play prerecorded announcements and tones IP phones and gateways.

Conference Bridges

Conference bridges in call manager can be either software or hardware applications. The bridge can be ad hoc or meet me voice conferencing. Each conference bridge can host several simultaneous, multiparty conferences.

Media Termination Point

A media termination point allows call manager to relay calls are routed through SIP or H.323 endpoints or gateways. You can allocate a media termination point device because of DTMF or RSVPs requirements. When a media termination point is allocated for RSVPs, you can insert it between any type of endpoint device, including SIP or H.323 devices.

Transcoder

Call manager invokes a transcoder on behalf of end point devices when the two devices are using different codecs would normally not be able to communicate. When inserted into a call, the transcoder converts the data streams between the two disparate codecs to enable communications between them.

Music On Hold

The integrated music on hold feature provides the ability to place on-net and off net users on hold with music that is streamed from a streaming source.

Transcoders

Situations where you’ll need transcoders in the lab:

• Ad hoc conferencing – one of more of the remote parties uses G.729
• Call transfer and forward – one leg of a hairpin uses G.711 and the other G.729
• CUE – CUE only supports G.711 so if G.729 must be transcoded if used.
• UCCX – Only supports either G.711 or G.729 but not both at the same time.

Transcoder Configuration (CUCM)

1. From Media Resources > Transcoder.  Choose Cisco IOS Enhanced Media Termination Point (hardware)
2. For the device name, use the same name that will be used on the IOS Gateway
3. Enter the device pool.
4. Create an MRG and assign the transcoder to it
5. Create an MRGL and assign the MRG to it
6. Add the MRGL to the device pool

Transcoder Configuration (IOS)

Example

voice-card 0
dsp services dspfarm

dspfarm profile 1 transcode
codec g711ulaw
codec g711alaw
codec g729ar8
codec g729abr8
maximum sessions 6
associate application sccp
no shut

sccp local FastEthernet0/0.20
sccp
sccp ccm 10.10.210.11 identifier 1 version 5.0.1
sccp ccm 10.10.210.10 identifier 2 version 5.0.1

! identifer needs to match ‘associate’ command in ccm group

sccp ccm group 1
bind interface fastethernet 0/0.20
associate ccm 1 priority 1
associate ccm 2 priority 2
associate profile 1 register HQ-XCODER
! register name needs to match transcoder name in UCM

telephony-service (if you need and xcoder on CME)
ip source-address 10.5.49.200 port 2000 sdspfarm units 1
sdspfarm transcode sessions 40
sdspfarm tag 1 XCODER

Conference Bridge Configuration (CUCM)

1. From Media Resources > Conference Bridge select Add New.  Select Cisco IOS Enhanced Conferencing and Transcoding for Voice Gateway Routers
2. Follow the same process as in the transcoder section.

Conference Bridge notes

Documents during lab:

CUCM – Admin guide,  SRND
CME – The CME admin guide has good examples of configuration

Hardware resources
Check the NIPS of the DSPs
show voice dsp group all (credits are MIPS)
G711u uses 15 MIPS and G729 uses 30 MIPS

DSP’es
Voice card
No dspfarm
This means that you will not share your On Board DSPs with other Modules (e.g. NM-HDV-2).
Dspfarm
This means you share your On-Board DSPs with other Modules
Dsp services dspfarm
This means that your On-Board DSPs could be used for dspfarm services (Transcoder, Conference bridge)

The best process to configure the bridge in IOS is to copy, edit and paste the configuration from the CEM admin guide.   If you are configuring a IOS bridge with CUCM, you can verify by using ‘show sccp’ and you should see a CONNECTED TCP state to CUCM.  You should also see a register state for the bridge in CUCM.

Media Termination Point (MTP) Configuration (CUCM)

1. From Media Resources > media Termination Point select Add New. Choose the Cisco IOS Enhanced Software Media Termination Point.
2. Select the type, the name (must be the same as in the Gateway) and the device pool.

MOH Notes This feature includes the following actions:

• End user hold

• Network hold, which includes transfer whole, conference hold, and park hold

Music On Hold Server

 Music on hold configuration

•  Configure audio sources
• Configure MOH server
• Configure MOH service parameters
• (Optional) Configure MOH multicast

Don’t forget to set the correct device pool on the music on hold server or you may end up hearing ‘beeps’ instead of the nice elevator music.

Media Resource Group

Media resource management comprises working with media resource groups and media resource group lists. Media resource management provides a mechanism for managing media resources, so all call managers within a cluster can share them. Media resources provide conferencing, transcoding, media termination, annunciator, music on hold services. You can group devices of the following types into a single media resource group: •Conference Bridge (CFB) •Media Termination Point (MTP) •Music On Hold Server (MOH) •Transcoder (XCODE) •Annunciator (ANN)

MOH spoof from router flash

Multicast MOH is configured as usual on CUCM, but multicast is setup so that the phones don’t see the MOH from CUCM.  This can be done by not enabling PIM, configuring an ACL or reducing the max hops. Configuration steps CUCM

1. Configure the audio source
2. Enable multicast on the pub and use mcast group 239.1.1.1 (G711ulaw) and set the max hops to 1 (for spoofing)
3. Configure the MRG with multicast
4. Configure the MRGL
5. Add the MRGL to the appropriate device pools
6. Create a region for g711ulaw if needed. Also create a new device pool for this region.  Don’t forget to go back to the music on hold server and update the device pool.

CME

Ensure that the music-on-hold.au file is on router flash
Configure music on hold as follows:

ccm-manager music-on-hold
telephony-service
max-ephones 1
max-dn 1
ip source-address x.x.x.x port 2000
moh music-on-hold.au
multicast moh 239.1.1.1 port 16384 route <loopback> <ethernet port&gt
Troubleshooting/Verification

Debug ccm-manager music-on-hold all
Debug ephone moh

Automated Alternate Routing Groups (AAR)

Automated alternate routing provides a mechanism to reroute calls through the PSTN or other network by using an alternate number when call manager blocks a call due to insufficient location bandwidth.   AAR uses the external number mask set on the DN to make the call.  The AAR group is where prefixing (like 91) can be done.

Configuration

1. Enable AAR under the service parameters
2. Create AAR group
3. Create AAR partitions and CSS’s.  Example (pt-aar and css-aar).
4. Adjust ANI as needed.
5. Create new route patterns using the AAR partition(s)
6. Assign AAR at the line level (IPExpert says device level can be unpredictable).  Use AAR CSS @ line and AAR group @ line

Mobile Connect (Single Number Reach)

1. Change device mobility mode to on under the phone
2. Add a user, enable mobility and select the primary device
3. Associate the end user with to the device and enable mobility.
4. Associate the user to the directory number
5. Create a remote destination profile and assign it to the user’s DN.
6. Create a remote destination

Remote Destination Profile

Mobile Connect allows users to manage business calls using a single phone number and pick up in-progress calls on the desktop phone and cellular phone. Mobile Voice Access is the associated integrated voice response (IVR) system, which allows users to turn Mobile Connect on or off and to initiate calls from a cellular phone or other remote phone as if the call were initiated from the desktop phone.

A user remote destination profile contains the parameters that apply to all the remote destinations (cellular or other phones) available for in-progress call transfers and initiation of calls by way of Mobile Voice Access.

A good way to check all the directory numbers that are tied to telephones is to go to call routing, route plan report.

Basic user configuration

Go to user management end-user and click add new. Enter the userid, password and PIN don’t forget the device associations to control the phone.  Also select the directory number associations.

Soft key templates

Soft key templates can be used to provide features when phones are in different states such as on hook, off hook, etc.  The configuration is soft key templates are pretty simple – go to device, device settings create a new soft key template. Then go back to the phone and assign the sake template to the phone.

Phone button templates

Phone button templates are used to provide items like line buttons, new speed dial buttons, etc.  Phone button templates are applied to phone types and are device specific.  These templates can then be applied to individual phones.  To verify that the configuration is correct, go to the phone configuration in call manager and check for the association information.

Common Phone Profiles

The common phone profile have limited options but are useful for creating a template to apply the phones to modify options such as do not disturb. Configure go to device, device settings common phone profile and select pre-configured profile and click the copy button. Then navigate to device phone and select the phone that you want to apply the phone profile to.

Directory Number/Line Configuration

Directory numbers can be added to device phone configuration page. Click the add to DN link on the phone configuration page to add a new DN. Items such as call forwarding call settings can also be set from this configuration screen. Call forward busy internal and external to either voicemail for destination numbers can be done.  The set external mask can also be done from the screen.

Partitions

Partitions are logical groupings used to restrict access to lines. Any DN within a partition can reach any other DN within the same partition.  Partitions are created in call manager from call routing, class of control, partitions.

Calling Search Spaces

Calling search spaces are used to group partitions and define access between different partitions.  CSSs can be configured at both the device level and for individual DNs.  Any configuration of the DN will override device level configuration.  To create a new CSS go to call routing, class of control, calling search space.  Create the CSS and add the route partitions to the calling search space.  Then go to device, phone and select the calling search space as needed.

Device Pools

Device pools are used as templates to set parameters for groups of devices such as phones and gateways on the CCM system. A device pool has many parameters that can be configured in one location applied to multiple devices. The pool eliminates the need for each setting to be configured per device. Once the device is put into a device pool, it will inherit all configuration settings for the device pool.  The device pool is configured from system, device pool.

Regions

When you create a region you specify the audio codec that is used for calls between devices within that region and between that region and other regions. Essentially regions are used to set the audio codec.

The default codec for all calls through CUCM specifies G. 711.

Locations

Locations feature and Cisco call manager lets you specify the maximum amount of audio bandwidth that is available for calls to and from each location. This specification limits the number of calls and it’s over subscription of the priority and with him the IP WAN links.