Mobile Voice Access Using a Hairpinning Configuration
PSTN --- GW <-- MGCP --> CUCM
<-- H.323 -->
*The Unified Communications Manager Version used in this document was 22.214.171.1240-13
*A Publisher and a Subscriber servers were used in this configuration
*The voice gateway used was a Cisco 2821 with the following hardware
2 Gigabit Ethernet Interfaces
48 Serial interfaces
4 Channelized T1/PRI ports
4 Voice FXO Interfaces
4 Voice FXS interfaces
*The IOS version used in our gateway was 12.4(3f)
-For the following example we will using 5311 as our incoming DID from the PSTN (4 digits)
-Our Mobile voice access number will be 3511
-The gateway used in this example was only configured as an MGCP gateway on our Unified Communications Manager, this gateway was also used to interconnect a ROLM 9755 using a CAS T1 connection.
It is assumed that you have already configured an RDP profile along with an Remote Destination Number as well the necessary settings have been applied to the UCM test user in CallManager.
Go to the UCM administration page
-Select the System TAB
-Select the Service parameters TAB
-For the server field, select the hostname/ip address of the publisher
-For the service field, select Cisco Callamanager
-Under Clusterwide Parameters (System-Mobility)
-Set the âEnable Enterprise Feature Accessâ parameter to True
-Set the âEnable Mobile Voice Accessâ parameter to True
-Proceed to Enter the Mobile Voice Access number that you are going to use in our case will be 3511
-Set the âMatching Caller ID with Remote Destinationâ parameter to âcomplete matchâ (by selecting this parameter the gateway will look for a âcomplete matchâ of digits coming from the PSTN and it will decide if is a complete match of an existing Destination Number then the user will be prompted for it's CCM user PIN number, if is not a complete match then the user will be prompted to enter its Remote Destination Number followed by the pound sign.
-In the other hand if you set the âMatching Caller ID with Remote Destinationâ parameter to âPartial Matchâ then the gateway is suppose to match the number of digits that you decide against an existing Destination number but will ONLY WORK WITH A DEDICATED H.323 GATEWAY and it will not work using a hairpinning set up which is our case.
Note: When setting the âMatching Caller ID with Remote Destinationâ parameter to âPartial Matchâ in this setup (a hairpinning set up) the Remote Destination user calling from a device that match a remote destination number will experience a silence when dialing our MVA DID
-Go to the Media Resources TAB
-Select the Mobile Voice Access TAB
-On the Mobile Voice Access Directory Number field enter 3511
-On the Mobile voice Access Partition select a partition that is an accessible partition
-Proceed to select the desire Locale.
-Telnet or SSH to the gateway that you are going to use.
-Under config mode proceed to enter the following command
Voice service voip
Allow-connections h323 to h323
Voice class h323 1
H225 timeout tcp establish 3
Service cmm http://[ip address of your publisher]:8080/ccmivr/pages/IVRMainpage.vxml
See the next steps