Information Technology Reference
In-Depth Information
The
zone local
gatekeeper-name
domain-name
[
ras-IP-address
] command is then used to configure the zone controlled by the
gatekeeper. In this example, the name of the domain served by the gatekeeper is mjlnet.com, the gatekeeper's name is mjlgk, and
10.1.1.1 is a local address used as a source IP address for RAS packets.
Next, the
zone prefix
gatekeeper-name
e164-prefix
command is used to specify the gatekeeper's name and add a prefix to the
gatekeeper's zone list. In this case, all prefixes beginning with digits 345 are associated with the gatekeeper mjlgk. Note that the
asterisk (*) is a wildcard that represents one or more digits (0[nd]9). The dot (.) wildcard (not shown) can be used to match one digit
(0[nd]9).
The
gw-type-prefix
type-prefix
[
default-technology
] command specifies a default technology prefix (1#*), which is used to route
calls if the called number does not correspond with a registered E.164 address.
After
gw-type-prefix
is the
bandwidth
total
zone
zone-name bandwidth-size
command. This command configures the maximum
aggregate bandwidth for H.323 traffic within the zone, which, in this case, is 1024 Kbps.
Next, the
bandwidth
session
zone
zone-name bandwidth-size
command is used to configure the maximum bandwidth available for a
session in the zone, which, in this example, is 128 Kbps.
Zone bandwidth can be calculated as follows:
Zone bandwidth = 2 * Total calls * Codec (payload) bandwidth
Finally, the
no shutdown
command activates the gatekeeper.
H.323 control messages used to facilitate CAC when using gatekeeper-control intercluster trunks are described in the section, “H.323:
H.225, H.245, RAS,” later in this e-book.
Session Initiation Protocol Proxy
The Session Initiation Protocol (SIP) is a peer-to-peer signaling protocol described in many RFCs (most notably 3261) that allows the
setup, modification, and termination of sessions between participants. SIP is described in more detail in the section, “SIP,” later in this
e-book. This section describes only the integration of Cisco CUCM with SIP networks via SIP trunks.
