Cisco TelePresence Serial Gateway Series

How dial plan rules work on Cisco TelePresence Serial Gateway Series products

The Cisco TelePresence Serial Gateway Series products (referred to here as the "serial gateway") store two separate dial plans:

• IP to Serial
• Serial to IP

First match routing

For a given call direction (IP to Serial or Serial to IP) the dial plan list works on a "first match" basis. The gateway starts at the top of the list and works down until it finds a matching rule. Then it applies that rule to the call. When a match is found no more rules are checked. When you are troubleshooting routing problems, always check the order of the dial plan rules.

IP to Serial rules

The IP to Serial direction involves calling from an IP endpoint (such as an MCU or H.323 endpoint) to an H.320 endpoint.

Example 1 Calling an H.320 endpoint from an MCU without a gatekeeper

If the MCU and the serial gateway are not registered to the same gatekeeper:

1. Configure the serial gateway as an H.323 gateway on the MCU.
2. Create the following dial plan rule:
   • Called number matches: type 5 (D+), for example
   • Call this number: enter $1

   This catches any number that begins with 5 and contains at least 2 digits. The digit(s) after the 5 are used to connect over serial (the parentheses in the rule tells the gateway to extract all incoming digits after the 5 into a substitution group and the $1 in the rule tells the gateway to substitute those digits as the outgoing number to call).

Example 2 Calling an H.320 endpoint from an MCU with a gatekeeper

If the MCU and the serial gateway are registered to the same gatekeeper:

1. Register a service prefix on the serial gateway (for example, 4).
2. Create the following dial plan rule:
   • Called number matches: type 45 (D+), for example
   • Call this number: enter $1

   This catches any number that begins with 45 and contains at least 3 digits. The digit(s) after the 45 are used to connect over serial (the parentheses in the rule tells the gateway to extract all incoming digits after the 45 into a substitution group and the $1 in the rule tells the gateway to substitute those digits as the outgoing number to call).

Serial to IP rules

The Serial to IP direction involves calling from an H.320 endpoint to an IP-based endpoint (such as an MCU or H.323 endpoint). The examples below illustrate typical scenarios, where you might want to route calls to an MCU auto attendant or to a particular conference on an MCU.

Example 3 Routing calls to an MCU auto attendant (or another IP address)

Create the following dial plan rule:

• Match calls incoming on port: select Any, for example
• Call this number: enter the IP address of the MCU or endpoint

Example 4 Routing calls to a particular conference on an MCU

Create the following dial plan rule:

• Match calls incoming on port: select 09, for example

• Call this number: enter the IP address of the MCU and the conference identifier in the format <ip address>!<Numeric id of conference>.

  If the gateway and the MCU are registered to the same gatekeeper, then for Call this number you can enter the E.164 number or the registered Numeric ID of the conference

More information

See the online help for more information about dial plans, including syntax and additional examples.

This article applies to the following products:

• Cisco TelePresence Serial GW 3340 / MSE 8330 blade