Integrating Cisco CallManager 7.0 and CME using H.323
Configuring a H.323 connection between CME and CallManager is just like configuring a H.323 connection between a Voice Gateway and CallManager. The fact that the Gateway is providing CME services is actually incidental - CallManager needs to know how to route calls to CME, and CME needs to know how to route calls to CallManager. Certain Directory Numbers will belong to CME, and certain Directory Numbers will belong to CallManager. When the number ranges overlap, a prefix can be used to route calls between systems.
The process to integrate CME and CallManager is as follows; first, on CallManager:
- Configure a new location and region for the CME site
- Configure the H.323 gateway, route-list and route-group
- Configure a route pattern for the CME numbers, referencing the specified route-group
On CME:
- Bind the H323 gateway process to the CME source address (the same IP as configured in CallManager)
- Configure the dial-peer to route numbers to CallManager
A few things to note:
- Make sure the codec matches under the Region configuration and the dial-peer
- Ensure that the H323 bound address matches the configuration in CUCM
- If dial-plan pattern is configured under telephony-service, the number is translated by the remote CME system
The configuration for the CME dial-peer is as follows:
dial-peer voice 1234 voip
 preference 1
 destination-pattern 1...
 session target ipv4:192.168.255.1
 dtmf-relay h245-alphanumeric
 codec g711ulaw
 no vad
Bind the H323 interface as appropriate; best practice dictates that this should be a loopback interface.
interface Loopback0
 ip address 172.16.1.1 255.255.255.255
 h323-gateway voip bind srcaddr 172.16.1.1
Verify on the CME side, the dial-peer is configured.
CME#show dial-peer voice summary
dial-peer hunt 0
             AD                                    PRE PASS                OUT
TAGÂ Â Â Â TYPEÂ Â MINÂ Â OPERÂ PREFIXÂ Â Â Â DEST-PATTERNÂ Â Â Â Â Â FERÂ THRUÂ SESS-TARGETÂ Â Â Â STATÂ PORT
1234   voip  up   up             1...               1  syst ipv4:192.168.255.1
Now, make a call from CME to CUCM, with the debug "debug voip ccapi inout" enabled.
Feb 23 11:32:39.067: //-1/8287825D80D0/CCAPI/cc_api_call_setup_ind_common:
   Interface=0x4863C5E8, Call Info(
   Calling Number=7001,(Calling Name=)(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
   Called Number=(TON=Unknown, NPI=Unknown),
   Calling Translated=FALSE, Subscriber Type Str=RegularLine, FinalDestinationFlag=FALSE,
   Incoming Dial-peer=20001, Progress Indication=ORIGINATING SIDE IS NON ISDN(3), Calling IE Present=TRUE,
   Source Trkgrp Route Label=, Target Trkgrp Route Label=, CLID Transparent=FALSE), Call Id=-1
Feb 23 11:32:39.723: //43/8287825D80D0/CCAPI/ccCallSetupRequest:
   Destination Pattern=1..., Called Number=1015, Digit Strip=FALSE
Feb 23 11:32:39.723: //43/8287825D80D0/CCAPI/ccIFCallSetupRequestPrivate:
   Interface=0x4744C394, Interface Type=1, Destination=, Mode=0x0,
   Call Params(Calling Number=7001,(Calling Name=Fred )(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
   Called Number=1015(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,
   Subscriber Type Str=RegularLine, FinalDestinationFlag=FALSE, Outgoing Dial-peer=1234, Call Count On=FALSE,
   Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Application Call Id=)
Once the call is established, you can verify that the call is enabled, and observe codec selection.
CME#show voice call status
CallID     CID  ccVdb      Port             DSP/Ch  Called #   Codec    Dial-peers
0x2F       12C4 0x4863C5E8 50/0/1.0                 1015       g711ulaw  20001/1234
1 active call found
Reference the CME Router as a H.323 Gateway
Create a Route Pattern for the CME Numbers
Enter the Number as a Normal 4 Digit Extension (per the Route Pattern)
Observe Translation due to CME Dialplan-Pattern
