You are on page 1of 7

H.

323 Defined
H.323 is a peer-to-peer voice signaling protocol. H.323 is a protocol suite built with

H.225

Handles call setup/teardown and Q.931 operations

H.225 RAS

Handles gatekeeper signaling

H.245

Feature negotiation likes codec etc

H.262 / H.263

H.450

Supplementary services (Hold, Transfer.)

T.120

Data transfer, application sharing etc

Video conferencing

Reason to choose H.323

You want caller-id support on FXO or T1 CAS

You want fractional PRI support

Widely supported-interoperable

Many call routing and manipulation options

Supports voice, video and data capabilities

Non-Facility Associated Signaling (NFAS) support

H.323 gatekeeper support

PRI call preservation

H.323 Call Flow

CCM and H.323 GW exchange H.225 setup messages on TCP port 1720

CCM and H.323 GW perform H.245 feature negotiation

RTP streams sent

H.323 Fast Start (default) combines H.225 and H.245

H.323 Defaults
VoIP

G.729 Codec (G729r8)

HUNTSTOP disabled

VAD enabled

RSVP = Best effort

DTMF Rely disabled

FAX Relay Disabled

Preference 0

PLAYOUT delay = 40 (de-jitter buffer)

Audio = DSCP EF

Signaling = DSCP AF31

PSTN

DID is disabled

Register with gatekeeper

Preference 0

HUNTSTOP disabled

Digit strip enabled

H.323 Basic Configuration


Router(config)#voice service voip
Enters voice-service voip configuration mode

Roter(config-voi-serv)#h323
This commands will let you to enable H.323 as VoIP service and enters h323 configuration mode
Router(config-serv-h323)#telephony-service ccm-compatible
This command will enable Call Manager compatibility for H323
Router(config-if)#h323-gateway voip bind srcaddr ip-addr-of-interface
This command will bind interface IP Address with H323 for signaling

DTMF and Payload Config


Router(config-dial-peer)# dtmf-relay type
This command should be issued in dial-peer configuration mode to enable dtmf-relay type which
should be used for connection using H323
Router(config-dial-peer)#rtp payload-type type
This will let you to specify payload for an rtp packet

Codec Configuration:
Router(config)#voice class codec tag
Router(config-class)#codec preference {1-14}
These commands allow you to define a voice-class for codec to use during different
configurations.
This can be implemented to any dial-peer using following command
Router(config-dial-peer)#voice-class type tag
You can also use codec command at dial-peer level but in this way you can define only single
codec.
Router(config-dial-peer)#codec codec-type

Using Voice-Class for H323 common features


Router(config)#voice class h323 tag
Router(config-class)#h225 timeout {connect|setup|tcp}

You can also define a H323 class to define different parameters which can be used for different
configuration rather typing in each case.

Step to configure H.323 Gateway with CUCM


1. Make sure that H.323 is enabled and specify the H.323 source address the voice gateway
2. Configure the POTS and VoIP dial peers on the gateway
3. Define H.323 gateway on CUCM
4. Add route pattern pointing to the H.323 gateway

Step 1: H.323 Configurations


voice service voip
h323
telephony-service ccm-compatible
no shutdown
interface FastEth0/0
h323-gateway voip bind srcaddr 10.1.1.1

Step 2: Configuring Dial Peers


dial-peer voice 9 pots
destination-pattern 9T
Incoming called-number 2
direct-inward-dial
port 1/0:23
dial-peer voice 10 voip
destination-pattern 2
session target ipv4:10.1.1.2

voice-class codec 1
voice-class h323 1
If you have multiple CUCM and want to implement fail over in case one goes down then you
have to specify this command
voice class h323 1
h225 timeout tcp establish 3
Also mention following command in dial-peer mode
preference 1

Step 3: Define H.323 gateway on CUCM


To define H.323 gateway in CUCM follow the steps

Device
o Gateway

Click on Add New

Choose Gateway type as H.323 Gateway and click Next

Enters all require parameters and click Save

H.323 Gateway
One thing we have to note here that H.323 Gateway never registers with CUCM.

Step 4: Add route pattern pointing to the H.323 gateway


Here we will define simple route pattern without defining Route Groups and Route Lists which
are beyond the scope of this document. To configure simple route pattern follow the steps

Call Routing

Route/Hunt

Route Pattern

Click to Add New

Calls between H.323 gateways and SIP gateways


If you want to route calls between two H.323 gateways then you may have to allow H.323 calls
relay to 2nd H.323 gateway using the following commands
Router(config)#voice service voip
Router(config-voi-serv)#allow-connection h323 to h323
You can also route calls from H.323 to SIP and vice versa using the following two commands
Router(config-voi-serv)#allow-connection h323 to sip
Router(config-voi-serv)#allow-connection sip to h323

Calls preservations to SRST in case CCM goes down

What happened with the calls if CUCM goes down during a call conversation? The call will be
dropped because gateway will keep in sending keep alive to CUCM and if it doesnt receive
response then call will be dropped rather fail over to SRST. To enable fail over to SRST we have
to disable keep alive in h323 voice service mode
Router(config-serv-h323)#no h225 timeout keepalive

Debug commands
show dial-peer voice tag
show dial-peer voice summery
debug { voip|voice} dialpeer
debug h225 asn1
debug h225 q931
debug h225 events
show dialplan number phone-number Tells which dial peers are matched by a specific phone
number
debug cch323 h225 Commands to troubleshoot call setup and teardown
debug cch323 h245 Commands to troubleshoot call setup and teardown
debug voip ccapi inout Debugs the call control application programming interface. It shows
details about the call setup from both the telephony and network sides (use with care of
production router)

You might also like