Cisco 3725 Software Configuration Guide - Page 74

Configuring T1 and E1 Interfaces Chapter 3 Configuring with the Command-Line Interface Defining ISDN Service Profile Identifiers Some service providers assign service profile identifiers (SPIDs) to define the services to which an ISDN device subscribes. If your service provider requires SPIDs, your ISDN device cannot place or receive calls until it sends a valid SPID to the service provider when initializing the connection. A SPID is usually a seven-digit telephone number plus some optional numbers, but service providers might use different numbering schemes. SPIDs have significance at the local access ISDN interface only; remote routers are never sent the SPID. Currently, only DMS-100 and NI-1 switch types require SPIDs. Two SPIDs are assigned for the DMS-100 switch type, one for each B channel. The AT&T 5ESS switch type might support SPIDs, but Cisco recommends that you set up that ISDN service without SPIDs. If your service provider assigns you SPIDs, you must define these SPIDs on the router. To define SPIDs and the local directory number (LDN) on the router for both ISDN BRI B channels, use the following isdn spid commands: Router (config-if)# isdn spid1 spid-number [ldn] Router (config-if)# isdn spid2 spid-number [ldn] Note Although the LDN is an optional parameter in the command, you might need to enter it so the router can answer calls made to the second directory number. For further information on configuring ISDN, see the chapters "Configuring ISDN" and "Configuring DDR" in the Wide-Area Networking Configuration Guide publication, for your Cisco IOS software release. Configuring T1 and E1 Interfaces To configure an ISDN PRI interface or T1/E1 multiflex trunk interface, use the configuration software provided with your router or network module, if any. Otherwise, for greatest power and flexibility use configuration mode (manual configuration). In this mode, you enter Cisco IOS commands at the router prompt. Note Before you begin, disconnect all WAN cables from the router to keep it from trying to run the AutoInstall process. The router tries to run AutoInstall whenever you power it on if there is a WAN connection on both ends and the router does not have a valid configuration file stored in NVRAM (for instance, when you add a new interface). It can take several minutes for the router to determine that AutoInstall is not connected to a remote Transmission Control Protocol/Internet Protocol (TCP/IP) host. This section describes basic configuration, including enabling the interface and specifying IP routing. Depending on your own requirements and the protocols you plan to route, you might also need to enter other configuration commands. Before you begin configuring the interfaces, make sure you: • Connect a console to the router. • Power on the router. 3-14 Software Configuration Guide for Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers OL-1957-04