Cisco H.323 VC-289 - Manual (Page 39)

Configuring H.323 Gatekeepers and Proxies
H.323 Gatekeeper Configuration Task List
VC-327
Cisco IOS Voice, Video, and Fax Configuration Guide
Configuring Gatekeeper Triggers for Interaction with External Applications
To establish statically configured triggers on a router, use the following commands beginning in global
configuration mode:
Command Purpose
Step 1 Router(config)# gatekeeper Enters gatekeeper configuration mode.
Step 2 Router(config)# server trigger
{arq | lcf | lrj | lrq | rrq | urq} gkid priority
server-id server-ip-address server-port
Configures a static server trigger for external
applications. Enter the all form of the no server trigger
all command to remove every static trigger that you
configured if you want to delete them all.
The keywords and arguments are as follows:
• all—Deletes all command-line interface- (CLI-)
configured triggers.
• arq, lcf, lrj, lrq, rrq, urq—Specifies Registration,
Admission, and Status (RAS) message types. Use
these message types to specify a submode in the
gatekeeper configuration mode where you configure
a trigger for the gatekeeper to act upon. Specify only
one message type per server trigger command. There
is a different trigger submode for each message type.
Each trigger submode has its own set of applicable
commands.
• gkid—Specifies the local gatekeeper identifier.
• priority—Specifies the priority for each trigger. The
range is from 1 through 20, with 1 being the highest
priority.
• server-id—Specifies the identification (ID) number
of the external application.
• server-ip-address—Specifies the IP address of the
server.
• server-port—Specifies the port on which the
Cisco IOS gatekeeper listens for messages from the
external server connection.
Step 3 Router(config)# info-only Indicates to the Cisco IOS gatekeeper that messages that
meet the specified trigger parameters should be sent as
notifications only and that the Cisco IOS gatekeeper
should not wait for a response from the external
application.