cc/td/doc/product/dsl_prod/ios_dsl/rel121
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Configuring Signaling Features

Configuring Signaling IE Forwarding

Configuring E.164 Addresses

Configuring E.164 Gateway

Configuring E.164 Address Autoconversion

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

Configuring Signaling Diagnostics Tables

Configuring Closed User Group Signaling Overview

Configuring Aliases for CUG Interlock Code

Configuring CUG on an Interface

Disabling Signaling on an Interface


Configuring Signaling Features

This chapter describes the signaling features for Cisco DSLAMs with NI-2. It includes these sections:

• Configuring Signaling IE Forwarding

• Configuring E.164 Addresses

• Configuring Signaling Diagnostics Tables

• Configuring Closed User Group Signaling Overview

• Configuring Aliases for CUG Interlock Code

Configuring Signaling IE Forwarding

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

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

To configure an interface signaling IE transfer, perform these steps, beginning in global configuration mode:

Step
Command
Task

1.

interface atm slot/port

Select the interface to be configured.

2.

atm signalling ie forward {aal-info | all | bli-repeat-ind | called-subaddress | calling-number | higher-layer-info | lower-layer-info | unknown-ie}

Configure the signaling information element forwarding.


Example

This example disables signaling of all forwarded IEs on ATM interface 0/0 and displays the result:

DSLAM(config)# interface atm 0/0
DSLAM(config-if)# no atm signalling ie forward all
DSLAM# show running-config
Building configuration...
Current configuration:
!
version XX.X
no service pad
service udp-small-servers
service tcp-small-servers
!
hostname DSLAM

!

<information deleted>

!
interface ATM0/0
   no atm signallling ie forward calling-number
no atm signallling ie forward calling-subaddress
no atm signallling ie forward called-subaddress
no atm signallling ie forward higher-layer-info
no atm signallling ie forward lower-layer-info
no atm signallling ie forward blli-repeat-ind
no atm signallling ie forward aal-info
!
interface ATM0/1
!
interface ATM0/2
!

Configuring E.164 Addresses

E.164 support allows networks that use E.164 ATM address formats (for example, 45.000001234567777F00000000.000000000000.00) to work with networks that use E.164 address formats (for example, 1-123-456-7777). Generally, you can use E.164 ATM addresses in ATM networks, and E.164 addresses in telephone networks.

There are several types of E.164 addresses. The DSLAM supports these E.164 address formats:

•Native E.164—An ASCII address that complies with the International Telecommunications Union (ITU) E.164 specification for international telephone numbers. For example, the number 1-800-555-1212 is encoded as 3138303035353531323132. Native E.164 addresses have these properties:

–Conform to ITU E.164 specification

–Contain 7 to 15 digits

–Decimal digits 0 to 9

–IA5 number, ASCII, 8-bits, MSB = 0

–Result equals one digit per byte

–User-Network Interface (UNI) or Interim Interswitch Signaling Protocol (IISP) support only; Private Network-Network Interface (PNNI) does not support E.164 addresses

These properties are carried in the called and calling party address IEs, which are part of the signaling packets used to set up a call.

•ARB_AESA—a form of ATM End System Address (AESA) with any arbitrary numbering, for example, 47.111111111111111111111111.111111111111.00.

•E164_ZDSP—An E164_AESA address with all zeros after the embedded E.164 number; for example, 45.000001234567777F00000000.000000000000.00. ZDSP means "Zero Domain Specific Part."

•E164_AESA—An AESA address with an embedded E.164 number; for example, 45.000007654321111FDDDDDDDD.CCCCCCCCCCCC.00. The "D" and "C" characters in this example represent an end system address.

Note AESA is an ATM Forum term for ATM address.

There are three features you can configure on the DSLAM for E.164 address conversion. The feature you choose depends on the address format you are using. The features are as follows:

•E.164 gateway—Use this feature when addresses are in ARB_AESA format and a call must traverse an E.164 network.

•E.164 address autoconversion—Use this feature when addresses are in E164_ZDSP or E.164_AESA format and a call must traverse an E.164 network.

•E.164 address one-to-one translation table—Use this feature when you want to create an E.164 to AESA address translation table manually. This feature is not recommended for most networks.

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

Proceed to the appropriate subsection for configuration information.

Configuring E.164 Gateway

If your network uses ARB_AESA, you can configure the E.164 gateway feature. 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.

This section describes how to configure the E.164 gateway feature and includes these procedures:

•Configuring a static ATM route with an E.164 address

•Configuring an E.164 address on an 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.

Signaling uses E.164 addresses in the called and calling party IEs, and uses AESAs in the called and calling party subaddress IEs.

Figure 15-1 illustrates an E.164 gateway configuration.

Figure 15-1 E.164 Gateway Conversion Example

The AESA address is used to initiate the call at the ingress to the public network. The public network routes the call based on the E.164 address. AESA subaddresses are carried through the public network in the subaddress fields. The AESA address is used to complete the call at the egress from the public network.

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.

Configuring an E.164 Address Static Route

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

Command
Task

atm route atm-address-prefix atm slot/port
[e164-address e164-address [number-type {international | local | national | subscriber}]]
[internal] [scope 1-15]

At the configure prompt, configure the static route prefix using the E.164 address.


Example

This example uses the atm route command to configure a static route using the 13-byte switch prefix 47.00918100000000410B0A1081 to ATM interface 0/0 with the E.164 address 1234567 and displays the result (To complete the E.164 address static route configuration, proceed to the "Configuring an ATM E.164 Address on an Interface" section):

DSLAM(config)# atm route 47.00918100000000410B0A1081 atm 0/0 e164-address 7654321
DSLAM# show atm route
Codes: P - installing Protocol (S - Static, P - PNNI, R - Routing control),
T - Type (I - Internal prefix, E - Exterior prefix, SE -
Summary Exterior prefix, SI - Summary Internal prefix,
ZE - Suppress Summary Exterior, ZI - Suppress Summary Internal)
P T Node/Port St Lev Prefix
~ ~~ ~~~~~~~~~~~~~~~~ ~~ ~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
S E 1 ATM0/1 DN 0 47.0091.8100.0000.0001/72
P SI 1 0 UP 0 47.0091.8100.0000.0002.eb1f.fe00/104
R I 1 ATM0/0 UP 0 47.0091.8100.0000.0002.eb1f.fe00.0002.eb1f.fe00/152
R I 1 ATM0/0 UP 0 47.0091.8100.0000.0002.eb1f.fe00.4000.0c/128
P SI 1 0 UP 0 47.0091.8100.0000.0040.0b0a.2b81/104
S E 1 ATM0/0 DN 0 47.0091.8100.0000.0040.0b0a.2b81/104
(E164 Address 1234567)
R I 1 ATM0/0 UP 0 47.0091.8100.0000.0040.0b0a.2b81.0040.0b0a.2b81/152
R I 1 ATM0/0 UP 0 47.0091.8100.0000.0040.0b0a.2b81.4000.0c/128

Configuring an ATM E.164 Address on an Interface

You can configure one E.164 address per ATM port. Signaling 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 these tasks, beginning in global configuration mode:

Step
Command
Task

1.

interface atm slot/port

Select an interface port.

2.

atm e164 address e164-address

Associate the E.164 address to the interface.


Example

This example configures the E.164 address 7654321 on ATM interface 0/1 and displays the result:

DSLAM(config)# interface atm 0/1
DSLAM(config-if)# atm e164 address 7654321
DSLAM# show atm interface atm 0/1

Interface: ATM0/1 Port-type: oc3suni
IF Status: UP Admin Status: up
Auto-config: enabled AutoCfgState: completed
IF-Side: Network IF-type: NNI
Uni-type: not applicable Uni-version: not applicable
Max-VPI-bits: 8 Max-VCI-bits: 14
Max-VP: 255 Max-VC: 16383
Svc Upc Intent: pass Signalling: Enabled
ATM Address for Soft VC: 47.0091.8100.0000.0041.0b0a.1081.4000.0c80.0010.00
ATM E164 Address: 7654321
Configured virtual links:
PVCLs SoftVCLs SVCLs PVPLs SoftVPLs SVPLs Total-Cfgd Installed-Conns
3 0 0 0 0 0 3 3
Logical ports(VP-tunnels): 0
Input cells: 226064 Output cells: 226139
5 minute input rate: 0 bits/sec, 0 cells/sec
5 minute output rate: 0 bits/sec, 0 cells/sec
Input AAL5 pkts: 147608, Output AAL5 pkts: 147636, AAL5 crc errors: 0

When the E.164 gateway feature is configured, the DSLAM first attempts to make a connection using the E.164 gateway feature. If that connection fails, the DSLAM attempts to make the connection using the E.164 address autoconversion feature. Proceed to the next section for configuration instructions.

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.

The E.164 portion of an E.164 ATM address is the first 15 digits following the authority and format identifier (AFI) of 45, shown in Figure 15-2.

Figure 15-2 E.164 Portion of an E.164 ATM Address

The E.164 portion is right-justified and ends with an "F." If all fifteen digits are not being used, the unused digits are filled with zeroes. In Figure 15-2, the embedded E.164 number is 1234567777, but it is signaled at the egress of the DSLAM and in the E.164 public network as 31323334353637373737.

The autoconversion process differs slightly between the E164_ZDSP and E164_AESA address formats. Table 15-1 compares the E.164 address autoconversion process by address type. The main difference between the two types is the way the IEs are signaled at the egress of the DSLAM, as described in the second row of Table 15-1. Note that during the final conversion process, the calling AESA and called AESA return to their original values.

Table 15-1 E164_ZDSP and E164_AESA Address Autoconversion Comparison

Action
E164_ZDSP
E164_AESA

Originates as

Calling AESA: 45.000001234567777F00000000.000000000000.00

Calling subaddress: None

Called AESA: 45.000007654321111F00000000.000000000000.00

Called subaddress: None

Calling AESA: 45.000001234567777FAAAAAAAA.BBBBBBBBBBBB.00

Calling subaddress: None

Called AESA: 45.000007654321111FCCCCCCCC.DDDDDDDDDDDD.00

Called subaddress: None

Signaled at egress of DSLAM as

Calling E.164: 31323334353637373737

Calling subaddress: None

Called E.164: 37363534333231313131

Called subaddress: None

Calling E.164: 31323334353637373737

Calling subaddress: 45.0000012345677777FAAAAAAAA.BBBBBBBBBBBB.00

Called E.164: 37363534333231313131

Called subaddress: 45.000007654321111FCCCCCCCC.DDDDDDDDDDDD.00

Converted back at ingress of DSLAM to

Calling AESA: 45.000001234567777F00000000.000000000000.00

Calling subaddress: None

Called AESA: 45.000007654321111F00000000.000000000000.00

Called subaddress: None

Calling AESA: 45.000001234567777FAAAAAAAA.BBBBBBBBBBBB.00

Calling subaddress: None

Called AESA: 45.000007654321111FCCCCCCCC.DDDDDDDDDDDD.00

Called subaddress: None


Figure 15-3 shows an example of an E164_ZDSP address autoconversion.

Figure 15-3 E164_ZDSP Sample Address Autoconversion

In Figure 15-3, a call (connection) from end system A is placed to end system B on the other side of an E.164 public network. The call originates as an E.164 ATM address and is signaled in native E.164 format at the egress port of DSLAM switch A and within the E.164 public network. When the call reaches the ingress port of DSLAM switch B, at the edge of the E.164 public network, the call is converted back to E.164 ATM address format.

Note The DSLAM routes calls based on the E.164 ATM address (not the native E.164 address).

Figure 15-4 shows an example of an E164_AESA address autoconversion.

Figure 15-4 E164_AESA Address Autoconversion Example

In Figure 15-4, a call from end system A is placed to end system B on the other side of an E.164 public network. The call originates as an E.164 ATM address and at the egress port of DSLAM switch A and within the E.164 public network:

•The E.164 ATM address is signaled in native E.164 format.

•The called party address (45.000007654321111F...) IE is included in the called party subaddress IE.

•The calling party address (45.000001234567777F...) IE is included in the calling party subaddress IE.

When the call reaches the ingress port of DSLAM switch B, at the edge of the E.164 public network, the call is converted back to E.164 ATM address format and:

•The native E.164 address is converted back to an E.164 ATM address.

•The called party subaddress (45.000007654321111F...) IE is returned to the called party address IE.

•The calling party subaddress (45.000001234567777F...) IE is returned to the calling party address IE.

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.

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 these steps, beginning in global configuration mode:

Step
Command
Task

1.

atm route atm-address-prefix atm slot/port
[e164-address e164-address [number-type {international | local | national | subscriber}]]
[internal] [scope 1-15]

At the configure prompt, configure the static route prefix with the E.164 address.

2.

interface atm slot/port

Select the ATM interface.

3.

atm e164 auto-conversion

Configure E.164 autoconversion.

4.

exit

Return to global configuration mode.


Examples

Command
Task
DSLAM(config)# atm route 45.000007654321111F atm 0/1
DSLAM(config)# int atm 0/1
DSLAM(config-if)# atm e164 auto-conversion

Configure interface 0/1 of DSLAM switch A in the example networks shown in Figure 15-3 and Figure 15-4.

DSLAM(config)# atm route 45.000001234567777F atm 0/1
DSLAM(config)# int atm 0/1
DSLAM(config-if)# atm e164 auto-conversion

Configure interface 0/1 of DSLAM switch B.

DSLAM# show atm interface atm 0/1

Interface: ATM0/1 Port-type: oc3suni
IF Status: DOWN Admin Status: down
Auto-config: disabled AutoCfgState: not applicable
IF-Side: Network IF-type: UNI
Uni-type: Private Uni-version: V3.0
Max-VPI-bits: 8 Max-VCI-bits: 14
Max-VP: 255 Max-VC: 16383
ConfMaxSvpcVpi: 255 CurrMaxSvpcVpi: 255
ConfMaxSvccVpi: 255 CurrMaxSvccVpi: 255
ConfMinSvccVci: 33 CurrMinSvccVci: 33
Svc Upc Intent: pass Signalling: Enabled
ATM Address for Soft VC: 47.0091.8100.0000.0002.eb1f.fe00.4000.0c80.0010.00
ATM E164 Auto Conversion Interface
Configured virtual links:
PVCLs SoftVCLs SVCLs TVCLs PVPLs SoftVPLs SVPLs Total-Cfgd Inst-Conns
2 0 0 0 0 0 0 2 0
Logical ports(VP-tunnels): 0
Input cells: 0 Output cells: 0
5 minute input rate: 0 bits/sec, 0 cells/sec
5 minute output rate: 0 bits/sec, 0 cells/sec
Input AAL5 pkts: 0, Output AAL5 pkts: 0, AAL5 crc errors: 0

Display the E.164 configuration for ATM interface 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 signaling, with ARB_AESA addresses carried in the subaddress fields of the message.

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

The one-to-one translation table allows signaling to look up the E.164 addresses and the ARB_AESA addresses in a database, allowing a one-to-one correspondence between ARB_AESA addresses and E.164 addresses.

During egress operation, when a signaling message attempts to establish a call out an interface, the called and calling party addresses are in ARB_AESA format.

If the interface has been configured for E.164 translation, signaling attempts to find a match for the ARB_AESA addresses. If found, the E.164 addresses corresponding to the ARB_AESA addresses are placed into the called and calling party addresses. The original ARB_AESA addresses are also placed into the called and calling party subaddresses.

•During ingress operation, if the interface is configured for E.164 translation, the called and calling party addresses are in E.164 format.

•If the original ARB_AESA-formatted called and calling addresses have been carried in subaddresses, then those addresses are used to forward the call.

•If subaddresses are not present due to the network blocking them, or to the switch at the entry to the E.164 network not using subaddresses, signaling attempts to find a match for the ARB_AESA address in the ATM E.164 translation table.

•If matches are found, the ARB_AESA addresses corresponding to the E.164 addresses in the translation table will be placed into the called and calling party addresses. The call is then forwarded using the ARB_AESA addresses.

To configure a one-to-one E.164 translation table:

Step 1 Configure specific ATM interfaces to connect to E.164 public networks to use the translation table.

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 these steps, beginning in global configuration mode:

Step
Command
Task

1.

interface atm slot/port

Select an interface port.

2.

atm e164 translation

Configure the ATM E.164 interface.

3.

exit

Return to EXEC configuration mode.

4.

atm e164 translation-table

Change to E.164 ATM configuration mode.

5.

e164 address address nsap-address1 nsap_address

Configure the E.164 translation table.

1 The NSAP address is the same as the ARB_AESA address.


Examples

This example shows how to configure the ATM interface 0/1 to use the one-to-one E.164 translation table:

DSLAM(config)# interface atm 0/1
DSLAM(config-if)# atm e164 translation
DSLAM(config-if)# exit
DSLAM(config)# atm e164 translation-table
DSLAM(config-atm-e164)# e164 address 1111111 nsap-address 11.111111111111111111111111.112233445566.11
DSLAM(config-atm-e164)# e164 address 2222222 nsap-address 22.222222222222222222222222.112233445566.22
DSLAM(config-atm-e164)# e164 address 3333333 nsap-address 33.333333333333333333333333.112233445566.33

These commands:

1. Change to interface configuration mode for ATM interface 0/1.

2. Enable ATM E.164 translation on the interface.

3. Exit interface configuration mode.

4. Change to ATM E.164 configuration mode.

5. Add the E.164 address 1111111 to the ARB_AESA address 11.11111... translation table entry.

6. Add the E.164 address 2222222 to the ARB_AESA address 22.22222... translation table entry.

7. Add the E.164 address 3333333 to the ARB_AESA address 33.33333... translation table entry.

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

DSLAM# show running-config
Building configuration...

Current configuration:
!
version XX.X
no service pad
service udp-small-servers
service tcp-small-servers
!
hostname DSLAM
!
!
username dtate
!
atm e164 translation-table
e164 address 1111111 nsap-address 11.111111111111111111111111.112233445566.11
e164 address 2222222 nsap-address 22.222222222222222222222222.112233445566.22
e164 address 3333333 nsap-address 33.333333333333333333333333.112233445566.33
!
atm service-category-limit cbr 64544
atm service-category-limit vbr-rt 64544
atm service-category-limit vbr-nrt 64544
atm service-category-limit ubr 64544
atm address 47.0091.8100.0000.0040.0b0a.2b81.0040.0b0a.2b81.00
--More--
<information deleted>

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

DSLAM# show atm interface atm 0/1
Interface: ATM0/1 Port-type: oc3suni
IF Status: DOWN Admin Status: administratively down
Auto-config: enabled AutoCfgState: waiting for response from peer
IF-Side: Network IF-type: UNI
Uni-type: Private Uni-version: V3.0
Max-VPI-bits: 8 Max-VCI-bits: 14
Max-VP: 255 Max-VC: 16383
Svc Upc Intent: pass Signalling: Enabled
ATM Address for Soft VC: 47.9999.9999.0000.0000.0000.0216.4000.0c80.0010.00
ATM E164 Translation Interface
Configured virtual links:
PVCLs SoftVCLs SVCLs PVPLs SoftVPLs SVPLs Total-Cfgd Installed-Conns
2 0 0 0 0 0 2 0
Logical ports(VP-tunnels): 0
Input cells: 0 Output cells: 0
5 minute input rate: 0 bits/sec, 0 cells/sec
5 minute output rate: 0 bits/sec, 0 cells/sec
Input AAL5 pkts: 0, Output AAL5 pkts: 0, AAL5 crc errors: 0

Configuring Signaling Diagnostics Tables

Use signaling diagnostics 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:

1. Configure a signaling 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 signaling diagnostics table. Each entry in the filter table is entered using command-line interface (CLI) commands or Simple Network Management Protocol (SNMP).

2. Then the diagnostics software module, when enabled, filters rejected calls based on the entries in your filter table.

3. A successful match in the filter table causes the rejected call information to be stored for analysis.

Note Signaling diagnostics is a tool for troubleshooting failed calls and should not be enabled during normal DSLAM operation.

To configure the signaling diagnostics table entries, perform these tasks, beginning in global configuration mode:

Step
Command 
Task

1.

atm signalling diagnostics enable

Enable ATM signaling diagnostics

2.

atm signalling diagnostics index

Change to ATM signaling diagnostics configuration mode.

3.

age-timer seconds

Configure the timeout value for the entry, in seconds.

4.

calling-address-mask nsap_address_mask2

Configure a filtering criteria based on the calling address mask value to be used to identify the valid bits of the calling NSAP address of the rejected call.

5.

called-nsap-address nsap_addrress

Configure a filtering criteria based on the called NSAP address of the rejected call.

6.

called-address-mask nsap_address_mask1

Configure a filtering criteria based on the called address mask value used to identify the valid bits of the calling NSAP address of the rejected call.

7.

calling-nsap-address nsap_address

Configure a filtering criteria based on the calling NSAP address of the rejected call.

8.

cast-type {p2p | p2mp | all}

Configure a filtering criteria based on the cast type of the rejected call. (The default is all.)

9.

clear-cause number2

Configure a filtering criteria based on the cleared cause code of the rejected call.

10.

connection-category {soft-vc | soft-vp | reg-vc | all}

Configure a filtering criteria based on the VC connection category of the rejected call.

11.

incoming-port atm slot/port

Configure a filtering criteria based on the incoming port of the rejected call.

12.

max-records number

Configure the maximum number of entries to be stored in the display table for each of the entries in the filter table.

13.

outgoing-port atm slot/port

Configure a filtering criteria based on the outgoing port of the rejected call.

14.

purge

Purge all the filtered records in the filter table.

15.

scope {internal | external}

Configure a filtering criteria based on the scope of the rejected call which either failed internally in the DSLAM or externally on other DSLAMs or switches.

16.

service-category {cbr | vbr-rt | vbr-nrt | ubr | all}

Configure a filtering criteria based on the service category of the rejected call.

17.

status [active filter_criteria | inactive filter_criteria | delete filter_criteria]

Configure the status of the entry in the filter table.

1 The combination of the configured calling_addr_mask (called_address_mask) and the configured calling_nsap_address (called_nsap_address) are used to filter the rejected call.

2 You can obtain the cause code values from the ATM forum UNI 3.1 specification.


The display table contains the records that were collected based on every filtering criteria in the filter table. Each filtering criteria has only a specified number of records that are stored in the table. After that specified number of records is exceeded, the table is overwritten.

Examples

Example 
Task
DSLAM(config)# atm signalling diagnostics enable

Enable signaling diagnostics on the DSLAM.

DSLAM(config)# atm signalling diagnostics 1
DSLAM(cfg-atmsig-diag)# service-category cbr
DSLAM(cfg-atmsig-diag)# service-category ubr
DSLAM(cfg-atmsig-diag)# service-category ubr

Configure filter criteria in signaling diagnostics index 1 for call failures based on the service category.

DSLAM(config)# atm signalling diagnostics 1
DSLAM(cfg-atmsig-diag)# connection-category soft-vc
DSLAM(cfg-atmsig-diag)# connection-category soft-vc soft-vp

Configure filter criteria for call failures based on the category of the virtual circuit.

DSLAM(config)# atm signalling diagnostics 1
DSLAM(cfg-atmsig-diag)# cast-type p2p p2mp

Configure filter criteria for calls rejected based on the connection type.

DSLAM(config)# atm signalling diagnostics 1
DSLAM(cfg-atmsig-diag)# scope internal

Configure filter criteria for calls that failed internally in the DSLAM.

DSLAM(config)# atm signalling diagnostics 1
DSLAM(cfg-atmsig-diag)# incoming-port ATM0/2

Configure the filter entry for filtering failed calls that came in through interface ATM0/2.

DSLAM(config)# atm signalling diagnostics 1
DSLAM(cfg-atmsig-diag)# outgoing-port ATM0/2

Configure the filter entry for filtering failed calls that went out through interface ATM0/2.

DSLAM(config)# atm signalling diagnostics 1
DSLAM(cfg-atmsig-diag)# clearcause 3

Configure the filter entry for filtering failed calls based on the clear cause value 3 (destination unreachable).

DSLAM(config)# atm signalling diagnostics 1
DSLAM(cfg-atmsig-diag)# calling-nsap-address 47.0091810000000061705BD901.010203040506.0.

Configure filter criteria for calls rejected based on the calling NSAP address of the call.

DSLAM(config)# atm signalling diagnostics 1
DSLAM(cfg-atmsig-diag)# called-nsap-address 47.0091810000000061705BD901.010203040506.0

Configure filter criteria for calls rejected based on the called NSAP address of the call.

DSLAM(config)# atm signalling diagnostics 1
DSLAM(cfg-atmsig-diag)# called-address-mask ff.ff.ff.00

Configure filter criteria for calls rejected based on the called address mask of the call.

DSLAM(config)# atm signalling diagnostics 1
DSLAM(cfg-atmsig-diag)# calling-address-mask ff.ff.ff.00

Configure filter criteria for calls rejected based on the calling address mask of the call.

DSLAM(config)# atm signalling diagnostics 1
DSLAM(cfg-atmsig-diag)# age-timer 3600

This example shows how to specify the timeout value for the entry in seconds:

DSLAM(config)# atm signalling diagnostics 1
DSLAM(cfg-atmsig-diag)# purge

Purge all the filtered records corresponding to this entry in the filter table.

DSLAM(config)# atm signalling diagnostics 1
DSLAM(cfg-atmsig-diag)# status delete

Delete an index entry in the filter table.

DSLAM(config)# atm signalling diagnostics 1
DSLAM(cfg-atmsig-diag)# max-records 40

Specify the maximum number of entries to be stored in the display table for each of the entries in the filter table

DSLAM# show atm signalling diagnostics record 1
D I S P L A Y I N D E X 1
--------------------------------
Scope: internal, Cast Type: p2p, Conn Indicator: Setup Failure
Connection Kind: switched-vc
Service Category: UBR (Unspecified Bit Rate)
Clear Cause: 0x29, Diagnostics: NULL
Incoming Port: ATM0/2, Outgoing Port:ATM0/1
Calling-Address: 47.009181000000006011000000.470803040506.00
Calling-SubAddr: NULL
Called-Address : 47.009181000000006083C42C01.750203040506.00
Called-SubAddr : NULL
Crankback Type : No Crankback
DTL's :
NodeId:56:160:47.009181000000006011000000.006083AB9001.00 Port: 0/1:2
NodeId:56:160:47.00918100000000603E7B4101.00603E7B4101.00 Port: 0/0:2
NodeId:56:160:47.009181000000006083C42C01.006083C42C01.00 Port: 0

Display the signaling diagnostic records for index 1.

DSLAM# show atm signalling diagnostics filter 1
F I L T E R I N D E X 1
------------------------------
Scope: internal, Cast Type: p2mp
Connection Kind: soft-vc
Service Category: CBR (Constant Bit Rate) UBR (Unspecified Bit Rate)
Clear Cause: 0, Initial TimerValue: 600
Max Records: 20, NumMatches: 0, Timer expiry: 600
Incoming Port: ATM0/1, Outgoing Port: ATM0/2
Calling Nsap Address:47.111122223333444455556666.777788889999.00
Calling Address Mask:FF.FFFFFF000000000000000000.000000000000.00
Called Nsap Address :47.111122223333444455556666.777788889999.01
Called Address Mask :FF.FFFFFF000000000000000000.000000000000.00
Status : active

Display the signaling diagnostics data for filter index 1.

DSLAM# show atm signalling diagnostics status
Signaling diagnostics disabled globally

Display the signaling diagnostics status.


Configuring Closed User Group Signaling Overview

You can configure a closed user group (CUG) to form restricted access groups (virtual private networks). You can define different CUGs and a specific user can be a member of one or more CUGs. Members of a CUG can communicate among themselves, but not with users outside the group. Specific users can have additional restrictions that prevent them from originating or receiving calls from other members of the CUG. You can also specify additional restrictions on originating and receiving calls to or from members of other CUGs.

For example, if you configure three CUGs (A, B, and C) in your network, you can configure them so that groups B and C can communicate with group A without restriction, but groups B and C cannot communicate between each other.You can also configure specific members of the same group to not accept calls from members of the same group.

The basis for CUGs are interlock codes. Interlock codes are:

•Unique in the whole network. Members belonging to a CUG are assigned a unique interlock code. Members of CUGs will use this interlock code while communicating with other members of the same or different CUGs.

•Passed in CUG interlock code information element (CUG IC IE). The CUG IE also carries information that specifies whether the call can go through if the called party is not a member of the specified CUG.

At the network boundary where the call originates, when a call is received from the user, the DSLAM or switch generates the CUG IE and sends it as part of the SETUP message. In this software release, the CUG IE can only contain the preferential CUG's interlock code. The CUG IE is used at the destination network interface to determine if the call should be forwarded or rejected. The CUG IE is forwarded transparently by the intermediate DSLAMs or switches.

Note End systems do not have any knowledge of interlock codes.

Two types of interlock codes are defined:

•Global interlock code is 24 bytes long and consists of a globally unique ATM End System Address (AESA) used to identify the network administering the CUG, followed by a 4-byte suffix assigned to this CUG by the network administration.

•International interlock code is 4 bytes long and consists of 4 binary coded decimal (BCD) digits containing a country code and network code, followed by a 2-byte suffix assigned to this CUG by the network administration.

Note Cisco only supports the 24-byte interlock code.

Figure 15-5 provides examples of CUGs and consists of these components:

•Members of CUG I: U1,U2, U4

•Members of CUG J: U3, U6, U7

•Members of CUG K: U6, U7, U8, U9, U10

•U11, U12 do not belong to any closed user groups

•Some of the members of CUG J (U6 and U7) also belong to CUG K

Figure 15-5 Closed User Groups

Two CUG calls shown in Figure 15-5 are:

•A call from U1 to U10 is an inter-CUG call since both users belong to different groups with different CUG interlock codes. The call is rejected at the switch connected to U10 if either the interface to U10 is not configured to accept calls from other groups, or the interface from the originating switch to U1 is not configured to allow origination of calls to other groups.

•A call from U1 to U2 is an intra-CUG call, since both users belong to the same group with the same CUG interlock code. The call is accepted at the switch connected to U2, unless the configuration of CUG I on the interface to U2 specifies that calls from the same group should not be accepted.

Configuring Aliases for CUG Interlock Code

You can define an alias for each CUG interlock code used on the DSLAM. Using an alias can simplify configuration of a CUG on multiple interfaces. When you use an alias, you no longer need to specify the 48-hexadecimal-digit CUG interlock code on each interface attached to a CUG member.

To configure an alias for a CUG interlock code, use this command in global configuration mode:

Command
Task

atm signalling cug alias alias_name interlock-code interlock_code

Configure the alias for the CUG interlock code.


Example

This example shows how to configure the alias TEST for the CUG interlock code 4700918100000000603E5A790100603E5A790100.12345678:

DSLAM(config)# atm signalling cug alias TEST interlock-code 4700918100000000603E5A790100603E5A790100.12345678

Configuring CUG on an Interface

This section describes how to configure CUG on interfaces.

To perform CUG configuration:

Step 1 Identify the access interfaces. Transmission and reception of CUG interlock codes is not allowed over access interfaces. Configuring all interfaces leading outside of the network as access interfaces ensures that all CUG interlock codes are generated and used only within this network. You implement CUG procedures only if you configure the interface as an access interface.

Step 2 Configure each access interface to permit or deny calls either from users attached to this interface or to unknown users that are not members of this interface's CUGs. In International Telecommunications Union Telecommunications Standardization Sector (ITU-T) terminology, this is called outgoing access. Similarly, each access interface can be configured to permit or deny calls either to the users attached to this interface or from unknown users that are not members of this interface's CUGs. In ITU-T terminology, this is called incoming access.

Note Interfaces to other networks should be configured as CUG access interfaces, even if no CUGs are configured on the interface. In this case, if you want the DSLAM to exchange SVCs with the neighbor network, calls to and from unknown users should be permitted on the interface.

Step 3 Configure each access interface to have one or more CUGs associated with it, but only one CUG can be selected as the preferential CUG. In this software release, calls received from users attached to this interface can only be associated with the preferential CUG. Calls destined to users attached to this interface can be accepted based on membership in any of the CUGs configured for the interface.

Note You can configure CUG service without any preferential CUG. If a preferential CUG is not configured on the interface, and calls from users attached to this interface to unknown users are permitted, the calls will proceed as non-CUG calls, without generating any CUG IEs.

For each CUG configured on the interface, you can specify that calls to or from other members of the same CUG be denied. In ITU-T terminology, this is called outgoing-calls-barred (OCB) and incoming-calls-barred (ICB), respectively.

Table 15-2 describes the relationship between the ITU-T CUG terminology and Cisco CUG terminology.

Table 15-2 Cisco CUG and ITU-T CUG Terminology Conversion

ITU-T CUG Terminology
Cisco CUG Terminology

preferential CUG

preferential

incoming access allowed

permit-unknown-cugs to-user

outgoing access allowed

permit-unknown-cugs from-user

incoming calls barred (ICB)

deny-same-cug to-user

outgoing calls barred (OCB)

deny-same-cug from-user


To configure an access interface and the CUG in which the interface is a member, perform these tasks, beginning in global configuration mode:

Step
Command
Task

1.

interface atm slot/port

Specify an ATM interface and enter interface configuration mode.

2.

atm signalling cug access [permit-unknown-cugs {to-user | from-user permanent | both-direction permanent}]

Configure the interface as a CUG access interface.

3.

atm signalling cug assign {alias alias_name | interlock-code interlock_code} [deny-same-cug {to-user | from-user}] [preferential]

Configure the CUG where this interface is a member.


Example

This example shows how to configure an interface as a CUG access interface and assign a preferential CUG and displays the result:

DSLAM(config)# interface atm 0/1
DSLAM(config-if)# atm signalling cug access permit-unknown-cugs both-direction permanent
DSLAM(config-if)# atm signalling cug assign interlock-code 4700918100000000603E5A790100603E5A790100.12345678 preferential

To display the global CUG configuration, use these EXEC commands:

Command
Task

show atm signalling cug
[interface atm slot/port]
[access | alias alias-name | interlock-code interlock_code]

Display the CUG interface configuration status.

show running-config

Display the CUG global configuration status.


Examples

Example
Task
DSLAM# show atm signalling cug
Interface: ATM0/1
Cug Alias Name:
Cug Interlock Code: 4700918100000000603E5A790100603E5A790100.12345678
Non preferential Cug
Permit Network to User Calls
Permit User to Network Calls

Display the global CUG configuration using the show atm signalling cug EXEC command.

DSLAM# show atm signalling cug access
Closed User Group Access Interface Parameters:

Interface: ATM0/1
Network To User (incoming) access: Permit calls from unknown CUGs to User
User To Network (outgoing) access: Permit permanent calls to unknown groups

Display the global CUG access configuration using the show atm signalling cug access command.

DSLAM# show running-config
Building configuration...
Current configuration:
!
version XX.X
no service pad
service udp-small-servers
service tcp-small-servers
!
hostname DSLAM
!
!
atm signalling cug alias TEST interlock-code 47.0091810000000061705BDA01.0061705BDA01.00.123456 78
!
atm address 47.0091.8100.0000.0061.705b.da01.0061.705b.da01.00

<information deleted>

!
interface ATM0/0
atm signalling cug access permit-unknown-cugs both-direction permanent
!
<information deleted>

Display the CUG global configuration using the show running-config command.


To display the ATM signaling statistics, use the EXEC command:

Command
Task

show atm signalling statistics

Display the ATM signaling statistics.


Example

This example displays the ATM signaling statistics:

DSLAM# show atm signalling statistics
Global Statistics:
Calls Throttled: 0
Max Crankback: 3
Max Connections Pending: 255
Max Connections Pending Hi Water Mark: 1
ATM 0/0:0 UP Time 01:06:20 # of int resets: 0
----------------------------------------------------------------
Terminating connections: 0 Soft VCs: 0
Active Transit PTP SVC: 0 Active Transit MTP SVC: 0
Port requests: 0 Source route requests: 0
Conn-Pending: 0 Conn-Pending High Water Mark: 1
Calls Throttled: 0 Max-Conn-Pending: 40
Messages: Incoming Outgoing
--------- -------- --------
PTP Setup Messages: 0 0
MTP Setup Messages: 0 0
Release Messages: 0 0
Restart Messages: 0 0
Message: Received Transmitted Tx-Reject Rx-Reject
Add Party Messages: 0 0 0 0
Failure Cause: Routing CAC Access-list Addr-Reg Misc-Failure
Location Local: 0 0 0 0 12334
Location Remote: 0 0 0 0 0
ATM 0/2:0 UP Time 3d21h # of int resets: 0
----------------------------------------------------------------
Terminating connections: 0 Soft VCs: 0
Active Transit PTP SVC: 0 Active Transit MTP SVC: 0
Port requests: 0 Source route requests: 0
Conn-Pending: 0 Conn-Pending High Water Mark: 0
Calls Throttled: 0 Max-Conn-Pending: 40

<information deleted>

Disabling Signaling on an Interface

If you disable signaling on a PNNI interface, PNNI routing is also disabled and ILMI is automatically restarted each time signaling is enabled or disabled.

To disable signaling on an interface, perform these tasks, beginning in global configuration mode:

Step
Command
Task

1.

interface atm slot/port

Select the interface to be configured.

2.

no atm signalling enable

Disable signaling on the interface.


Example

This example shows how to disable signaling on ATM interface 0/1:

DSLAM(config)# interface atm 0/1
DSLAM(config-if)# no atm signalling enable
DSLAM(config-if)#
%ATM-5-ATMSOFTSTART: Restarting ATM signalling and ILMI on ATM0/1.

hometocprevnextglossaryfeedbacksearchhelp

Posted: Fri Dec 3 13:54:50 PST 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.