Adding a Server Trigger

Server triggers allow you to configure your gatekeepers to connect to a specific back-end server.

You can also set the triggers in the gatekeeper configuration so that they send only the specified messages. Servers can also dynamically register their triggers with a gatekeeper.

Server triggers use the Gatekeeper Transaction Message Protocol (GKTMP) to communicate with servers other than Cisco IOS servers.

Use this procedure to add a server trigger to a zone or directory gatekeeper group.

Procedure

You must be in the Design View to add a server trigger.

  1. Expand the dial plan tree to view all components.

  2. Locate the zone or directory gatekeeper group you want to add a server trigger to.

  3. Click the Server Triggers tab.

  4. Right-click and choose Add from the menu. The Add Server Trigger dialog box appears.

  5. Enter the server trigger attribute information.

  6. Click Apply to apply the values and add a new server trigger.

The entry fields are described in the following table:

General Attributes

Description

Message

Configures triggering on RAS message types. Choose one message type from ARQ, DRQ, LCF, LRJ, LRQ, RAI, RRQ, URQ, or IRR. You can only choose IRR if one of the following conditions exists:

  • This server trigger is contained by a directory gatekeeper group with a GDPM feature set of dp1.1 or later.

  • This server trigger is contained directly by a managed zone whose gatekeeper group attribute references a gatekeeper group with a GDPM feature set of dp1.1 or later.

Priority

The priority for each trigger. The range is  1 to 20, with 1 being the highest priority.

Route Server

The route server associated with the gatekeeper for this server trigger.

Information only

Specifies whether this server trigger is for information only. There is no need to wait for acknowledgment.

Destination Type

Choose from  e-mail, e164, or h323-id. You can only set this attribute if the message type is ARQ, LRQ, LCF, IRR, or LRJ. You must also specify destination information.

Destination

The value must be an address of the type specified by the destination type attribute.

Redirect Reason

Configure a redirect reason to trigger on if the message type is ARQ, IRR, or LRQ. The range is 0 to 65535. Reserved values are: 0=unknown, 1=call forwarding busy or called DTE busy, 2=call forwarded no reply, 4=call deflection, 9=called DTE out of order, 10=call forwarding by the call DTE, and 15=call forwarding unconditionally.

Remote Ext. Address

The remote extension address. The value can be any string up to 255 characters.

Endpoint Type

Choose from gatekeeper, h320-gateway, mcu, other gateway, proxy, terminal, voice-gateway

Tech. Prefix

The default tech prefix for this server trigger if the message type is RRQ or URQ.

Click Cancel to cancel the procedure.