Configure the Mobile Voice Access Feature

Introduction

This document describes Mobile Voice Access feature  (MVA) which is being introduced in Cisco Unified Communications Manager (CUCM) 6.0 and higher releases.Using Cisco MVA feature, a Public Switched Telephone Network (PSTN) phone user (who has access to CUCM) can dial into the office DID number (XXX-XXXX for an example) and can use his mobile phone as a Internal phone device. The mobile phone operates in a similar fashion like any other IP Deskphone inside the company.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on CUCM 10.X and higher versions.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Configure

Service Activation

Navigate to Cisco Unified Serviceability > Control Center Feature Services > Activate Cisco Unified Mobile Voice Access Service

Configure MVA DN

Navigate to Media Resource > Mobile Voice Access > Configure your MVA number, in this case the number is 5050, as shown in the image:

Configure Service Parameter

Navigate to Service Parameter > Cisco CallManager > Change below parameters

Configure H323 Gateway

Configure your H323 gateway, in this case 10.106.103.149 is the CUCM address.

application
 service mva http://10.106.103.149:8080/ccmivr/pages/IVRMainpage.vxml

 dial-peer voice 5050 pots
 service mva
 incoming called-number 5050
 no digit-strip
 direct-inward-dial
!
dial-peer voice 3001 voip
 destination-pattern 5050
 session target ipv4:10.106.103.149
 dtmf-relay h245-alphanumeric
 codec g711ulaw
 no vad

Configure End User

Navigate to User Management > End User >  End User for MVA access

Also ensure that it is added to the appropriate User Group

Associate the User ID 

Associate the user to the device and the Directory Number (DN).  Also change the device owner ID to that user.

Configure RDP and RD

Create Remote Destination Profile (RDP) and Remote Destination (RD). Ensure that the rerouting CSS can reach the route pattern for Mobile Connect. Associate the DN on RDP to the user, as shown in the image:

Configure Softkey template

Navigate to Device > Device settings > Softkey template > Standard User > Copy > Rename it.

Navigate to On Hook status > Select Mobility, as shown in the image:

Then navigate to Connected status > Select Mobility as shown in the image:

Assigne Softkey template

On the phone, add the softkey template for mobile connect, as shown in the image:

Verify

Use this section in order to confirm that your configuration works properly.

To test it, make a call from PSTN to the MVA number. If the PSTN number matches (partial match according to the preceding configuration) with your remote destination number, you are only required to enter the PIN without the key in the remote destination number when you call the MVA number. Also try Mobile connect and make sure the re-routing CSS can reach the remote destination number.

Troubleshoot

There is currently no specific troubleshooting information available for this configuration.