Understanding H323 Gateway Confguration and Example

There are basically 3 types of Gateways that you would integrate with CUCM -
H323 Gateway (the most popular
MGC! Gateway (easiest configuration
"#! Gateway (upcoming technology
"o in this section we will e$plain you what is a H323 Gateway and how to configure and integrate with Cisco call
manager%
&irst of all' you need to understand that H323 is peer to peer protocol suite which means each end point
in(ol(ed is a intelligent endpoint and can ta)e the routing decision on its own based on its configuration% #t is
not li)e MGC! endpoints which depends on the call manager for each and e(ery action it ta)es%
*efore proceeding further i would recommend you to go through the H323 protocol basics and call flow
e$plained here%
+ets ta)e an e$ample how in CC#, -oice' you would be as)ed to use a H323 Gateway% There are 3 branch sites as
you )now' so you may be as)ed to configure "ite* or "iteC as H323 G.% #n addition you may be as)ed that you
should use the loopbac) interface as the source ip for all the H323 messages originating from gateway%
Your configuration will look like as below:
interface +oopbac)/
ip address 0/%0/%00/%2 211%211%211%211
h323-gateway (oip interface
h323-gateway (oip bind srcaddr 0/%0/%00/%2
This would ensure your re2uirement of using loopbac) interface as originating interface for h323%
3e$t' if the #! phones on the branch sites are registered to the Cisco Call manager then you will need you will
create dial-peer towards CUCM to route the calls coming from !"T3 to CUCM% "ince H323 is a peer to peer
protocol so it can use its dial-peer to route the call correctly%
Here is a sample H323 Gateway configuration:
(oice class codec 0
codec preference 0 g400ulaw
codec preference 2 g425r6
7
(oice class h323 0
h221 timeout tcp establish 3
7
(oice translation-rule 8
rule 0 9:3208;(3<;9 9;09
rule 2 9:383208;(3<;9 9;09
7
(oice translation-profile con(ertTo8digit=3#
translate called 8
7
(oice-port 39/>01
translation-profile incoming con(ertTo8digit=3#
7
dial-peer (oice 0 pots
direct-inward-dial
incoming called-number %
7
dial-peer (oice 3/// (oip
destination-pattern 3<
(oice-class codec 0
(oice-class h323 0
session target ip(8>052%0?6%?3%285
dtmf-relay h281-alphanumeric
incoming called-number %
no (ad
7
dial-peer (oice 3//0 (oip
preference 0
destination-pattern 3<
(oice-class codec 0
(oice-class h323 0
session target ip(8>052%0?6%?3%286
dtmf-relay h281-alphanumeric
no (ad
!
@ Autbound dialpeers
#n abo(e e$ample following things are to be noticed>
1. Dial-peer voice 1 pots is acting li)e the efault incoming ial-peer for all the incoming calls from
!"T3%
2. Dialpeer 3!!! an 3!!1 are the outboun ialpeer towars "#"$ for D%s 3&&&% 3//0 act as bac)up
dial-peer with preference 0 if "U* (052%0?6%?3%285 call manager does not respond in 3 sec as per t'e
voice class '323.
3. (%o 'untstop) comman is efault in the (oip dial-peers howe(er in the case of ephone-dn BhuntstopC
was default%
*. Dialpeer 3!!! is also acting as voip incoming efault ialpeer since we ha(e used Bincoming called-
number %C command
+. .hen 3/// is used as incoming dialpeer only dtmf-relay' (oice class codec and no (ad is used% .hen it is
used as outgoing dial peer then all the commands are used instead of incoming called-number
,. .e ha(e applied translation-profile to voice-port instead of dialpeer so that these translations are
in(o)ed e(erytime irrespecti(e of dial-peer%
%ow you nee to go on "all $anager.
Under De(ice E Gateway E =dd new
De(ice name should be same as the loopbac) address on G.% =ssign correct De(ice pool and location%
For Calling name select display ie delivery.
Feset the gateway%
Gou will ne(er see this G. as registered because this is a peer to peer protocol%
3ow inbound call to the #! phones of *F0 site should wor)%
To ma)e the outgoing calls wor)' we need to ma)e dial-peer on G. and route-patterns on CUCM%
An CUCM>
0% Create a route group% =dd H323 gateway to it%
2% =ssign this Foute group to the +ocal Foute Group in de(ice pool settings%
3% Create Foute list% =ssign the "+FG to Foute list%
8% Create a route pattern% =ssign Foute list to route pattern% Use ,!3M for correct calling number%
!lease lea(e your comments if you ha(e any 2uery% .e will be glad to answer your 2ueries%
MGCP Gateway Confguration
The Media Gateway Control !rotocol (MGC! is an implementation of the Media Gateway Control !rotocol
architectureH0I for controlling media gateways on #nternet !rotocol (#! networ)s connected to the public
switched telephone networ) (!"T3%
#n CC#, -oice +ab you may ha(e to configure one or two gateways as the MGC! gateway% MGC! gateway is
controlled by CUCM means all the call routing decision are made on CUCM% .e donJt configure any dial-peer on
the gateway% "o this ma)es the call routing configuration a lot more easier than h323 gateway%
#"D3 !F# physically terminates on Gateway (i%e% layer 2 howe(er gateway bac)hauls the K530 (+ayer 3
messages to CUCM using MGC! protocol on tcp port 2486%
"o here we are going to tell you how to configure MGC! gateway in simple steps%
&irst configure the #A" gateway from C+# using below commands
card type t0 / / 7 Creating T0 controller
networ)-cloc)-participate wic / 7 +ayer2 cloc)ing
networ)-cloc)-select 0 t0 /9/9/
isdn switch-type primary-ni
controller T0 /9/9/
framing esf
linecode b6Ls
pri-group timeslots 0-3'28 ser(ice mgcp 7 #t means we are creating only 3 bearer channels
interface "erial/9/9/>23
no ip address
encapsulation hdlc
isdn bind-l3 ccm-manager 7 *inding layer 3 to cucm
isdn switch-type primary-ni
isdn incoming-(oice (oice
no cdp enable
ccm-manager switchbac) immediate
ccm-manager fallbac)-mgcp 7 allow gateway to pro(ide call processing ser(ices when Cisco CallManager is
una(ailable
ccm-manager redundant-host 052%0?6%?3%286 7 #! address of !ub CUCM
ccm-manager mgcp
ccm-manager music-on-hold
mgcp
mgcp call-agent 052%0?6%?3%285 ser(ice-type mgcp (ersion /%0 7 #! address of "ubscriber CUCM
mgcp bind control source-interface +oopbac)/ 7 *inding MGC! signalling to loopbac)/
mgcp bind media source-interface +oopbac)/ 7 binding rtp stream to loopbac)/

$G"- Gateway "onfiguration on "#"$
0% MGC! Gateway Configuration> CUCM
&ollow these steps to add an MGC! gateway to CUCM>
1a. . an $G"- Gateway to "#"$
"tep0> #n CUCM =dministration' Choose De(ice E Gateway%
"tep2> Clic) the =dd 3ew button%
"tep3> Choose the =ppropriate MGC! gateway by gateway or router name
"tep8> Clic) 3e$t%
"tep1> Choose MGC! from the protocol drop-down menu and clic) 3e$t
Then the Configuration of the MGC! gateway includes the following steps>
"tep0> ,nter the host name or fully 2ualified domain name (&KD3 of the gateway in the Domain name field% #f a
domain name is specified in the Cisco router you must pro(ision an &KD3% #f the &KD3 specified in the CUCM
does not match the Bhost nameC dot Bdomain nameC of the Cisco #A" router' then end pint will ne(er register% =
router with the host name of Fouter0 and domain name of ccie(oicee$pert%com would ha(e an &KD3 of
Fouter0%ccie(oicee$pert%come
"tep2> ,nter a description of the gateway%
"tep3> "elect a CUCM group
"tep8> Configure the #"D3 switch type
"tep1> +ocate the configured slots' -#C" and endpoint selection' and select the (oice hardware module placed in
the slot
"tep?> Clic) "a(e% Feset the gateway ( or clic) =pply config for the changes to apply%
1b. .ing t'e /npoints
,ndpoints are added by selecting the -oice modules and (oice interface cards at the Gateway configuration
page% To add endpoints to a gateway' follow these steps>
"tep0> +ocate the configured slots' -#Cs and ,ndpoints selection and select the (oice hardware module placed in
the slot%
"tep2> The subunits (-#C slots of the selected (oice module will display% "elect the subunit ((oice interface
card
"tep3> Clic) "a(e%
"tep8> Fepeat the process to indicate all the (oice interface cards on the gateway%
%ote:
"isco 012 "omman (2'ow inventory) will isplay t'e voice moules an voice interface cars 340"5 wit'
w'ic' t'e gateway is e6uippe.
To configure MGC! endpoint' follow these steps>
"tep0> Clic) the endpoint identifier (/9/9/
"tep2> "elect the de(ice protocol or signaling for the endpoint% T0 and ,0 interfaces support channel associated
signaling (C=" or common channel signaling (CC" if the interface is an #"D3 !rimary Fate #nterface (!F#% =nalog
interface supports ground Mstart (G" and loop-start (+" signaling% "elect the signaling mechanism that be used
on the endpoint and clic) 3e$t%
"tep3> ,nter a description for the point%
"tep8> "elect the de(ice pool for the endpoint%
"tep1> Choose the Calling "earch "pace (C"" and "ignificant digits under the #nbound Call routing section%
"tep?> Clic) "a(e% Clic) Feset to rest the gateway% The reset functionality will push configuration changes to the
gateway%
=fter you reset the gateway' it should show up as registered on the Call manager%
4erification s'ow commans:
s'ow ccm-manager
#t will tell you the registration status of G. on the CUCM and other good details%
s'ow isn status
#t will tell you the isdn status% +ayer 2 status should be BMultiframeN,stablishedC and layer 3 should be B=cti(eC%
=t this point of time' your incoming calls from !"T3 to CUCM endpoints should complete successfully%# hope you
found this post useful% !lease lea(e your comments for any 2uery%
http>99ccie(oicee$pert%com9OpP083
Cisco CUCM and VC !ntegration" H#323 Voice Gateways
Fecently' # ha(e been able to wor) on CiscoQs #! -ideo Communications (#!-C solution portfolio based on the
Tandberg ac2uisition% Cisco is now referring to this collecti(ely as CiscoQs Tele!resence solution%
# ha(e a few blogs in the wor)s on this% Today # wanted to ta)e a little time to discuss a recent issue a customer
of ours encountered%
7'e 2tage
&or sa)e of discussion' consider the following playing field>
Aur customer was running H%323 on the (oice gateway and they used CiscoQs deployment guide for integrating
the CUCM and -C" platforms% They pro(isioned a "#! trun) between the -C" and CUCM in accordance with CiscoQs
3eighbor Rone approach%
7'e -roblem
#n this configuration' the customer was able to dial the auto attendant on their MCU and access meetings using
DTM& from Cisco #! phones% Howe(er' the customer was not able to pass DTM& for !"T3 callers%
The root cause came down to how DTM& relay was configured on the -o#! dial-peers% The dial-peers were
configured to use Sdtmf-relay h281-alphanumericS% "ince the "#! trun) to the -C" was configured for F&C 2633
support there was a conflict in DTM& relay methodology% #n this specific use case' the CUCM tried to engage a
media termination point (MT! resource unsuccessfully and the DTM& failed to be relayed%
7'e 2olution
-o#! dial-peers on H%323 gateways ha(e se(eral DTM& options% =t a high-le(el>
Use Cisco-proprietary FT!% DTM& tones sent Sin-bandS with the FT! channel as (oice data%
Using H%281 signaling or H%281 alphanumeric method% These methods separate DTM& digits from the
(oice stream and send them through the H%281 signaling channel instead of the media channel% =ll H%323
(2 compliant systems support Sh281-alphanumericS% The Sh281-signalS method is optional%
Use 3amed Telephone ,(ents (3T,s% Using 3T, pro(ides a standard way to transport DTM& tones in FT!
pac)ets according to section 3 of F&C 2633%
"o' using 3T, made the most sense since it allows the H%323 gateway and the -C" "#! trun) to negotiate the
DTM& relay method% = sample dial-peer>
dial-peer (oice 0// (oip
description cucm/0
destination-pattern 8881110202
(oice-class codec 0/
session target ip(8>0/%0/%0/%0/
tmf-relay rtp-nte
=fter ma)ing this change' DTM& wor)ed as desired%