Information Technology Reference
In-Depth Information
voice-class h323 1
session target ipv4:10.2.2.1
codec g711alaw
!
dial-peer voice 30 voip
preference 2
destination-pattern 5...
voice-class h323 1
session target ipv4:10.2.2.2
codec g711alaw
As previously discussed, the
voice service voip
command is used to enter voice service configuration mode.
Next, the
h323
command enters the H.323 submode, and the
ccm-compatible
command configures the gateway for connectivity with
a CUCM.
The
h323-gateway voip bind srcaddr
ip-address
command is now used to configure the IP address used as a source IP address for
messages sent to a CUCM.
The
voice class h323
tag
command is then used to configure an H.323 voice class. With the H.323 voice class, the
h225 timeout tcp
seconds
command configures the H.225 TCP establish timeout.
VoIP dial peers are then configured pointing to redundant CUCMs, and the previously defined voice class is referenced within each
VoIP dial peer.
H.323 gateways can be configured in CUCM by navigating to
Device
,
Gateway
.
Although most problems with H.323 gateways are caused by simple misconfiguration, before finishing this section, it is worth
looking at some particular issues that can occur when deploying H.323 gateways in conjunction with CUCM. These issues result in no
ringback tone being played when it should be. The following three conditions can occur:
■
No ringback tone on an IP phone when calling a destination in the PSTN:
This issue occurs because of the way in which
CUCM handles ringback when it is calling out via an H.323 gateway. It can be resolved by configuring the
progress_ind
alert enable 8
command under the appropriate POTS dial peer.
