Table of Contents

Terminology
System Overview

Traffic-Based Sizing
System Components

Hardware Installation of System Chassis

Network Access Servers

Cisco AS5200 Universal Access Server
Cisco AS5300 Universal Access Server
Cisco AS5800 Universal Access Server

Cisco LS1010
Cisco Signaling Controllers

System Connections
Upgrading the Access Server for New Releases of Software or Portware

Install a TFTP Application on the PC
Connect PC and Access Server
Establish HyperTerminal Session
Ping PC and Access Server
Download Software on Access Server
Download Portware to Access Server

Software Configuration

Configuring the Cisco LS1010

Sample Configuration
Verify

Configuring the NAS

Additional Reference Documentation
Sample Configurations

Setting Up Continuity Testing in the NAS (Optional)
Configuring the Cisco SC2200 Signaling Controller

If You Need More Information
Cisco Connection Online

Cisco SS7 Dial Access Solution System Integration---Release 1

This document provides an overview of a Signaling System 7 (SS7) dial access solution using the Cisco Signaling Controller SC2200 connected by way of an M1/0 multiplexer to the Cisco AS5200, Cisco AS5300, or Cisco AS5800 universal access server. This document also includes basic configuration information and sample configurations for a dial access solution. For detailed installation and configuration procedures for the various components, refer to the installation and configuration guides for the components.

The Cisco SC2200 uses SS7 signaling to build a point of presence (POP) without concentrating traffic through a legacy circuit-switch. The access servers connect to the SS7 signaling network so that dial-up calls are routed to the access servers in the same way that calls are routed to a service provider's PBX.

The following sections are included in this document:

• Terminology

• System Overview

  • Traffic-Based Sizing

  • System Components

• Hardware Installation of System Chassis

  • Network Access Servers

  • Cisco LS1010

  • Cisco Signaling Controllers

• System Connections

• Upgrading the Access Server for New Releases of Software or Portware

• Software Configuration

  • Configuring the Cisco LS1010

  • Configuring the NAS

  • Configuring the Cisco SC2200 Signaling Controller

• If You Need More Information

• Cisco Connection Online

Terminology

Table 1: Terminology

Acronym	Description
AAA	A software application that provides authentication, authorization, and accounting for system and network resources.
A-link	SS7 Access Link. A dedicated SS7 signaling link not physically associated with any particular link carrying traffic.
ASP	Auxiliary Signal Path. A link between signaling controllers that allows them to exchange signaling information that is incompatible with the PSTN backbone network protocol; used to provide feature transparency.
CLI	Command Language Interface; the basic Cisco IOS configuration and management interface.
COT	Continuity Test. A test used to verify that an SS7 bearer circuit is functioning correctly; generally involves a combination of tone generation, tone detection, and loopback circuitry to verify physical continuity of a circuit; COT may be invoked automatically by network elements in an SS7 network.
DS0	A 64-Kbps digital TDM channel used for carrying a single POTS call.
DS0A	A 56-Kbps digital channel, running over twisted-pair, with an included composite clock signal; One of the styles of SS7 physical interfaces used in North America.
DSP	Digital Signal Processor. Many firmware functions of a NAS are performed by DSPs which are generally provisioned as banks of shared resources among all the DS0s. Typical DSP functions include: Data modems, voice CODECs, fax modems and CODECs, and low-level signaling (such as CAS/R2).
Feature Transparency	A way of passing special feature requests from one PBX to another, using a signaling controller on each side of the PSTN. Without feature transparency, feature requests would be lost if the PSTN backbone protocol did not support them.
F-link	SS7 Fully associated link. An SS7 signaling link directly associated with a link carrying traffic.
Gatekeeper	The component of an ITU-T H.323 conferencing system which performs call address resolution, admission control, and subnet bandwidth management.
ISP	Internet Service Provider.
ISUP	Integrated Services Digital Network User Part. The call control part of the SS7 Protocol, it determines the procedures for setting up, coordinating, and taking down trunk calls on the SS7 network.
IXC	Inter-Exchange Carrier.
LEC	Local Exchange Carrier.
MDL	Message Definition Language. A high-level language used to specify protocols and protocol conversion operations on the signaling controller system.
MML	The signaling controller Man-Machine Language.
NAS	Network Access Server. A Cisco platform (or collection of platforms such as an AccessPath system) that interfaces between the packet world (for example, the Internet) and the circuit world (e.g., the PSTN).
POP	Point-of-presence. A location where two service providers (for example, an ISP and a LEC) co-locate and interconnect equipment.
POTS	Plain Old Telephone Service.
PSTN	Public Switched Telephone Network.
RAS	Registration, Admission, and Status protocol. the protocol used in the ITU-T H.323 protocol suite for discovering and interacting with a Gatekeeper.
SAS	Signaling Access Server. Also called a signaling controller. A server based on TransPath system technology that interfaces between the NAS and the SS7 signaling network.
SCP	Service Control Point. SCPs are database applications that provide information necessary for special call processing and routing, including 800 and 900 call services, credit card calls, local number portability, and advanced call center applications.
SSP	Service Switching Point. Telephone switches (Class 5 end offices or Class 4 tandems) equipped with SS7 software and signaling links are designated as SSPs. They originate, terminate, or transit switch calls based on SS7 signaling procedures through interaction with STPs, SCPs, and other SSPs. The combined NAS/signaling controller dial solution system looks like one or more SSPs to the SS7 network.
STP	Signal Transfer Point. STPs receive and route incoming signaling messages toward the appropriate destination. They function as packet switches, terminating the 56 to 64-kbps SS7 (packet data) signaling links.
TDM	Time Division Multiplexing. Technique in which information from multiple channels can be allocated bandwidth on a single wire based on preassigned time slots. Bandwidth is allocated to each channel regardless of whether the station has data to transmit.
TIOS	TransPath (signaling controller) I/O Subsystem. A set of hardware and software components on the signaling controller that generally maintain the lower levels of the OSI reference model for protocols supported by the signaling controller.
VoIP	Voice over IP. The ability to carry normal telephony-style voice over an IP-based Internet with POTS-like functionality, reliability, and voice quality.
XE	Execution Environment. A layer of software that provides shared services for all application software on the signaling controller system; and isolates higher-level software from operating system dependencies.

System Overview

Figure 1 shows the setup for a typical SS7 dial access solution.

Figure 1: SS7 Dial Access Solution

Traffic-Based Sizing

This section discusses how to calculate your network usage. It is important not only to understand your network's capacity today but also to know your call processing requirements for the future so that you can plan your network for the future demands now. You need to take in many factors when calculating network usage and we have provided a very simple formula to help you determine how many calls are being processed by your network so that we can fulfill your needs in a timely manner.

When you use the Cisco SC2200 Signaling Controller to translate Primary Rate Interfaces of one variant to another, the relationship is a one-to-one relationship, that is, DPNSS to ETSI requires that there be the same number of incoming and outgoing T1/E1s D channels. This does not hold true for C7/SS7 conversion to another protocol, such as DPNSS or ETSI. See the following sections for details.

Netra 1100

If you are using the Netra 1100, one SS7 Link Input to the Cisco SC2200 Signaling Controller can control 24 times the number of cards (maximum of two cards). This is the number of T1s that receive the D channel output of Transpath. For example, you can have one SS7/C7 link on Card 1 (one card can have up to 4 SS7/C7 links) and you can use Card 2 for D Channel output (DPNSS).

With this scenario Card 2's output can control up to 24 T1s (24 channels on the T1 card). If you are using two cards, this means that the maximum number of DS0s is 48 T1s * 23 DS0s = 1104 (note that one DS0 Blocked for insertion of the D channel on the trunk side), as shown in Table 2.

Table 2: Maximum Number of T1 Links

Card One	Card Two	Card Three	Total # of T1s	Max # of DS0s
SS7/C7 Link	24 D channels	--	24 T1s	552
SS7/C7 Link	24 D channels	24 D channels	48 T1s	1104

For E1s the multiplier is 30 times the number of cards, as shown in Table 3.

Table 3: Maximum Number of E1 Links

Card One	Card Two	Card Three	Total # of E1s	Max # of DS0s
SS7/C7 Link	31 D channels	--	31 T1s	930
SS7/C7 Link	31 D channels	31 D channels	62 T1s	1860

E450

If you are using the E450, one SS7 Link Input to the Cisco SC2200 Signaling Controller can control 24 times the number of cards (maximum of seven cards). This is the number of T1s that receive the D channel output of the Cisco SC2200 Signaling Controller. You can place two SS7/C7 links on a Cisco SC2200 Signaling Controller and have them on separate cards. If you are using the maximum number of cards permitted in the E450, you can then use the five cards for the PRI D channel output.

For T1s, the five cards can control 5 * 24 T1s = 120 T1s or 2760 DS0s, as shown in Table 4.

Table 4: Maximum Number of T1 Links

Card 1	Card 2	Card 3	Card 4	Card 5	Card 6	Card 7	Total # of T1s	Total # of DS0s
SS7/C7	24 D channels	24 D channels	24 D channels	--	--	--	72	1656
SS7/C7	24 D channels	24 D channels	24 D channels	24 D channels	--	--	96	2208
SS7/C7	24 D channels	24 D channels	24 D channels	24 D channels	24 D channels	--	120	2760
SS7/C7	24 D channels	24 D channels	24 D channels	24 D channels	24 D channels	24 D channels	144	3312
SS7/C7	SS7/C7	24 D channels	24 D channels	24 D channels	24 D channels	24 D channels	120	2760

For E1s, the five cards can control 5 * 30 E1s = 150 E1s or 4650 DSOs, as shown in

Table 5: Maximum Number of E1 Links

Card 1	Card 2	Card 3	Card 4	Card 5	Card 6	Card 7	Total # of E1s	Total # of DS0s
SS7/C7	31 D channels	31 D channels	31 D channels	--	--	--	93	2790
SS7/C7	31D channels	31 D channels	31 D channels	31 D channels			124	3720
SS7/C7	31 D channels	31 D channels	31 D channels	31 D channels	31 D channels		155	4650
SS7/C7	31 D channels	31 D channels	31 D channels	31 D channels	31 D channels	31 D channels	186	5580
SS7/C7	SS7/C7	31 D channels	31 D channels	31 D channels	31 D channels	31 D channels	155	4650

Table 5.

System Components

To set up the configuration (dial access solution) in Figure 1, you need the following components:

• A network access server (NAS), such as the Cisco  AS5300, Cisco  AS5200, or Cisco  AS5800, located at one or more service provider POPs.

Each NAS provides termination for voice network trunks and has at least two IP network interfaces, one to carry IP packet data to one or more of the ISP backbones, and another to connect to the ISP-secure management, signaling, and control network.

• A set of voice network trunks that terminate at the NAS.

These trunks can be any TDM type including T1, E1, T3, or E3 depending on the particular NAS platform and the supported suite of digital interfaces. These network trunks do not carry associated signaling channels (for example, PRI D-channels) and are bearer channels; all PSTN signaling terminates on the signaling controller.

• One or more signaling controllers for multiple NASes.

The controller provides termination for the SS7 signaling links and handle all aspects of voice network call control. The signaling controller must be located at the same location as the NAS. One signaling controller can provide signaling and call processing services for a large number of NASes. The signaling controller operates as both a terminating and originating Service Switching Point (SSP) for the SS7 network.

• A set of SS7 signaling trunks that terminate at the signaling controller.

These can be A-links or F-links that have been groomed from their associated voice trunks and delivered to the signaling controller via separate facilities.

Hardware Installation of System Chassis

This section provides an overview of hardware installation of each chassis in the SS7 system. Detailed chassis and rack installation instructions are provided in the publications referenced in the following sections.

Network Access Servers

Cisco AS5200 Universal Access Server

Figure 2 shows the rear panel of a Cisco AS5200 with a Dual T1/PRI card installed.

Figure 2: Cisco AS5200 Rear Panel

Table 6 lists the six cables available from Cisco Systems for connecting the E1 or T1/PRI card ports.

For details on hardware setup, installing cards, and cabling connections, refer to the Cisco AS5200 Universal Access Server Hardware Installation Guide that ships with the access server. Refer to the section "Cisco Connection Online," for more information.

Cisco AS5300 Universal Access Server

Figure 3 shows the rear panel of a Cisco AS5300 with a Quad T1/PRI card installed.

Figure 3: Cisco AS5300 Rear Panel

Table 7 lists the eight cables available from Cisco Systems for connecting the E1 or T1/PRI card ports.

For details on hardware setup, installing cards, and cabling connections, refer to the Cisco AS5300 Universal Access Server Hardware Installation Guide that ships with the access server. Refer to the section "Cisco Connection Online," for more information.

Cisco AS5800 Universal Access Server

Figure 4 shows the rear panel of a fully loaded Cisco AS5800.

Figure 4: Cisco AS5800 Rear Panel - Fully Loaded

Table 8 lists the part number for the interface cables for connecting the T1 card ports.

Table 9 lists the part numbers for the eight interface cables for connecting the E1 card ports.

For details on hardware setup, installing cards, and cabling connections, refer to the Cisco AS5800 Universal Access Server Hardware Installation Guide that ships with the access server. Refer to the section "Cisco Connection Online," for more information.

Cisco LS1010

You can use the Cisco LS1010 ATM switch as a M1/0 device for the SS7 dial access solution. This configuration requires Circuit Emulation Service (CES) T1/E1 port adapter modules, and uses ATM permanent virtual circuits to drop and add individual timeslots from one port to another.

Figure 5 shows the rear panel of a Cisco LS1010.

• Each of the four slots (0 to 3) is referred to as a carrier module (CM).

• Slot 2 is always used for the ATM Service Port (ASP)

• Within each slot, you can have two port adapter modules (PAM) with 4 T1/E1's on each.

• The PAM on the left is always numbered 0, and the PAM on the right is numbered 1.

• There are four ports on each PAM, numbered 0 to 3.

Figure 5: Cisco LS1010 Rear Panel

Table 10 provides a sample mapping. Define circuits as CM/PAM/Port:Circuit:Timeslot.

For details on hardware setup and cabling connections, refer to the Cisco LS1010 Hardware Installation Guide that ships with the multiplexing device. Refer to the section "Cisco Connection Online," for more information.

Cisco Signaling Controllers

Figure 6 shows the rear panel of a Cisco SC2201.

Figure 6: Cisco SC2201 Rear Panel

Figure 7 shows the rear panel of a Cisco SC2211.

Figure 7: Cisco SC2211 Rear Panel

For details on hardware setup, installing cards, and cabling connections, refer to the TransPath System Engineering Application Notes (78-5410-0X) and the TransPath System Installation Guide (78-5419-0X) that ship with the signaling controller. Refer to the section "Cisco Connection Online," for more information.

System Connections

To set up the configuration (dial access solution) in Figure 1, you need to connect the system components as follows:

Step 1 Connect the SS7 signaling links to the Cisco SC2200 Signaling Controller via E1, T1, or V.35 interfaces. For E1/T1 interfaces, you need to use RJ-48 connections, and for V.35 interfaces, you need to use Winchester connections.

Step 2 Connect the voice network directly to the Cisco LS1010 using RJ-48 connections for the E1 and T1 interfaces, or an optional BNC (75 ohms) connection for the E1 interface.

Step 3 Cross-connect the Voice Bearer Channels to another E1/T1 interface on the Cisco  LS1010 and the D channel to the same E1/T1 to set up the Primary Rate Interface (PRI). The Cisco  SC2200 converts the SS7/C7 signal output to D channels for insertion into the voice links T1/E1 interface and then inputs the signal into the Cisco  LS1010 via the RJ-48 connection for both E1 and T1 interfaces or via the optional BNC (75 ohms) connection for the E1 interface. The D channel is connected into the respective E1 or T1 interface as a PRI with E1 = 30 B + D and T1 = 23 B + D.

Step 4 Connect the Cisco LS1010 output PRI E1/T1 to a E1/T1 PRI interface (using an RJ-48 connection) on the Cisco AS5200, Cisco AS5300, or Cisco AS5800 access server. The access server prepares the PRI circuits for transmission to the enterprise or Intranet/Internet networks.

Figure 8 shows system connections.

Figure 8: System Connections

Upgrading the Access Server for New Releases of Software or Portware

The installation process for an SS7 solution often involves downloading late-release software (the Cisco  IOS image running on the access server) or portware (the modem firmware running on modem modules installed in the access server.) This section provides example instructions for how to upgrade a Cisco AS5300 access server using a PC environment. If you are using another access server or a UNIX environment, use the following procedures as general guidelines; the steps are similar.

The upgrade procedure includes the tasks summarized below:

• Install a TFTP Application on the PC

• Connect PC and Access Server

• Establish HyperTerminal Session

• Ping PC and Access Server

• Download Software on Access Server

• Download Portware to Access Server

Install a TFTP Application on the PC

Step 1 Use the Microsoft Windows 95 Explorer to create a directory labeled tftp on your hard disk.

Step 2 Download the TFTP server application from the Cisco web site to the directory created in Step 1. Go to the following Cisco web site, and then click Other Software under the section Cisco Software Products:

http://www.cisco.com/kobayashi/sw-center/

---

Note The TFTP program at this URL is provided as a courtesy of Cisco Systems and is not an officially supported product.

---

Step 3 Make sure that all TFTP files reside in the directory created in Step 1. The TFTP files include tFTPSERV.EXE, TFTPSERV.DLL, MFC42.DLL, and MSVCRT.DLL.

Step 4 Double-click tftpsrv.exe in the Microsoft Windows 95 Explorer to launch the TFTP application.

Step 5 Set your TFTP server root directory:

(a) Choose Server Root Directory from the Options menu.

(b) Double-click tftpboot in [...] list box. If necessary, choose drive c from the Drives list box.

(c) Click OK. The status bar below the menu bar displays c:\tftpboot as the TFTP server root directory.

Caution If you do not select the c:\tftpboot directory as your TFTP server directory, you will not be able to perform the copy procedure. This also applies if you are using rcp on your system.

Step 6 Continue with the following section "Connect PC and Access Server."

Connect PC and Access Server

Step 1 Use network cables to connect the PC and access server to the network, as shown in Figure 9.

Figure 9: Connecting a PC and an Access Server

Step 2 Connect your PC's COM port to the access server console port using the standard Cisco console cable, as shown in Figure 9.

Step 3 Make sure the PC, access server, and hub are all powered ON.

Step 4 Continue with the following section "Establish HyperTerminal Session."

Establish HyperTerminal Session

Use the steps in this section to establish a HyperTerminal session from your local PC to the Cisco  AS5300. You will use the HyperTerminal session to talk to the access server.

Step 1 In Microsoft Windows 95 on your PC, click Start/Programs/Accessories/HyperTerminal.

Step 2 Double-click Hypertrm.exe to display the Connection Description dialog box.

Step 3 Enter a name for your connection, for example, AS5300 and then click OK. HyperTerminal displays the Phone Number dialog box.

Step 4 Choose the COM port connecting the PC and the access server in the Connect Using list box. You have options to connect directly to one of four COM ports.

Step 5 Click OK. HyperTerminal displays the COM Properties dialog box.

Step 6 Choose these options in the COM Properties dialog box:

• Bits per second: 9600

• Data bits: 8

• Parity: None

• Stop bits: 1

• Flow control: None

Step 7 Click OK. The HyperTerminal dialog box appears.

Step 8 Press Enter to display the acc_server> prompt.

---

Note If the access server prompt does not appear, you might have selected the wrong COM port, the cable connections could be incorrect or bad, or the access server might not be powered on.

---

Step 9 Enter the enable mode by entering the enable command and the password:

acc_server> enable
Password: <password>
acc_server#

Step 10 Continue with the following section "Ping PC and Access Server."

Ping PC and Access Server

Ping the access server and the PC to make sure they are talking to each other and there are no configuration problems on your access server.

Step 1 Choose the correct Ethernet adapter connecting to the access server and note the PC's IP address:

(a) Choose Start/Run to display the Run dialog.

(b) Enter winipcfg and click OK to display the IP Configuration dialog box.

(c) Choose the PC Ethernet adapter connector used for the connection to the access server if you have more than one Ethernet adapter connector installed on your PC.

(d) Make a note of the PC IP address, and then click OK.

---

Note Enter the show running-configuration command at the 5300# prompt to verify the access server has an IP address assigned. If the access server does not have an IP address, assign an IP address before continuing.

---

Step 2 In the HyperTerminal dialog box (see the section "Establish HyperTerminal Session" for details), make sure you are at the acc_server# prompt.

Step 3 Enter the ping command with your PC's IP address.

acc_server# ping XXX.XXX.X.X

The access server displays five exclamation points (!) if everything is working and it displays five dots (.) if there is a problem. In the latter case, check the cabling between the router and the PC and check the access server configuration.

Step 4 Continue with the following sections "Download Software on Access Server" or "Download Portware to Access Server."

Download Software on Access Server

This section describes how to download new software to your PC hard drive and then copy the software to the access server Flash memory.

Step 1 Open your TFTP server or rcp application on your PC.

Step 2 Download the Cisco IOS image from the Software Center on the Cisco web site or from a Cisco FTP server. You can use the MS-DOS prompt application that is installed on your PC as an FTP download program or an application like Reflection FTP Client to access the Cisco FTP server and copy the image to your PC.

Make sure the all files are copied into the c:\tftpboot directory.

---

Note For the Cisco  AS5300, use the copy rcp flash command if you are running an rcp application. For the Cisco  AS5200, use the copy rcp bootflash command if you are running an rcp application.

---

Step 3 From the HyperTerminal prompt, enter the copy tftp flash command to copy the new software image from the PC to the access server:

acc_server# copy tftp flash

---

Note Use the copy tftp flash command to copy the new software image from the PC to the Cisco  AS5200.

---

---

Note If the system Flash memory on your access server is partitioned, the access server prompts you to choose the partition for the upload. The default is partition 1, which you should use.

---

TimeSaver You can also copy the Cisco IOS image from the Cisco FTP server directly to Flash memory on your Cisco AS5300 or Cisco AS5800 (you cannot do this with the Cisco AS5200) using HyperTerminal and the copy tftp flash command. In this case, you bypass your PC and the remote host address is not your PC's IP address, but that of the Cisco FTP server.

Step 4 When prompted, enter the IP address of your PC:

Address or name of remote host [255.255.255.255]? 131.108.1.1

Step 5 When prompted, enter the filename of the Cisco  IOS image to be copied to the access server:

Source file name? XXXXXXXX

---

Note You can look at your c:\tftpboot directory to verify the filename for the Cisco  IOS image you are copying.

---

Step 6 When prompted, enter the destination filename and press Enter to indicate that you want to copy the image. We recommend using the descriptive image name (shown below) because this will be the Cisco  IOS image name displayed on the access server's console screen's startup banner (You can also use the show version command to see the Cisco  IOS version number). The image filename is also listed on the diskette label if you copied the image from a diskette.

Destination file name [XXXXXXXX]? c5300-js-mz.113-3.2.AA

During the transfer process, the software displays messages indicating that it has accessed the file you specified and is loading it.

Step 7 Press y when the following prompt appears to confirm the deletion:

Erase flash device before writing? [confirm] y

Step 8 When prompted, press y to reconfirm the deletion.

Step 9 Type yes and then press Enter when the following prompt appears:

Copy `57199401' from server as `cXX00-js-mz.113-3.2.AA' into Flash with erase? [yes/no] yes

The access server displays messages while erasing the Flash memory device, and while loading the new image. The message "Verifying Checksum... OK" indicates a successful load of the new image.

Step 10 Enter the reload command to reload the access server configuration:

acc_server# reload

Step 11 When prompted, press Enter to confirm the reload. The reload can take several minutes. After the reload is complete, you are returned to the acc_server> prompt.

Step 12 Enter the following commands to verify the upload was successful:

acc_server> enable
Password: <password>
acc_server# show version

The Cisco IOS version number displayed should match the version you selected to download from the Cisco web site or FTP server.

Download Portware to Access Server

This section describes how to download the portware to your hard drive and then copy the file to the access server Flash memory.

Step 1 Download the Cisco portware from the software center on the Cisco web site or from a Cisco FTP server into the c:\tftpboot directory.

Step 2 Make sure you have the following prerequisites:

• The TFTP application is running on your PC.

• The PC and access server are connected.

• A HyperTerminal session is running on your PC.

• The access server and PC are talking to each other (verify by pinging).

Step 3 Check the image in the access server Flash memory.

acc_server# show flash
System flash directory:
File Length Name/status
1 4530624 images/cXX00-js-mz.113-4.2.AA
[498776 bytes used, 16278440 available, 16777216 total]
16384K bytes of processor board System flash (Read/Write)

Step 4 Enter the copy tftp flash command to download the modem code file from the c:\tftpboot directory on your PC into the access server Flash memory. (If you are using a Cisco  AS5200, substitute the command copy tftp boot.) You are prompted for the download destination and the remote host name. The remote host name is the IP address of your PC.

acc_server# copy tftp flash
System flash directory:
File Length Name/status
1 4530624 images/cXX00-js-mz.113-3.2.AA
[498776 bytes used, 16278440 available, 16777216 total]
Address or name of remote host [255.255.255.255]?
Source file name? cXX00_portware1-1
Destination file name [images/c5300_portware1-1]?
Accessing file 'cXX00_portware1-1' on 255.255.255.255...
Loading images/cXX00_portware1-1 from 2.2.0.1 (via Ethernet0): ! [OK]
Erase flash device before writing? [confirm] no
Copy 'images/cXX00_portware1-1' from server
as 'images/cXX00_portware1-1' into Flash WITHOUT erase? [yes/no] yes
Loading images/cXX00_portware1-1 from 2.2.0.1 (via Ethernet0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 249108/16278440 bytes]
Verifying checksum... OK (0xE009)
Flash device copy took 00:00:02 [hh:mm:ss]

Step 5 Verify the file has been copied into the access server Flash memory (or boot Flash in Cisco AS5200).

acc_server# show flash
System flash directory:
File Length Name/status
1 4530624 images/cXX00-js-mz.113-3.2.AA
2 210104 images/cXX00_portware1-1
[747948 bytes used, 16029268 available, 16777216 total]
16384K bytes of processor board System flash (Read/Write)

Step 6 Copy the modem code file from the access server Flash memory to the modems by entering the copy flash modem privileged EXEC command. (If you are using a Cisco  AS5200, substitute the command copy bootflash modem.)

acc_server# copy flash modem
Modem Numbers (<slot>/<port> | group <number> | all)? all
System flash directory:
File Length Name/status
1 4530624 images/cXX00-js-mz.113-3.2.AA
2 210104 images/cXX00_portware1-1
[747948 bytes used, 16029268 available, 16777216 total]
Name of file to copy? images/cXX00_portware1-1
Type of service [busyout/reboot] busyout
Copy 'flash:images/cXX00_portware1-1' from Flash to modems? [yes/no] yes

*Feb 26 21:17:43.574: %MODEM-5-DL_START: Modem (2/0) started portware download
.
.
.
*Feb 26 21:17:43.598: %MODEM-5-DL_START: Modem (2/13) started portware download
*Feb 26 21:17:53.598: %MODEM-5-DL_GOOD: Modem (2/14) completed portware download:

---

Note The modem code is downloaded to the module, not the individual slots as shown.

---

After you copy the modem code file into system Flash memory for the first time, you should not have to perform these steps again. Because the modem code runs from modem RAM, the Cisco  IOS software must automatically copy the modem code to every modem each time the access server power cycles.

Software Configuration

To configure your SS7 dial access solution, you need to:

1. Configure the Cisco LS1010.

2. Configure the NAS.

3. Setup continuity testing on the NAS (optional).

4. Configure the Signaling Controller to connect to the NAS.

Configuring the Cisco LS1010

This section provides instructions on how to configure the Cisco LS1010 for a basic configuration that include four T1s. Note that the procedures are the same for adding additional T1s and E1s and using the Cisco LS1010 as a DACs.

For detailed, up-to-date instructions and Command-line interface (CLI) command descriptions, see the LightStream 1010 ATM Switch Software Configuration Guide and the LightStream 1010 ATM Switch Command Reference publication. These documents shipped with your Cisco  LS1010, and they are available on the Cisco Connection Documentation CD that shipped with chassis. Refer to the section "Cisco Connection Online," for more information.

Table 11: Configuring the Cisco LS1010

Step	Command	Purpose
1 .	Switch> enable Switch#	Enter enable mode. You have entered enable mode when the prompt changes to Switch#.
2 .	Switch# config term Enter configuration commands, one per line. End with CNTL/Z. Switch(config)#	Enter global configuration mode. The abbreviated command config term represents the command configure terminal. You can abbreviate commands by entering the minimum number of characters that uniquely identify the command.
3	Switch(config)#  interface ethernet 2/0/0 Switch(config-if)#	Specify the Ethernet interface to configure.
3 .	Switch(config-if)#  ip address xxx.xx.xxx.xx 255.255.0.0	Specify the IP address and subnet mask for the Cisco LS1010. Note that both are required.
4 .	Switch(config-if)# line vty 0 4 switch(config-line)# login switch(config-line)# privilege level 1 switch(config-line)# password changeme switch(config-line)# enable password level 15 changeme switch(config)# hostname ls1010 ls1010(config)# end	Configure the switch for virtual terminal (vty) (Telnet) sessions. Zero (0) is the starting line number and 4 is the maximum number of lines or terminal sessions supported. Enable login on the vty lines. Set the default privilege level for the vtys to 1 (user). Set the password for the vtys. Set the level 15 (admin) password. Note that level 15 is optional because it is the default if the level keyword is not used. Set the hostname for the switch. End the configuration session.
5 .	ls1010# copy running-config startup-config Building configuration... [OK]	Copy the configuration changes so that the switch boots with the correct parameters.
6 .	ls1010# disable ls1010> exit	Exit from enable (also called privileged exec) mode.
7 .	--	Continue with Table 12.

Next, configure the CBR ciruits using the following table.

Table 12: Configuring the CBR Circuits

Step	Command	Purpose
1 .	ls1010> enable ls1010#	Enter enable mode. You have entered enable mode when the prompt changes to ls1010#.
2 .	ls1010# config term Enter configuration commands, one per line. End with CNTL/Z. ls1010(config)#	Enter global configuration mode. The abbreviated command config term represents the command configure terminal. You can abbreviate commands by entering the minimum number of characters that uniquely identify the command.
3	ls1010# int cbr 0/0/0 ls1010# ces aal1 service structured ls1010# int cbr 0/0/1 ls1010# ces aal1 service structured ls1010# int cbr 0/0/2 ls1010# ces aal1 service structured ls1010# int cbr 0/0/3 ls1010# ces aal1 service structured	Configure each CBR interface for structured service to access individual timeslots.
3 .	ls1010# network-clock-select 1 cbr 0/0/0 revertive ls1010# network-clock-select 2 cbr 0/0/1 revertive ls1010# network-clock-select 3 cbr 0/0/2 revertive ls1010# network-clock-select 4 cbr 0/0/3 revertive	Select a clock signal. This clock synchronizes timing between different devices. A stable clock source is essential to reliable (error-free) access to the indiviual timeslots. The network-clock-select commands 1, 2, 3, and 4 represent the configurable clock priority levels (level 5 is the internal system oscillator); cbr X/X/X specifies the interface from which the clock is taken, and revertive specifies that the clock revert to a higher level clock if the current clock goes offline. This step specifies multiple priorities each linked to a different interface (or port).
4 .	ls1010# clock source network-derived	Specify that the clock is network derived (as opposed to internal).
5 .	ls1010# int cbr 0/0/0 ls1010# ces cir 1 time 1-23 circuit-name BEARER_CHNLS ls1010# ces cir 2 time 24 circuit-name ATTPRI_D_CHNL ls1010# int cbr 0/0/1 ls1010# ces cir 1 time 1 circuit-name NI2_D_CHNL ls1010# int cbr 0/0/2 ls1010# ces cir 1 time 1 circuit-name ATTPRI_D_CHNL ls1010# int cbr 0/0/3 ls1010# ces cir 1 time 1-23 circuit-name BEARER_CHNLS ls1010# ces cir 2 time 24 circuit-name NI2_D_CHNL	Define the circuit number, timeslot number, and circuit name for each circuit.
6 .	ls1010# int cbr 0/0/0 ls1010# ces pvc 1 dest 47.0091.8100.0000.0060.83c5.c801.4000.0c80.003c.10 vpi 0 vci 3088 ls1010# ces pvc 2 dest 47.0091.8100.0000.0060.83c5.c801.4000.0c80.0038.10 vpi 0 vci 2064 ls1010# int cbr 0/0/1 ls1010# ces pvc 1 dest 47.0091.8100.0000.0060.83c5.c801.4000.0c80.003c.20 vpi 0 vci 3104	Configure the permanent virtual circuits (PVC). PVCs are defined as a link between ports, so there is only one PCC per circuit. Select the interface of the originating (active) side of the PVC. The ces pvc command is used with arguments to connect the PVC to the destination (passive) port and circuit as follows: ces pvc circuit# dest NSAP address vpi vpi# vci vci#. The circuit number was defined in the ces cir command in Step 5 and the NSAP address, vpi # and vci # can be found in the output of sho ces address (see the Verify section). Note The show ces address command must be run after the circuits are defined, from a normal (not config) enable (also called privileged exec) prompt. The NSAP address is a 20-byte ATM address, that together with theVPI, VCI pair uniquely define the passive end of the PVC.
7 .	ls1010# int cbr 0/0/0 ls1010# no shut ls1010# int cbr 0/0/1 ls1010# no shut ls1010# int cbr 0/0/2 ls1010# no shut ls1010# int cbr 0/0/3 ls1010# no shut	Bring up the circuits by executing the no shutdown command for each port.
8 .	ls1010# exit	Exit from enable (also called privileged exec) mode.

Sample Configuration

The following display represents a sample configuration:

Current configuration:
!
version 11.3
no service pad
no service udp-small-servers
no service tcp-small-servers
!
hostname annapolis
!
enable password vsbuops
!
network-clock-select revertive
network-clock-select 1 CBR0/0/0
network-clock-select 2 CBR0/0/1
network-clock-select 3 CBR0/0/2
!
atm address 47.0091.8100.0000.0060.83c5.c801.0060.83c5.c801.00
atm router pnni
node 1 level 56 lowest
redistribute atm-static
!
!
interface CBR0/0/0
no ip address
ces aal1 service Structured
ces circuit 1 timeslots 1-23 circuit-name bearer_chnls
ces pvc 1 dest-address 47.0091.8100.0000.0060.83c5.c801.4000.0c80.003c.10
vpi 0 vci 3088
ces circuit 2 timeslots 24 circuit-name attpri_d_chnl
ces pvc 2 dest-address 47.0091.8100.0000.0060.83c5.c801.4000.0c80.0038.10
vpi 0 vci 2064
!
interface CBR0/0/1
no ip address
ces aal1 service Structured
ces circuit 1 timeslots 1 circuit-name ni2_d_chnl
ces pvc 1 dest-address 47.0091.8100.0000.0060.83c5.c801.4000.0c80.003c.20
vpi 0 vci 3104
!
interface CBR0/0/2
no ip address
ces aal1 service Structured
ces circuit 1 timeslots 1 circuit-name attpri_d_chnl
!
interface CBR0/0/3
no ip address
ces aal1 service Structured
ces circuit 1 timeslots 1-23 circuit-name bearer_chnls
ces circuit 2 timeslots 24 circuit-name ni2_d_chnl
!
interface CBR0/1/0
no ip address
ces aal1 service Structured
!
interface CBR0/1/1
no ip address
ces aal1 service Structured
!
interface CBR0/1/2
no ip address
ces aal1 service Structured
!
interface CBR0/1/3
no ip address
ces aal1 service Structured
!
interface CBR1/0/0
no ip address
!
interface CBR1/0/1
no ip address
!
interface CBR1/0/2
no ip address
!
interface CBR1/0/3
no ip address
!
interface ATM2/0/0
no ip address
atm maxvp-number 0
!
interface Ethernet2/0/0
ip address 171.71.120.50 255.255.0.0
!
no ip classless
!
line con 0
line aux 0
line vty 0 4
password vsbuops
login
!
end

Verify

• Enter the show ces cir command:

ls1010# show ces cir

Interface  Circuit  Circuit-Type     X-interface   X-vpi   X-vci Status
 CBR0/0/0    1       Active SoftVC   ATM-P0/0/3      0      3088  UP
 CBR0/0/0    2       Active SoftVC   ATM-P0/0/3      0      2064  UP
 CBR0/0/1    1       Active SoftVC   ATM-P0/0/3      0      3104  UP
 CBR0/0/2    1       Passive SoftVC  ATM-P0/0/3      0        32  UP
 CBR0/0/3    1       Passive SoftVC  ATM-P0/0/3      0        16  UP
 CBR0/0/3    2       Passive SoftVC  ATM-P0/0/3      0      1040  UP

• Enter the show ces address command:

ls1010# show ces address

CES-IWF ATM Address(es):
47.0091.8100.0000.0060.83c5.c801.4000.0c80.0030.10  CBR0/0/0:1  vpi 0 vci 16
47.0091.8100.0000.0060.83c5.c801.4000.0c80.0030.20  CBR0/0/0:2  vpi 0 vci 32
47.0091.8100.0000.0060.83c5.c801.4000.0c80.0034.10  CBR0/0/1:1  vpi 0 vci 1040
47.0091.8100.0000.0060.83c5.c801.4000.0c80.0038.10  CBR0/0/2:1  vpi 0 vci 2064
47.0091.8100.0000.0060.83c5.c801.4000.0c80.003c.10  CBR0/0/3:1  vpi 0 vci 3088
47.0091.8100.0000.0060.83c5.c801.4000.0c80.003c.20  CBR0/0/3:2  vpi 0 vci 3104
47.0091.8100.0000.0060.83c5.c801.4000.0c80.1030.10  CBR0/1/0:1  vpi 0 vci 16
47.0091.8100.0000.0060.83c5.c801.4000.0c80.1034.10  CBR0/1/1:1  vpi 0 vci 1040
47.0091.8100.0000.0060.83c5.c801.4000.0c80.1034.20  CBR0/1/1:2  vpi 0 vci 1056
47.0091.8100.0000.0060.83c5.c801.4000.0c80.1038.10  CBR0/1/2:1  vpi 0 vci 2064
47.0091.8100.0000.0060.83c5.c801.4000.0c80.103c.20  CBR0/1/3:2  vpi 0 vci 3104
ls1010#

Configuring the NAS

For each NAS installed in your SS7 Dial Access Solution System, you need to:

Step 1 Configure the switch type to NI2 using the isdn switch-type primary-ni command. This command enables the connection between the NAS and the signaling controller. You also need to enable COT loopback support for call termination from SS7 using the isdn service cot command.

Step 2 Configure the access server for channelized T1 or E1 lines.

Step 3 Configure the D channels for modem signaling and to receive calls from the Cisco  LS1010. SS7 is processed on the NAS D channels. You must configure all the D channels to carry the appropriate control and signaling messages for communication between the Cisco Signaling Controller SC2200 and NAS. In most scenarios, the D channel configuration on each ISDN PRI will be identical. Also note that the isdn incoming-voice modem command allocates modems to any incoming voice calls and stops call rejection so call type is not passed to NAS from the Cisco LS1010.

For detailed configuration instructions:

• For the Cisco AS5200, see Chapter 3, "Configuring the Access Manually" in the Cisco AS5200 Universal Access Server Software Configuration Guide that shipped with the universal access server.

• For the Cisco AS5300, see "Chapter 3, Basic Configuration" in the Cisco AS5300 Universal Access Server Software Configuration Guide that shipped with the universal access server.

• For the Cisco AS5800, see "Chapter 3, Configuring your Cisco AS5800 Universal Access Server" in the Cisco AS5800 Universal Access Server Software Configuration Guide that shipped with the universal access server.

Additional Reference Documentation

For additional information refer to the following documentation:

• Dial Solutions Configuration Guide

• Dial Solutions Command Reference Guide

• Dial Solutions Quick Configuration Guide

Sample Configurations

This is a sample configuration showing a Cisco AS5300 with an E1 interface configured to receive calls from the Cisco LS1010. Note: The NAS must be set to isdn switch-type primary-ni.

hostname TD_nas2
!
boot system tftp c5300.nubu 171.71.120.19
enable secret 5 $1$AitJ$yID83jtMnPq3uqr.o699M/
enable password lightspeed
!
username cisco password 0 cisco
ip domain-name cisco.com
ip name-server 171.71.120.12
isdn switch-type primary-ni
!
!
controller E1 0
 framing NO-CRC4
 clock source line primary
 pri-group timeslots 1-31
!
controller E1 1
 framing NO-CRC4
 clock source line secondary
 pri-group timeslots 1-31
!
controller E1 2
 clock source internal
!
controller E1 3
 clock source internal
!
!
interface Loopback0
 ip address 10.1.1.130 255.255.255.128
!
interface Ethernet0
 ip address 171.71.120.84 255.255.255.0
 no ip mroute-cache
 shutdown
!
interface Serial0:15
 ip unnumbered Ethernet0
 encapsulation ppp
 dialer-group 1
 isdn switch-type primary-ni
 isdn incoming-voice modem
 isdn service cot
 peer default ip address pool setup_pool
 no fair-queue
 no cdp enable
 ppp authentication chap pap
 ppp multilink
!
interface FastEthernet0
 ip address 172.24.233.45 255.255.255.0
!
interface Group-Async1
 description "Async Incoming Call"
 ip unnumbered FastEthernet0
 ip tcp header-compression passive
 encapsulation ppp
 no ip mroute-cache
 async dynamic address
 async mode interactive
 no snmp trap link-status
 peer default ip address pool default
 no fair-queue
 no cdp enable
 ppp authentication chap pap
 ppp chap hostname wotremotsees
 group-range 1 96
 hold-queue 10 in
!
router igrp 1
 redistribute connected
 network 172.24.0.0
!
ip local pool default 172.24.233.46 172.24.233.48
ip default-gateway 172.24.233.6
no ip classless
ip route 0.0.0.0 0.0.0.0 172.24.233.6
ip route 10.1.2.0 255.255.255.128 10.1.1.1
access-list 101 permit ip any any
dialer-list 1 protocol ip list 101
dialer-list 1 protocol ipx permit
!
line con 0
 exec-timeout 0 0
 logging synchronous
 transport input none
line 1 96
 autoselect during-login
 autoselect ppp
 login local
 modem InOut
 transport preferred none
 transport input all
line aux 0
line vty 0 4
 exec-timeout 0 0
 password cisco
 login
!
scheduler interval 1000
end
 

This is a sample configuration showing a Cisco AS5800 with a T1 interface configured to receive calls from the Cisco LS1010.

hostname capone
!
boot system flash c5800-p4-mz.nubu.Jun1
aaa new-model
aaa authentication local-override
aaa authentication login CONSOLE none
aaa authentication login RADIUS_LIST radius none
aaa authentication login TAC_PLUS tacacs+ enable none
aaa authentication enable default enable tacacs+
aaa authentication ppp RADIUS_LIST if-needed radius none
enable secret 5 $1$J6YP$0CCkyB6I9.hCWqnAZZUX4.
enable password 7 045802150C2E
!
username admin password 7 060506324F4149
username user password 7 00071A1507544B
shelf-id 0 router-shelf
shelf-id 1 dial-shelf
!
!
modem-pool Default
 pool-range 1/6/0-1/6/71
!
modem-pool sw56
!
ip subnet-zero
no ip source-route
ip host jamba 171.71.120.41
ip domain-name cisco.com
ip name-server 171.71.120.12
isdn switch-type primary-ni
modemcap entry mica_name:MSC=s39=7
clock timezone EST -5
clock summer-time EDT recurring
!
!
controller T1 1/0/0
 framing esf
 linecode b8zs
 pri-group timeslots 1-24
!
controller T1 1/0/1
 framing esf
 linecode b8zs
 pri-group timeslots 1-24
!
controller T1 1/0/2
 framing esf
 linecode b8zs
 pri-group timeslots 1-24
!
controller T1 1/0/3
 framing esf
 linecode b8zs
 pri-group timeslots 1-24
!
controller T1 1/0/4
 framing esf
 linecode b8zs
 pri-group timeslots 1-24
!
controller T1 1/0/5
 framing esf
 linecode b8zs
 pri-group timeslots 1-24
!
controller T1 1/0/6
 framing esf
 linecode b8zs
 pri-group timeslots 1-24
!
controller T1 1/0/7
 framing esf
 linecode b8zs
 pri-group timeslots 1-24
!
controller T1 1/0/8
 framing esf
 linecode b8zs
 pri-group timeslots 1-24
!
controller T1 1/0/9
 framing esf
 linecode b8zs
 pri-group timeslots 1-24
!
controller T1 1/0/10
 framing esf
 linecode b8zs
 pri-group timeslots 1-24
!
controller T1 1/0/11
 framing esf
 linecode b8zs
 pri-group timeslots 1-24
!
interface Loopback0
 no ip address
 no ip mroute-cache
 no logging event link-status
!
interface FastEthernet0/0/0
 ip address 171.71.120.90 255.255.255.0
 no ip mroute-cache
 no logging event link-status
 full-duplex
!
interface Serial1/0/0:23
 no ip address
 no ip mroute-cache
 no logging event link-status
 isdn switch-type primary-ni
 isdn incoming-voice modem
 isdn service cot
 no cdp enable
!
interface Serial1/0/1:23
 no ip address
 no ip mroute-cache
 no logging event link-status
 isdn switch-type primary-ni
 isdn incoming-voice modem
 isdn service cot
 no cdp enable
!
interface Serial1/0/2:23
 no ip address
 no ip mroute-cache
 no logging event link-status
 shutdown
 isdn switch-type primary-ni
 isdn incoming-voice modem
 isdn service cot
 no cdp enable
!
interface Serial1/0/3:23
 no ip address
 no ip mroute-cache
 no logging event link-status
 isdn switch-type primary-ni
 isdn incoming-voice modem
 isdn service cot
 no cdp enable
!
interface Serial1/0/4:23
 no ip address
 no ip mroute-cache
 no logging event link-status
 isdn switch-type primary-ni
 isdn service cot
 no cdp enable
!
interface Serial1/0/5:23
 no ip address
 no ip mroute-cache
 no logging event link-status
 isdn switch-type primary-ni
 isdn service cot
 no cdp enable
!
interface Serial1/0/6:23
 no ip address
 no ip mroute-cache
 no logging event link-status
 isdn switch-type primary-ni
 isdn service cot
 no cdp enable
!
interface Serial1/0/7:23
 no ip address
 no ip mroute-cache
 no logging event link-status
 isdn switch-type primary-ni
 isdn service cot
 no cdp enable
!
interface Serial1/0/8:23
 no ip address
 no ip mroute-cache
 no logging event link-status
 isdn switch-type primary-ni
 isdn service cot
 no cdp enable
!
interface Serial1/0/9:23
 no ip address
 no ip mroute-cache
 no logging event link-status
 isdn switch-type primary-ni
 isdn service cot
 no cdp enable
!
interface Serial1/0/10:23
 no ip address
 no ip mroute-cache
 no logging event link-status
 isdn switch-type primary-ni
 isdn service cot
 no cdp enable
!
interface Serial1/0/11:23
 no ip address
 no ip mroute-cache
 no logging event link-status
 isdn switch-type primary-ni
 isdn service cot
 no cdp enable
!
interface Group-Async0
 ip unnumbered FastEthernet0/0/0
 encapsulation ppp
 no ip mroute-cache
 no logging event link-status
 async mode dedicated
 peer default ip address pool default
 no fair-queue
 no cdp enable
 ppp authentication chap callin RADIUS_LIST
 ppp chap hostname sgtisdn
 ppp multilink
 group-range 1/6/00 1/6/71
 hold-queue 10 in
!
interface Dialer0
 description "Config parameters common to all D-Chans"
 ip unnumbered Loopback0
 encapsulation ppp
 no ip mroute-cache
 no logging event link-status
 dialer in-band
 dialer-group 1
 peer default ip address pool default
 no fair-queue
 no cdp enable
 ppp authentication chap callin RADIUS_LIST
 ppp chap hostname nas01
 ppp multilink
!
ip local pool default 171.71.120.91 171.71.120.92
ip default-gateway 171.71.120.6
ip classless
ip route 0.0.0.0 0.0.0.0 171.71.120.6
!
ip access-list standard DEFAULT
 deny   0.0.0.0
 permit any
ip access-list standard RFC1918
 deny   10.0.0.0 0.255.255.255
 deny   172.0.0.0 0.31.255.255
 deny   192.168.0.0 0.0.255.255
 permit any
no logging buffered
no logging console
logging trap debugging
logging 110.0.0.10
dialer-list 1 protocol ip permit
snmp-server community public RO
snmp-server system-shutdown
!
!
line con 0
 exec-timeout 0 0
 login authentication CONSOLE
 transport input none
line aux 0
 exec-timeout 15 0
 modem InOut
 transport input all
 autohangup
 speed 38400
 flowcontrol hardware
line vty 0 4
 session-timeout 45
 exec-timeout 1200 0
 password 7 00101602
 login authentication TAC_PLUS
 transport preferred none
line 1/6/00 1/6/71
 autoselect ppp
 login authentication TAC_PLUS
 modem InOut
 modem autoconfigure discovery
 transport input all
!
end
 

Setting Up Continuity Testing in the NAS (Optional)

Continuity testing is set up by enabling the NI2 switch type and configuring ISDN service COT messages to pass through each D-channel interface involved in SS7 call signaling control.

Table 13: Setting up Continuity Testing for SS7

Step	Command	Purpose
1 .	NAS (config)# isdn switch-type primary-ni	Configure support for the NI2 local ISDN PRI switch type. This switch type is enhanced to support communication between the access server and the Cisco Signaling Controller SC2200.
2 .	NAS(config)# interface serial number:number	Specify a D-channel serial interface. Replace the number argument with a controller number followed by a colon (:) and D-channel number. For example, a Cisco AS5300 T1 configuration can have either 0:23, 1:23, 2:23, or 3:23. A Cisco AS5300 E1 configuration can have either 0:15, 1:15, 2:15, or 3:15.
3 .	NAS(config-if)# isdn service cot	Allow ISDN service COT messages to pass through the D  channel. This command is disabled by default. This command must also be configured on each D-channel interface that is involved in SS7 call signaling control.

Verify

Use the debug isdn q931 command to display continuity testing debug messages. The following shows a successful COT sequence debug log after the debug isdn q931 command is issued and a call comes through the system.

A COT request comes into the NAS, as indicated by the field COT REQUEST pd. The NAS performs a loopback test on DS0 channel 1, as indicated by the field COT_ServiceMsg: set loop on dsl 0, channel 1. The test operation was a success, as shown by the field COT Result i = 0x02.

NAS# debug isdn q931

00:06:38: ISDN Se0:23: RX <-  RRp sapi = 0  tei = 0 nr = 0 
00:06:38: ISDN Se0:23: TX ->  RRf sapi = 0  tei = 0  nr = 0
NAS#
00:06:48: ISDN Se0:23: RX <-  RRp sapi = 0  tei = 0 nr = 0 
00:06:48: ISDN Se0:23: TX ->  RRf sapi = 0  tei = 0  nr = 0
NAS#
00:06:52: ISDN Se0:23: RX <-  INFOc sapi = 0  tei = 0  ns = 0  nr = 0  i = 
0x43020003031804E9808381610102620227
00:06:52:     COT REQUEST pd = 67  callref = 0x0003
00:06:52:         Channel ID i = 0xE9808381
00:06:52:         COT Operation i = 0x02
00:06:52:         COT Duration i = 0x2702
00:06:52: ISDN Se0:23: TX ->  RRr sapi = 0  tei = 0  nr = 1
00:06:52: COT_ServiceMsg: set loop on dsl 0, channel 1

00:06:52: COT_Response(call_id 0x8003, operation 2, result 2) sent
00:06:52: ISDN Se0:23: TX ->  INFOc sapi = 0  tei = 0  ns = 0  nr = 1  i = 
0x43028003021804E9808381610102630102
00:06:52:     COT RESULT pd = 67  callref = 0x8003
00:06:52:         Channel ID i = 0xE9808381
00:06:52:         COT Operation i = 0x02
00:06:52:         COT Result i = 0x02

00:06:52: ISDN Se0:23: RX <-  RRr sapi = 0  tei = 0  nr = 1
NAS#
00:07:02: ISDN Se0:23: RX <-  RRp sapi = 0  tei = 0 nr = 1 
00:07:02: ISDN Se0:23: TX ->  RRf sapi = 0  tei = 0  nr = 1
NAS#
00:07:12: ISDN Se0:23: RX <-  RRp sapi = 0  tei = 0 nr = 1 
00:07:12: ISDN Se0:23: TX ->  RRf sapi = 0  tei = 0  nr = 1
NAS#
00:07:14: ISDN Se0:23: RX <-  INFOc sapi = 0  tei = 0  ns = 1  nr = 1  i = 
0x43020003031804E9808381610101
00:07:14:     COT REQUEST pd = 67  callref = 0x0003

00:07:14:         Channel ID i = 0xE9808381
00:07:14:         COT Operation i = 0x01
00:07:14: ISDN Se0:23: TX ->  RRr sapi = 0  tei = 0  nr = 2
00:07:14: COT_ServiceMsg: clear loop on dsl 0, channel 1

00:07:14: COT_Response(call_id 0x8003, operation 1, result 1) sent
00:07:14: ISDN Se0:23: TX ->  INFOc sapi = 0  tei = 0  ns = 1  nr = 2  i = 
0x43028003021804E9808381610101630101
00:07:14:     COT RESULT pd = 67  callref = 0x8003
00:07:14:         Channel ID i = 0xE9808381
00:07:14:         COT Operation i = 0x01
00:07:14:         COT Result i = 0x02

00:07:14: ISDN Se0:23: RX <-  RRr sapi = 0  tei = 0  nr = 2
NAS#
00:07:24: ISDN Se0:23: RX <-  RRp sapi = 0  tei = 0 nr = 2 
00:07:24: ISDN Se0:23: TX ->  RRf sapi = 0  tei = 0  nr = 2
NAS#
00:07:34: ISDN Se0:23: RX <-  INFOc sapi = 0  tei = 0  ns = 2  nr = 2  i = 
0x43020003031804E9808381610102620227
00:07:34:     COT REQUEST pd = 67  callref = 0x0003
00:07:34:         Channel ID i = 0xE9808381
00:07:34:         COT Operation i = 0x02
00:07:34:         COT Duration i = 0x2702
00:07:34: ISDN Se0:23: TX ->  RRr sapi = 0  tei = 0  nr = 3
00:07:34: COT_ServiceMsg: set loop on dsl 0, channel 1

00:07:34: COT_Response(call_id 0x8003, operation 2, result 2) sent
00:07:34: ISDN Se0:23: TX ->  INFOc sapi = 0  tei = 0  ns = 2  nr = 3  i = 
0x43028003021804E9808381610102630102
00:07:34:     COT RESULT pd = 67  callref = 0x8003
00:07:34:         Channel ID i = 0xE9808381
00:07:34:         COT Operation i = 0x02
00:07:34:         COT Result i = 0x02

00:07:34: ISDN Se0:23: RX <-  RRr sapi = 0  tei = 0  nr = 3
NAS#
00:07:39: ISDN Se0:23: RX <-  INFOc sapi = 0  tei = 0  ns = 3  nr = 3  i = 
0x43020003031804E9808381610101

Tips

• To generate service messages for each DS0 (B channel) that is removed from service, use the isdn service dsl 0 b_channel 1 state 2 command. This command is also configured on the D-channel interface. This command is useful for informing the LS1010 or Digital Cross Connect System (DACS) to not place calls to B channels that are removed from service.

• To view channels that are manually taken out of service or if a PRI line goes up then down, use the show isdn service command.

Configuring the Cisco SC2200 Signaling Controller

For complete instructions on how to configure the Cisco  SC2200 signaling controller and its software, see the publications that shipped with the controller:

• TransPath System Product Release Notes, part number 78-5417-0X

• TransPath System Engineering Application Notes, part number 78-5410-0X

• TransPath System Installation Guide, part number 78-5419-0X

• TransPath System Software Operations and Maintenance Guide, part number 78-5435-0X

• TransPath System Configuration Tool Guide, part number 78-5382-0X

• TransPath System Configurable Number Manipulation Guide, part number 78-5418-0X

If You Need More Information

The Cisco IOS software running on your router contains extensive features and functionality. The effective use of many of these features is easier if you have more information at hand. For additional information on configuring and maintaining a Cisco SC2200, the following documentation resources are available:

• Cisco Documentation CD-ROM

Cisco documentation and additional literature are available on a CD-ROM, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly; therefore, it might be more up to date than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM is available as a single item or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback on the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.

---

Note You can access Cisco IOS software configuration documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com

---

• For Cisco IOS software configuration information, refer to the modular configuration and modular command reference publications in the Cisco IOS software configuration documentation set that corresponds to the software release installed on your Cisco hardware.

• To obtain general information about documentation, refer to the section "Cisco Connection Online," or call customer service at 800 553-6387 or 408  526-7208. Customer service hours are 5:00 a.m. to 6:00 p.m. Pacific time, Monday through Friday (excluding Cisco-observed holidays). You can also send e-mail to cs-rep@cisco.com, or you can refer to the Cisco Information Packet that shipped with your router.

Cisco Connection Online

Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

• WWW:    http://www.cisco.com

• WWW:    http://www-europe.cisco.com

• WWW:    http://www-china.cisco.com

• Telnet:    cco.cisco.com

• Modem:    From North America, 408  526-8070; from Europe, 33  1  64  46  40  82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and connection rates up to 28.8  kbps.

For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

Copyright 1989-1998 © Cisco Systems Inc.