Table of Contents

Configuring Signalling Features

This chapter describes signalling-related features and their configuration for the ATM switch router.

Note   This chapter provides advanced configuration instructions for the Catalyst 8540 MSR, Catalyst 8510 MSR, and LightStream 1010 ATM switch routers. For general information about ATM signalling protocols, refer to the Guide to ATM Technology. For complete descriptions of the commands mentioned in this chapter, refer to the ATM Switch Router Command Reference publication.

This chapter includes the following sections:

Configuring Signalling IE Forwarding

You enable signalling information element (IE) forwarding of the specified IE from the calling party to the called party.

Note   The default is to transfer all the information elements in the signalling message.

To configure interface signalling IE transfer, perform the following steps, beginning in global configuration mode:

Example

The following example shows how to disable signalling of all forwarded IEs on ATM interface 0/0/0:

Displaying the Interface Signalling IE Forwarding Configuration

To display the interface signalling IE forwarding configuration, use the following privileged EXEC command:

Example

The following example displays the modified configuration of the signalling IE forwarding:

Configuring ATM SVC Frame Discard

You can select the criteria used to install frame discard on switched virtual channels (SVCs). The default is to install packet discard based on the presence of the ATM adaptation layer 5 (AAL5) information element in the SETUP message.

Note   The term frame discard is referred to as packet discard on ATM switch router virtual circuits.

You can use this global configuration function to modify frame discard for all connections.

To configure frame discard, use the following command in global configuration mode:

This command changes the information that the ATM switch router uses to decide whether or not to install frame discard on SVCs. User-Network Interface (UNI) 4.0 signalling allows for explicit signalling of frame discard. Pre-UNI 4.0 versions use the presence of the AAL5 information elements to determine whether or not to install frame discard. If the AAL5 information element is present, frame discard is installed; otherwise it is not, as shown in the following example.

Example

In the following example, the ATM switch router behavior is set to not use the AAL5 information element to dictate frame discard.

Displaying the ATM Frame Discard Configuration

To display the ATM frame discard configuration, use the following privileged EXEC command:

Example

The following example shows how to display the frame discard configuration:

Configuring E.164 Addresses

E.164 support allows networks that use network service access point (NSAP) ATM addresses formats (for example, 45.000001234567777F00000000.000000000000.00) to work with networks that use E.164 address formats (for example, 1-123-456-7777). For an overview of address types and E.164 subtypes, refer to the Guide to ATM Technology.

The following sections describe configuring E.164 support:

E.164 Conversion Methods

There are three features you can configure on the ATM switch router for E.164 address conversion. The feature you chose depends on the address format you are using. The features are as follows:

Caution   Manually creating the E.164 to AESA address translation table is a time consuming and error prone process. We strongly recommend that you use either the E.164 gateway or E.164 autoconversion feature instead of the E.164 one-to-one address translation feature.

Configuring E.164 Gateway

The E.164 gateway feature allows calls with AESAs to be forwarded, based on prefix matching, on interfaces that are statically mapped to E.164 addresses. To configure the E.164 gateway feature, you must first configure a static ATM route with an E.164 address, then configure the E.164 address to use on the interface.

When a static route is configured on an interface, all ATM addresses that match the configured address prefix are routed through that interface to an E.164 address.

Signalling uses E.164 addresses in the called and calling party IEs, and uses AESAs in the called and calling party subaddress IEs. For a detailed description of how the E.164 gateway feature works, refer to the Guide to ATM Technology.

Note   Enter access lists for E.164 addresses in the E164_AESA format, not native E.164 format. For example, if the E.164 address is 7654321, then the E164_AESA format is 45.000000007654321F00000000.000000000000.00. To filter prefix "765", enter the prefix 45.00000000765..., not just 765.... Access lists operate on the called and calling party IEs. See "Using Access Control."

Configuring an E.164 Address Static Route

To configure an E.164 address static route, use the following command in global configuration mode:

Example

The following example uses the atm route command to configure a static route using the 13-byte switch prefix 47.00918100000000410B0A1081 to ATM interface 0/0/0 with the E.164 address 1234567:

To complete the E.164 address static route configuration, proceed to the "Configuring an ATM E.164 Address on an Interface" section.

Displaying the E.164 Static Route Configuration

To display the E.164 address configuration, use the following privileged EXEC command:

Example

The following example displays the E.164 address configuration using the show atm route privileged EXEC command:

Configuring an ATM E.164 Address on an Interface

One E.164 address can be configured per ATM port. Signalling uses E.164 addresses in the called and calling party IEs, and uses AESA addresses in the called and calling party subaddress IEs.

To configure an E.164 address on a per-interface basis, perform the following steps, beginning in global configuration mode:

Example

The following example shows how to configure the E.164 address 7654321 on ATM interface 0/0/1:

Displaying the E.164 Address Association to Interface Configuration

To display the E.164 configuration, use the following EXEC command:

Example

The following example shows how to display the E.164 address configuration for ATM interface 0/0/1:

When the E.164 gateway feature is configured, the switch first attempts to make a connection using the E.164 gateway feature. If that connection fails, the switch attempts to make the connection using the E.164 address autoconversion feature, described in the following section.

Configuring E.164 Address Autoconversion

If your network uses E164_ZDSP or E164_AESA addresses, you can configure E.164 address autoconversion. The E164_ZDSP and E164_AESA addresses include an embedded E.164 number in the E.164 portion of an E.164 ATM address. This embedded E.164 number is used in the autoconversion process.

For a detailed description of the E.164 autoconversion feature and differences in the autoconversion process between the E164_ZDSP and E164_AESA address formats, refer to the Guide to ATM Technology.

Note   Enter access lists for E.164 addresses in the E164_AESA format, not the native E.164 format. For example, if the E.164 address is 7654321, then the E164_AESA format is 45.000000007654321F00000000.000000000000.00. To filter prefix "765," enter the prefix 45.00000000765..., not just 765.... Access lists operate on the called and calling party IEs. See "Using Access Control.".

E.164 address autoconversion configuration is the same, regardless of which type of address (E164_ZDSP or E164_AESA) your network uses. To configure E.164 address autoconversion, perform the following steps, beginning in global configuration mode:

Examples

In the following example a static route is configured on interface 0/0/1 using the ATM address of the ATM switch router on the opposite side of the E.164 public network; E.164 autoconversion is also enabled:

The converse configuration is done at the ATM switch router across the E.164 network; a static route is configured to the ATM address of the above switch, and E.164 autoconversion is enabled:

Displaying the E.164 Address Autoconversion

To display the E.164 configuration on an interface, use the following EXEC command:

Example

The following example shows how to display the E.164 configuration for ATM interface 0/0/1:

Configuring E.164 Address One-to-One Translation Table

The ATM interface to a public network commonly uses an E.164 address for ATM signalling, with international code designator (ICD) or data country code (DCC) format AESA addresses carried in the subaddress fields of the message. The one-to-one translation table allows signalling to look up the E.164 addresses and the AESA addresses in a database, allowing a one-to-one correspondence between AESA addresses and E.164 addresses.

Caution   Manually mapping AESA addresses to E.164 addresses is a time consuming and error prone process. We highly recommend that you use either the E.164 gateway or E.164 autoconversion feature instead of the E.164 one-to-one address translation feature.

For a detailed explanation of how the E.164 translation table feature works, refer to the Guide to ATM Technology.

Configuring one-to-one E.164 translation tables requires the following steps:

Step 2   Configure the translation table.

Step 3   Add entries to the translation table for both the called and calling parties.

To configure E.164 translation on the interface, perform the following steps, beginning in global configuration mode:

Example

The following example shows how to configure the ATM interface 0/0/1 to use the one-to-one E.164 translation table and specifies three table entries:

Displaying the ATM E.164 Translation Table Configuration

To display the ATM E.164 translation table configuration, use the following privileged EXEC commands:

Example

The following example shows how to display the E.164 translation table configuration:

Example

The following example shows how to display the E.164 configuration for ATM interface 0/0/1:

Configuring Signalling Diagnostics Tables

Signalling diagnostics enable you to diagnose a specific call failure in your network and pinpoint the location of the call failure along with the reason for the failure. To do this, you must configure a signalling diagnostics table that stores the filtering criteria and a filter index, an integer value between 1 and 50, used to uniquely identify each set of filtering criteria you select. Each filtering criteria occupies one entry in the signalling diagnostics table. Each entry in the filter table is entered using command-line interface (CLI) commands or Simple Network Management Protocol (SNMP). Then the diagnostics software module, when enabled, filters rejected calls based on the entries in your filter table. A successful match in the filter table causes the rejected call information to be stored for analysis.

Note   Signalling diagnostics is a tool for troubleshooting failed calls and should not be enabled during normal operation of the ATM switch router.

To configure the signalling diagnostics table entries, perform the following steps, beginning in global configuration mode: