Now let's look at the steps to go in and configure specifically Mobile Voice Access. We have a few extra things that we need to do in this instance. We need to activate the service, setup any service parameters, enable the Mobile Voice Access on our users, configure the media resource and then the all important Gateway configuration, making sure we have that VoiceXML application working on our IOS gateways. Remember this needs to be either H.323 or SIP.
Step 1: Activate Service
To activate the service we go out to our Service Activation area, select our server and then make sure that the Cisco Unified Mobility Voice Access Service is selected and activated.
Step 2: Configure Service Parameters
We have some service parameters that we could fine tune. First of all if I am using like my cell phone and I want to put somebody on hold, how do I do that? There are key strokes that we can use and they have some default codes. If you are using a different set of codes, just be careful, they don't overlap with any PSTN codes like turning on and off caller ID, but you know you want to make sure that you don't overlap these codes with anything else that could be functioning.
Also we want to Enable Enterprise Feature Access for Mobile Voice Access. We want to set this to true by setting that Enable Voice Access parameter to True. Mobile Voice Access is only enabled in general but by doing this we can say, "yep, it's out there and it's capable of being used", but in the end user that's where we say this particular end user is going to be using this feature.
Step 3: Enable MVA for End Users
Again key to all this, go into that end user and make sure we say Enable Mobile Voice Access. We also want to go ahead and verify that that Remote Destination Profiles is configured and then associated with this end user.
Step 4: Configure MVA Media Resource
Here's something very specific to Mobile Voice Access, the media resource. We want to go into our Media Resources > Mobile Voice Access and then enter that Directory Number or the number that's going to be dialed for Mobile Voice Access. We also want to reference the gateway that's running the application and remember we want to make sure that the partition of the Mobile Voice Access number is available or associated with that gateway, so make sure they're in the same partition. And then we have to select the language here. So we have to make sure even if it's just English, we select that and add that to the Selected Locales. Once we're done with that we've now configured the Communications Manager side of this, then last thing we need to do is do our gateway configuration.
Step 5: Cisco IOS Gateway Configuration
We need to setup our IOS Gateway Configuration. Now this is just a snapshot of what the configuration could look like. You set application and then you have the service mva and you specify the URL.
applicationservice mva http://192.168.10.240:8080/ccmivr/pages/IVRMainpage.vxml!dial-peer voice 29991 potsservice mvaincoming called-number 4085552999direct-inward-dial!dial-peer voice 29992 voipdestination-patters 4085552999session target: ipv4:192.168.10.240dtmf-relay h245-alhpanumericcodec g711ulawno vad
This is locating the Communications Manager Server where your Mobile Voice Access service has been activated. And I'll tell you easiest way to grab this is to go into your Communications Manager, copy and paste that out to your IOS Gateway. Now we have to configure an Inbound Dial-Peer, this Dial-Peer is POTS in nature and you can see the dial-peer voice 29991 and we say service mva so that actually invokes that application service that we configured. It matches the incoming call number, which in his instance is that 1-408-555-2999, and now we say direct-inward-dial. We say that because on a POTS Dial-Peer, it would play dial tone again. So by saying Direct Inward Dial, it doesn't play dial tone again, so the user doesn't get confused.
We also want to make sure it forwards off to the Communications Manager, so we have a Dial-Peer that matches that destination pattern and points to the Communications Manager via that session target IP address and again we're relaying the DTMF digits coming in, we're specifying what codec we are using and there is no voice activity detection turned on here, so this is again just a snapshot or an example of how an H.323 Gateway might look like when you have that Mobile Voice Access VoiceXML application working.
Mobility features in CUCM Express
On the Communications Manager Express we can setup Mobility. One key element to all of this is modifying the Softkey Template for Mobility. We want to make sure in an idle state that the user can toggle the Mobility feature on and off, so we add it to the on-hook state, we also have the connected state which allows an end user to then toggle that active call to that Single Number Reach that we've setup and we want to reset the ephone to apply any changes. Anytime we make a change to the template in order for that phone to now grab that new configuration we've got to reset it. Here's an example of the ephone template and how we can add that softkey.
ephone-template 1softkeys idle Newcall Cfwdall Redial Mobilitysoftkeys connected Endcall Trnsfer Park Mobility!ephone 1mac-address 0123.4567.89ABephone-template 1username "jdoe" password ciscotype 7965button 1:1
The softkey state is idle so we can say Newcall, if that is something we want to have as one of the softkeys, the Cfwdall, the Redial, and then Mobility. So we add that to the list. In the connected state we do the same thing. Only in a connected state you might see something like Endcall, Transfer Call, Park Call and then add that Mobility feature.
Now we apply that ephone template to our ephone, so we go into our ephone configuration and we now say ephone-template 1 like we see what we created and now that phone template has been applied to that device. You could add this template and then apply it to many phones that are going to be using your Mobility service.
Configuring Single Number Reach
To setup our Single Number Reach we need to get into our Extensions, so whether we've created this extension or we add a new one, once we're in there we click the Advance tab. This will now give us the extension configuration window. Here's where we check the Enable SNR (Single Number Reach) checkbox.
This activates this for that Single Number Reach and now we can enter the Remote number. Remember we have to use a PSTN prefix for outside dialing, remember dialing a 9 possibly and we need to define the Ring remote number after how many times, so we set a timeout value. We can even optionally setup any Call forward no answer parameters, and to enable Mobility we check the Mobility checkbox. Once we're done with this we save it or we click OK and now we click Deliver to send that configuration back to the router so that this takes place.
We can go out to the command line and view what we just pushed as far as our Single Number Reach configuration and we can do some additional configurations. Let’s say we want to make sure that the caller ID is the enterprise number, not the individual number. We can go in and say snr calling-number local and with this, this command sends the enterprise Directory Number instead of the original caller ID at the Single Number Reach number.
ephone-dn 1number 2001name John Doemobilitysnr callin-number localsnr 915118827499 delay 0 timeout 30 cfwd-noan 2000!ephone 1ephone-template 1username "jdoe" password ciscotype 7965button 1:1
For example 91-511-882-7499, by default the original caller ID would be used, maybe that’s not what we want. We want to make sure it’s the enterprise number and we can do that at the command line.