Network Bulls
www.networkbulls.com
Best Institute for CCNA CCNP CCSP CCIP CCIE Training in India
M-44, Old Dlf, Sector-14 Gurgaon, Haryana, India
Call: +91-9654672192
Figure 3-7 shows an example of a CUCM H.323 gateway configuration.
To add an H.323 gateway to CUCM, choose Device > Gateway and click Add New. Then,
from the Gateway Type drop-down list, choose H.323 and click Next.
When configuring an H.323 gateway, be sure to first enable H.323 at one IP interface. If
multiple IP interfaces are present, it is recommended that you use a loopback interface.
Otherwise, if the interface that has been selected for H.323 is down, the H.323 application
will not work, even if other interfaces could be used to route the IP packets. In this example,
H.323 has been enabled on the loopback interface using the h323-gateway voip interface
and h323 gateway voip bind srcaddr IP address commands.
In contrast to MGCP gateways, in which the call agent takes care of call routing, H.323
gateways require local dial plan configuration. In the example, the H.323 gateway is
configured with a VoIP dial peer that routes calls placed to the gateway's PSTN number
511555.... toward CUCM. These are the calls that the gateway receives from the PSTN,
because 511555 1001-1003 is the direct inward dialing (DID) range of the PSTN interface
(port 0/0/0:23). In addition, the PSTN gateway is configured with a plain old telephone
service (POTS) dial peer that routes all calls starting with 9 to the PSTN using the ISDN
PRI (port 0/0/0:23).
Note that the configured digits of a destination pattern in a POTS dial peer are automatically
stripped, because POTS dial peers send only wildcard (variable) digits by default. Therefore,
the 9 is not sent to the PSTN. In the other direction, the gateway does not perform any digit
manipulation, because VoIP dial peers do not strip any digits by default. CUCM receives
H.323 call setup messages for calls that were received from the PSTN in full length (usually
ten digits). Because the internal directory numbers are four digits, either CUCM or the
H.323 gateway needs to be configured to strip the leading digits so that the remaining four
digits can be used to route the call to internal directory numbers.
Trunk Implementation Overview 65
Figure 3-7 CUCM H.323 Gateway Configuration
In the Gateway Configuration window, enter the IP address of the H.323 gateway in the
Device Name field, select the device pool that should be used, and optionally enter a
description. If CUCM should consider only some of the called digits, the significant digits
parameter can be set to the number of least-significant digits that should be used to route
inbound calls. In this example, in which the gateway sends full ten-digit PSTN numbers to
CUCM, setting the significant digits to 4 would allow the incoming calls to be routed to
internal directory numbers without any additional CUCM digit manipulation configurations,
such as translation patterns.
Trunk Implementation Overview
Figure 3-8 illustrates the most important configuration elements for implementing a SIP or
nongatekeeper-controlled intercluster trunk (ICT) in CUCM—the configuration of the trunk
itself and the IP address of the peer. CUCM also needs to have the route group configured
with the gateway, the route list, and route pattern configuration.
Chapter 3: Implementing Multisite Connections
Figure 3-8 Nongatekeeper-Cont rolled ICT and SIP Trunk Configuration Overview
Gatekeeper-Controlled ICT and H.225 Trunk Configuration
Figure 3-9 illustrates the most important configuration elements for implementing a
gatekeeper-controlled intercluster trunk or H.225 trunk in CUCM.
The required items are the configuration of the gatekeeper with its IP address and the
gatekeeper-controlled ICT that points to the gatekeeper. CUCM also needs the route group
connected to the gateway, route list, and route pattern configuration, similar to the previous
example.
Trunk Implementation Overview 67
Figure 3-9 Gatekeeper-Controlled ICT and H.225 Trunk Configuration Overview
Implementing SIP Trunks
Figures 3-10 and 3-11 illustrate a CUCM SIP trunk configuration.
Chapter 3: Implementing Multisite Connections
Figure 3-11 CUCM SIP Trunk Configuration, Continued
To add a SIP trunk in CUCM, choose Device > Trunk and click Add New. Then, in the
Trunk Type drop-down list, choose SIP Trunk and click Next.
In the Trunk Configuration window, enter a name for the SIP trunk, choose the device pool
that should be used, and optionally add a description.
In the SIP Information area of the Trunk Configuration window shown in Figure 3-11, enter
the destination address of the device that is located on the other end of the SIP trunk. This
device can be a Cisco Unified Border Element, CUCM Express, or any other SIP-capable
device, such as a third-party SIP proxy server.
In addition, you must choose a SIP Trunk Security Profile and a SIP Profile. Both
parameters are mandatory and do not have a default value.
The SIP Trunk Security Profile is used to enable and configure security features on SIP
trunks, such as Transport Layer Security (TLS) with two-way certificate exchange, or SIP
digest authentication. One default SIP Trunk Security Profile exists: the Non Secure SIP
Trunk Profile, which has security disabled. You can configure additional SIP Trunk Security
Profiles by choosing System > Security Profile > SIP Trunk Security Profile.
Trunk Implementation Overview 69
The SIP Profile is used to set timers, Real-Time Transport Protocol (RTP) port numbers,
and some feature settings (such as call pickup Uniform Resource Identifiers [URIs], call
hold ringback, or caller ID blocking). One default SIP profile exists called the Standard SIP
Profile. You can configure additional SIP profiles by choosing Device > Device Settings >
SIP Profile.
Implementing Intercluster and H.225 Trunks
Figures 3-12 and 3-13 demonstrate how to implement nongatekeeper-controlled
intercluster trunks in CUCM. The steps are as follows:
Step 1 Choose Device > Trunk, and then click Add New.
Step 2 Choose the appropriate trunk type. After you click Next, the Trunk
Configuration window appears, where you can configure the
nongatekeeper-controlled intercluster trunk.
Step 3 Enter a device name, choose the device pool that should be used, and
optionally add a description.
Step 4 Enter the IP address or addresses of the CUCM servers of the other
cluster.
Figure 3-12 Implementing Nongatekeeper-Controlled Intercluster Trunks
Chapter 3: Implementing Multisite Connections
NOTE Because the nongatekeeper-controlled intercluster trunk does not use a
gatekeeper for address resolution, you must manually enter the IP address(es) of the
devices on the other side.
No comments:
Post a Comment