Cisco Router ISDN Configuration

Cisco router ISDN configuration
http://searchenterprisewan.techtarget.com/tip/Cisco-router-ISDN-confi...
You're logged in as: tamrat andarge Edit your profile Logout RSS Part of the TechTarget network SearchEnterpriseWAN.com News
Latest Headlines
Web content optimization: A new approach to SharePoint optimization Ensuring Quality of Experience: Monitor networks or applications? Should you redesign WAN architecture for cloud and UC? View All News Enterprise WAN Topics
Topics
Telecom Services
Selecting telecommunications services and providers, Managed services, Cloud computing and SaaS
VPNs/Security
VPN design, VPN setup and configuration, Remote access, Internet and application security
WAN Design
Bandwidth and capacity planning, Branch office network design, Network disaster recovery, WWANs, VPN Design
Infrastructure
IP networks, Network Infrastructure, WAN protocols

Optimization/Application Performance
Application performance on the WAN, WAN network monitoring, WAN optimization and application acceleration
Hot Topics
Optimization/Application Performance VPNs/Security Infrastructure Tutorials

Guides
1 of 14
5/24/2012 7:07 PM
Advanced Workshops MPLS VPN fundamentals VoIP over WAN tutorial

Technology Dictionary
Find definitions and links to technical resources Powered by WhatIs.com Expert Advice
Tips
Selecting WAN application visibility solutions Achieving application visibility through wide area network visibility Understanding application performance monitoring and management View All Tips
Answers
How can I allow and restrict user access on my VPN client? How do remote access VPNs compare with other types of VPNs? How can I make sure my VPN is encrypted and working properly? View All Answers
Ask a Question
Pose a question to the SearchEnterpriseWAN.com Experts Get help from our technical community Powered by ITKnowledgeExchange.com White Papers
Research Library
White Papers Business Webcasts Downloads Powered by Bitpipe.com

Product Demos
Try out software demos Powered by 2020Software.com Blogs

Blogs
Window on WANS Unified Communications Nation Powered by ITKnowledgeExchange.com Search this site
2 of 14
5/24/2012 7:07 PM
Home Topics Telecommunications Carrier Services Selecting telecommunications services and providers Cisco router ISDN configuration

Chris Partsenidis E-mail Print A AA AAA LinkedIn Facebook Twitter Share This RSS Reprints Integrated Services Digital Network (ISDN) provides for digital transmission over ordinary telephone copper wire as well as over other media uses. Chris Partsenidis teaches you how to configure your Cisco router to work with ISDN, in this continuation of his tip series on ISDN implementation.
Cisco routers' basic ISDN configuration

Here we will go through the basic steps of configuring a Cisco router to work with ISDN. Below is a table of ISDN switch types. Before you attempt to configure ISDN, you need to ensure that you know which type of ISDN switch you are connecting to at the telco. ISDN SWITCH TYPES
Telco switch type AT&T basic rate switch Nortel DMS-100 basic rate switch National ISDN-1 switch
Cisco keyword basic-5ess basic-dms100 basic-ni1
PINX (PBS) switches with QSIG signalling per Q.931 basic-qsig NET3 switch type for U.K., Europe, Asia & Australia basic-net3 AT&T 4ESS (ISDN PRI only) AT&T 5ESS (ISDN PRI only) Nortel DMS-100 (ISDN PRI only) National ISDN switch type NTT ISDN PRI switches (Japan) European and Australian ISDN PRI switches QSIG signalling per Q.931 No switch type primary-4ess primary-5ess primary-dms100 primary-ni primary-ntt primary-net5 primary-qsig none
For a very basic BRI ISDN configuration on a Cisco router, you need to perform the following steps, providing you are not using
3 of 14
5/24/2012 7:07 PM
Demand Dial Routing (DDR): 1. Configure the Switch Type (using switch-type). 2. Configure the ISDN Dialer Map; this basically maps the IP address of the end router's IP address with its telephone number (using dialer-map). 3. Configure your ISDN interface IP address (using interface and IP address). 4. Configure a routing rule (using IP route). For example: Router(config)#isdn switch-type basic-5ess Router(config)#isdn dialer map ip 10.10.10.2 name main_office 66552 Router(config)#ip route 192.168.0.0 255.255.255.0 10.10.10.2 Router(config)#interface BRI 0 Router(config-if)#ip address 10.10.10.1 255.255.255.0 N.B. If using the DMS-100 and National-1 switch types (as well as AT&T 5ESS), you will need to obtain from your telco the Service Profile Identifiers (SPIDs), of which you require one per each Bearer Channel. For these switch types, these need to be configured using the isdn spid1 & isdn spid2 commands. The SPIDs are used to authenticate call requests at the telco's switch. The format for using the SPIDs is isdn spid1 spid-number ldn and isdn spid2 spid-number ldn.
Demand dial routing

Since ISDN is a circuit-switched technology, you usually pay for the amount of time that the line is active. For this reason, you generally do not want to raise the ISDN line for just any type of traffic. In order to accommodate this, you can configure what's called Demand Dial Routing (DDR). The idea behind DDR is that you specify the "interesting" traffic that will be able to raise the ISDN line. For example, you can set as "interesting" traffic all packets destined toward a specific remote network you connect to. If none of the routed traffic that is heading for that network (on the other side of the ISDN line), the line doesn't get raised. This saves on unnecessary costs caused by nonessential traffic raising the line. You specify "interesting" traffic with the use of Access Control Lists (ACLs). If the traffic destined for the remote network doesn't match this interesting traffic, then the line stays down. Otherwise, the line is raised and traffic is allowed to travel to the remote network. It's worth mentioning here that although you have defined this "Interesting" traffic, it doesn't mean that other traffic will not be allowed to travel along the ISDN link. If the link is active, any traffic (unless blocked by Access Lists) is allowed to travel the link, so keep in mind that the "Interesting" traffic is used only to bring the line up. You can then create a second set of ACLs which define the traffic that can traverse the ISDN line. Also, the DDR works using a counter, like a time-out counter. Once the counter reaches a preset configurable threshold, the line will drop again. This threshold is reduced each time "Interesting" traffic is sent over the ISDN Link, so it's also only the "Interesting" traffic that is used to maintain the link. Steps in configuring DDR (assumes some of the basic steps above have already been configured) 1. Define Interesting Traffic (using dialer-list and access-list). 2. Assign Interesting Traffic to an Interface (using dialer-group). 3. Define the destination IP address, hostname and telephone number to dial (using dialer map). 4. Define any additional options (using dialer idle-timeout, dialer fast-idle, dialer load-threshold). THE ADDITIONAL OPTIONS:
More tips on ISDN implementation Understanding the ISDN standard ISDN protocols, components and router options Cisco router ISDN configuration
Command dialer idle-timeout seconds dialer fast-idle seconds
Description Specifies the amount of idle time in seconds before the link is dropped. Specifies the time that a line showing contention can remain idle before it is dropped in order to allow the other call to be placed.
Specifies the amount of load on the ISDN before the dialer initiates another call to the same dialer load-threshold load destination (i.e., brings up the second channel, making the link 128 Kbps). The load is a number [outbound | inbound from 1 to 255, with 255 equalling 100% load. The final parameters specify which direction of |either]
4 of 14
5/24/2012 7:07 PM
traffic to calculate the load from. For example: Router(config)#isdn dialer map ip 10.10.10.2 name main_office 66552 Router(config)#access-list 101 permit tcp any any eq http Router(config)#dialer-list 1 protocol ip list 101 Router(config)#interface BRI 0 Router(config-if)#dialer-group 1 What this example does is allow all Web traffic (http) from anywhere to anywhere. As you can see, the dialer-list is specifying the 101 access list to dialer-list 1. The dialer-group is then specifying the 1, which links to the dialer-list 1. Dialer profiles Cisco's website states: "Dialer Profiles implementation of DDR is based on a separation between the logical and physical interface configurations. Dialer profiles also allow the logical and physical configurations to be bound together dynamically on a per-call basis." There are several advantages of Dialer Profiles over Legacy DDR; it is much more scalable than Legacy DDR because Legacy DDR is based on a static binding between the per-destination call and the physical interface configuration. Dialer profiles are point-to-point interfaces, which means we no longer need the Layer 3 to Layer 2 mapping (Layer 2 meaning the telephone number) since the profile can only dial a single location (hence point-to-point). Because the logical and physical configurations are dynamic, physical interfaces can take on different characteristics based on the logical call requirements that are utilizing the physical interface. The final advantage that we will include here is that it enables you to have a backup interface that isn't tying up one of the physical interfaces. Providing a spare interface is available, the backup can be used when it's required. Dialer profiles are made up of a dialer interface, dialer pool and physical interface. Optionally, you can also have a map class. These are highlighted in the table below: DIALER PROFILES:
Dialer Interface
This is the logical call requirements to the Point-to-Point connection. The following parameters can be configured; the IP address of the destination network (IP address address mask); Layer 2 encapsulation type -- for example, ppp (encapsulation ppp); PPP authentication (ppp authentication chap & pap); the remote router's authentication name (dialer remote-name username); the remote destination to call (dialer string dial-string); dialer pool mapping to use for calls to this destination (dialer pool number); assign dialer interface to a dialer group (dialer group number). There are other optional parameters such as PPP Multilink, idle timeout and more. Here we assign a physical interface into a dialer pool (dialer pool-member number) and assign any additional physical features, such as Layer 2 encapsulation (encapsulation ppp), ppp authentication (authentication chap), etc. Used to create a mapping between the remote IP address and phone number to dial in order to reach it.
Dialer Pool Used for a dialer interface to reference and be associated to a physical interface Physical Interface Map Class (Optional)
Steps in creating a Dialer Profile (assumes some of the basic steps above have already been configured, such as ISDN type): 1. 2. 3. 4. Define a Dialer Interface. Configure a Dialer String. Assign Physical Interface to a Dialer Pool, plus any additional Physical attributes. Other steps from the previous sections may need to be performed; for example, if you wanted to active the link using interesting traffic, DDR needs to be configured.
For example: Define Dialer Interface Router(config)#interface dialer1 Router(config-if)#ip address 10.10.10.1 255.255.255.0 Router(config-if)#encapsulation ppp Router(config-if)#ppp authentication chap Router(config-if)#dialer remote-name remote-office Router(config-if)#dialer string 999666
5 of 14
5/24/2012 7:07 PM
Router(config-if)#dialer pool 1 Router(config-if)#dialer-group 1 Router(config-if)#exit Configure Physical Interface Router(config)#interface bri0 Router(config-if)#encapsulation ppp Router(config-if)#dialer pool-member 1 Router(config-if)#ppp authentication chap Router(config-if)#exit Configure DDR to specify "Interesting" traffic (http) used to bring the line up Router(config)#access-list 101 permit tcp any any eq http Router(config)#dialer-list 1 protocol ip list 101
A simple example
The following example includes a variety of different items discussed in this document to help you see how they are applied in a real-case scenario. As always, depending on the security policies and network complexity, the configuration can change quite a bit. For simplicity, we've kept the complexity to a minimum. Our scenario is based upon two routers that occasionally need to connect their networks via an ISDN dial line, in order to transfer data between them.
Router 1 Remote Office Router1(config)#isdn switch-type basic-5ess Assign the switch type that we are connecting through to on the physical layer, AT&T Basic Rate Switch telco switch Router1(config)#interface dialer Create a dialer interface called dialer1 ready for configuring it Router1(config)#description Outgoing To HQ Set a description for this interface. Router1(config-if)#ip address 10.10.10.1 255.255.255.252 Assign an IP address to the virtual dialer interface Router1(config-if)#encapsulation ppp Configure the encapsulation used when we are connecting through this virtual interface Router1(config-if)#ppp authentication chap pap callin Set our ppp authentication to use chap, pap. The 'Callin' parameter ensures our router authenticates the remote router (HQ) on an incoming call. Since we are always the calling party, it does not expect the remote (HQ) router to authenticate, making this authentication process a one-way direction. Remote Office authenticates to the HQ router. Router1(config-if)#ppp chap hostname remote-office Set the username for chap authentication protocol Router1(config-if)#ppp chap password cisco Set the password for the chap authentication protocol Router1(config-if)#ppp pap sent-username remote-office password cisco Set the username and password for the pap authentication protocol. Router1(config-if)#dialer string 999666 Configure the telephone number to call when connecting through this virtual interface Router1(config-if)#dialer pool 1 Assign this virtual interface to use any physical interface that's assigned to pool number 1 Router1(config-if)#dialer-group 1
6 of 14
5/24/2012 7:07 PM
This is to define the interesting traffic that can be used to raise this virtual interface Router1(config-if)#dialer idle-timeout 300 Disconnect this call after 300 seconds of inactivity Router1(config-if)#ppp multilink Make this link 'ppp multilink' capable, allowing the aggregation of the two available 64K ISDN lines to a total of 128 Kbps. Router1(config-if)#dialer load-threshold 125 either When either the incoming or outgoing traffic reaches half of the available bandwidth (125), then bring up the 2nd ISDN channel. Router1(config-if)#exit Exits out of the interface sub command Router1(config)#interface bri0 Enters into the interface sub command on the physical interface bri0/0, ready for configuring the physical characteristics Router1(config-if)#encapsulation ppp Configure the encapsulation for this physical interface (optional command since we've already included it in the Dialer Interface) Router1(config-if)#dialer pool-member 1 Assign this physical interface to a pool. This allows this physical interface to be used by any virtual interface in this same pool. In this case, Dialer 1 Router1(config-if)#ppp authentication chap Set our ppp authentication to use chap (optional command since we've already included it in the Dialer Interface) Router1(config-if)#exit Exits out of the interface sub command Router1(config)#access-list 101 permit tcp any any eq http Access list used in defining interesting traffic. This line specifies that tcp port 80 traffic from anywhere to anywhere is interesting Router1(config)#dialer-list 1 protocol ip list 101 Maps the access-list with the dialer-group. As you can see, number 1 is used in the dialer-list and dialer-group statements Router1(config)#ip route 192.168.0.0 255.255.255.0 10.10.10.2 Creates a route to the 192.168.0.0/24 subnet to go through 10.10.10.2 (will use Dialer1 to get there since it's on the 10.10.10.0 subnet)
Router 2 Headquarters HQ(config)#username remote-office password cisco Assign the username and password the remote office router will use while authenticating to this router HQ(config)#isdn switch-type basic-5ess Assign the switch type that we are connecting through to on the physical layer, AT&T Basic Rate Switch telco switch HQ(config)#interface dialer1 Create a dialer interface called dialer1 ready for configuring it HQ(config)#description Incoming From Remote-Office Set a description for this interface. HQ(config-if)#ip address 10.10.10.2 255.255.255.252 Assign an IP address to the virtual dialer interface HQ(config-if)#encapsulation ppp Configure the encapsulation used when we are connecting through this virtual interface HQ(config-if)#ppp authentication chap pap callin Set our ppp authentication to use chap, pap. The 'Callin' parameter ensures our router authenticates the remote router (Remote Office) on an incoming call. Since we are always the called party, it will expect the remote router to authenticate. Remote Office authenticates to the HQ router. Username and password will be checked against the credentials we provided in the first line of this router's configuration. HQ(config-if)#dialer pool 1 Assign this virtual interface to use any physical interface that's assigned to pool number 1 HQ(config-if)#ppp multilink Make this link 'ppp multilink' capable, allowing the aggregation of the two available 64K ISDN lines to a total of 128 Kbps. HQ(config-if)#exit
7 of 14
5/24/2012 7:07 PM
Exits out of the interface sub command HQ(config)#interface bri0 Enters into the interface sub command on the physical interface bri0/0, ready for configuring the physical characteristics HQ(config-if)#encapsulation ppp Configure the encapsulation for this physical interface (optional command since we've already included it in the Dialer Interface) HQ(config-if)#dialer pool-member 1 Assign this physical interface to a pool. This allows this physical interface to be used by any virtual interface in this same pool. In this case, Dialer 1 HQ(config-if)#exit Exits out of the interface sub command HQ(config)#ip route 192.168.5.0 255.255.255.0 10.10.10.1 Creates a route to the 192.168.5.0/24 subnet to go through 10.10.10.1.
About the author:

Chris Partsenidis has more than eight years of experience as a senior network engineer, network administrator and network security consultant for companies in Australia, New Zealand and Greece. Chris has a bachelor's degree in electrical technology and holds the following certifications: CNA for Netware 3, 4, 5, CCNA, MCP, DCE (D-link Certified Engineer), LCP (Linux Certified Professional), Network+ and A+. In addition, Chris is the founder and senior editor of Firewall.cx -- a Web site recommended by Cisco Systems in their CCNA Academy program. His site now offers free access to Cisco lab equipment, allowing users to put in practice the theory covered in the ISDN article. For more information on networking, VPN security and firewalls, visit Firewall.cx, one of the few websites recommended by Cisco Systems in its world class Cisco Academy program.
Dig Deeper Articles ISDN implementation: Part 3 -- Cisco router ISDN configuration Can a Cisco 801 be configured on a dedicated 128KB ISDN line? I want my four remote locations to be able to dial any one main office and after doing data transfer Configuring an ISDN for the Internet How do I configure an ISDN connection on my Cisco router for Internet connection?
8 of 14
5/24/2012 7:07 PM
Related tags bri cisco configuration configure dialer example isdn isdn configuration pri router
Show me more This was first published in September 2007

Announcing SearchNetworking.co.UK; the Web's dedicated resource for IT pros in UK and Europe
Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk. Back to top This Content Component encountered an error
Get e-mail updates Submit your e-mail below to receive EnterpriseWAN-related news, tech tips and more, delivered to your inbox.
1.
Selecting Telecommunications Services and Providers
Not a member? We'll activate your FREE membership with your subscription.
Ads by Google Manage Microsoft WindowsStreamline Windows Administration and Management. Free 30-day Trialwww.systemtools.com fiber connectionsUE Tee connector Manufacturer High Quality fiber Fittingswww.chblqd.com
9 of 14
5/24/2012 7:07 PM
loading Arms from Chinamanufacture & design loading Arms complete sorts & info. Low price!www.dmco.com.cn VSAT Satellite InternetSatellite Internet for Africa VSAT, Ku-Band, C-Bandwww.telstream.co.za News
Latest Headlines
Web content optimization: A new approach to SharePoint optimization Ensuring Quality of Experience: Monitor networks or applications? Should you redesign WAN architecture for cloud and UC? View All News Enterprise WAN Topics
Topics
Telecom Services
Selecting telecommunications services and providers, Managed services, Cloud computing and SaaS
VPNs/Security
VPN design, VPN setup and configuration, Remote access, Internet and application security
WAN Design
Bandwidth and capacity planning, Branch office network design, Network disaster recovery, WWANs, VPN Design
Infrastructure
IP networks, Network Infrastructure, WAN protocols

Optimization/Application Performance
Application performance on the WAN, WAN network monitoring, WAN optimization and application acceleration
Hot Topics
Optimization/Application Performance VPNs/Security Infrastructure Tutorials

Guides
Advanced Workshops MPLS VPN fundamentals
10 of 14
5/24/2012 7:07 PM
VoIP over WAN tutorial

Technology Dictionary
Find definitions and links to technical resources Powered by WhatIs.com Expert Advice
Tips
Selecting WAN application visibility solutions Achieving application visibility through wide area network visibility Understanding application performance monitoring and management View All Tips
Answers
How can I allow and restrict user access on my VPN client? How do remote access VPNs compare with other types of VPNs? How can I make sure my VPN is encrypted and working properly? View All Answers
Ask a Question
Pose a question to the SearchEnterpriseWAN.com Experts Get help from our technical community Powered by ITKnowledgeExchange.com White Papers
Research Library
White Papers Business Webcasts Downloads Powered by Bitpipe.com

Product Demos
Try out software demos Powered by 2020Software.com Blogs

Blogs
Window on WANS Unified Communications Nation Powered by ITKnowledgeExchange.com Search this site
More from Related TechTarget Sites
Networking Mobile Computing Telecom
11 of 14
5/24/2012 7:07 PM
Unified Communications Networking Channel Networking UK Data Backup Networking

Will the DevOps movement simplify network automation?
Until now the DevOps movement has been lead by systems administrators, but now network engineers may find it also eases network automation and cloud orchestration.
BYOD policy: More than on-boarding and security
Experts say a BYOD policy will require network managers to reach across IT silos.
Combining NetFlow and packet analysis boosts network visibility
Packet analysis may provide a deeper look into the network, but NetFlow analysis can offer a broader view. To achieve even better network visibility the two work best together.
Mobile Computing
Bringing BYOD to your enterprise
Bring your own device (BYOD) can be a boon for both employees and enterprises, but clear policies and management tools are needed.
Meeting technical requirements for mobile health care deployments
IT departments deploying mobile health care solutions must ensure that using mobile devices in health care settings doesn't violate federal laws or compromise security.
Making the call: Distributed antenna systems and in-building wireless
Distributed antenna systems and in-building wireless solutions are two options to improve wireless cellular coverage within an enterprise facility. Telecom
Smartphone adoption spurs advanced services demand in Latin America
Latin American smartphone adoption is more robust than North America's, and the consumers are more mobilefriendly than their peers in developed economies.
Need for wireless network upgrade is key AT&T/T-Mobile driver
12 of 14
5/24/2012 7:07 PM
Rising demand for high-quality network service delivery will require operators to undertake a massive wireless network upgrade, driving deals like the AT&T/T-Mobile acquisition.
Video: ACG Research dissects telecom routing and switching market
In this ACG Research HotSeat video, Managing Partner Ray Mota gives viewers a quarterly update on the telecom service provider routing and switching market. Unified Communications
Integrating mobile device management with UC systems and features
Businesses need a plan to integrate their existing UC systems with their mobile device management and BYOD policy; building a matrix can give the project a logical start.
Enterprises turning to session management for UC interoperability
The use of session management middleware is being floated as a way to use SIP to improve UC interoperability for collaboration and UC apps.
Interop 2012: UC apps vendors must strive for interoperability
Vendors are aware of and gradually responding to issues around multi-vendor UC strategies and UC interoperability, according to a discussion panel at Interop 2012. Networking Channel
Partners learn to sell telemedicine solutions
Selling telemedicine solutions can be an opportunity for partner growth, but it comes with its share of technology and skill set challenges to overcome.
Think you can't make digital signage sales?
When video wall technology was expensive it was hard to sell. But selling digital signage has dropped in cost and many companies are now eager to replace static signs.
Cisco Partner Summit 2012: Support services, cloud and mobility reign
At Cisco Partner Summit 2012, Cisco continues its attempt to improve business by refocusing its channel partner strategy with support services, mobility and cloud announcements. Networking UK
Cisco Live London: 40 and 100 GbE, souped up WLAN
At Cisco Live London, Cisco launched 40 and 100 GbE switching, a souped-up 4-antenna WLAN access point, and a host of network virtualisation technologies.
UK Networkers should gear up for mobility implementations in 2012
Companies are rethinking legacy tools to take advantage of what users get from having access to data and applications across all kinds of devices, according to TechTargets 2012 IT Priorities Survey.
Cloud gets vote of confidence from UK buyers in 2012 IT priorities
The cloud is set to be a key investment area for UK buyers in 2012 with 30.5% of IT buyers pledging to spend on the technology, according to TechTargets 2012 IT Priorities Survey. searchDataBackup
13 of 14
5/24/2012 7:07 PM
SAN backup and recovery
Moving data can complicate your backup efforts. In this tip, youll learn backup goals for SAN environments and backup methods to achieve those goals.
Execs talk Backup Exec 2012, integrated appliances at Symantec Vision
Our senior news director Dave Raffo attended Symantec Vision last week, and we have compiled his reporting for your convenience.
Run virtual machines from backup without first restoring them
Find out how common it is to run virtual machines from backup without first restoring them in this Expert Response from Brien Posey. All Rights Reserved, Copyright 2009 - 2012, TechTarget About us Contact us Site index Privacy policy Advertisers Business partners Events Media kit TechTarget corporate site Reprints Site map
14 of 14
5/24/2012 7:07 PM

Cisco Router ISDN Configuration

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cisco Router ISDN Configuration

Uploaded by

Copyright:

Available Formats

Cisco router ISDN configuration

IP networks, Network Infrastructure, WAN protocols

Optimization/Application Performance VPNs/Security Infrastructure Tutorials