<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Tom&#039;s Notes &#187; ddr</title>
	<atom:link href="http://wp.greenwood.net.nz/tag/ddr/feed/" rel="self" type="application/rss+xml" />
	<link>http://wp.greenwood.net.nz</link>
	<description>CCNA4 Notes - Term 2, 2009</description>
	<lastBuildDate>Thu, 02 Jul 2009 21:43:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Module 4 &#8211; ISDN and DDR</title>
		<link>http://wp.greenwood.net.nz/module-4-isdn-and-ddr/</link>
		<comments>http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#comments</comments>
		<pubDate>Sun, 14 Jun 2009 21:00:25 +0000</pubDate>
		<dc:creator>Tom GT</dc:creator>
				<category><![CDATA[Cisco CCNA4]]></category>
		<category><![CDATA[ddr]]></category>
		<category><![CDATA[isdn]]></category>

		<guid isPermaLink="false">http://wp.greenwood.net.nz/?p=37</guid>
		<description><![CDATA[Index

ISDN Concepts

ISDN Benefits
ISDN standards and access methods
ISDN 3-layer model and related standards
ISDN functions
ISDN reference points
Determining the router ISDN interface
ISDN switch types


ISDN Configuration

Configuring ISDN BRI
Configuring ISDN PRI
Verifying ISDN Configuration
Troubleshooting ISDN Configurations


DDR Configuration

DDR Operation
Configuring legacy DDR
Static Routes
Defining interesting traffic
Dialer Profiles
Debugging DDR configs




ISDN Concepts
ISDN Benefits
Traditional PSTN is based on an analog connection between the local exchange and the [...]]]></description>
			<content:encoded><![CDATA[<h3>Index</h3>
<ul>
<li><a href="http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#isdn-concepts">ISDN Concepts</a>
<ul>
<li><a href="http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#isdn-benefits">ISDN Benefits</a></li>
<li><a href="http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#isdn-standards">ISDN standards and access methods</a></li>
<li><a href="http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#isdn-3-layer">ISDN 3-layer model and related standards</a></li>
<li><a href="http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#isdn-functions">ISDN functions</a></li>
<li><a href="http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#isdn-ref-points">ISDN reference points</a></li>
<li><a href="http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#isdn-interface">Determining the router ISDN interface</a></li>
<li><a href="http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#isdn-switches">ISDN switch types</a></li>
</ul>
</li>
<li><a href="http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#isdn-config">ISDN Configuration</a>
<ul>
<li><a href="http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#isdn-config-bri">Configuring ISDN BRI</a></li>
<li><a href="http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#isdn-config-pri">Configuring ISDN PRI</a></li>
<li><a href="http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#verify-isdn">Verifying ISDN Configuration</a></li>
<li><a href="http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#troubleshoot-isdn">Troubleshooting ISDN Configurations</a></li>
</ul>
</li>
<li><a href="http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#isdn-config">DDR Configuration</a>
<ul>
<li><a href="http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#ddr-operation">DDR Operation</a></li>
<li><a href="http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#legacy-ddr">Configuring legacy DDR</a></li>
<li><a href="http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#static-routes">Static Routes</a></li>
<li><a href="http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#interesting-traffic">Defining interesting traffic</a></li>
<li><a href="http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#dialer-profiles">Dialer Profiles</a></li>
<li><a href="http://wp.greenwood.net.nz/module-4-isdn-and-ddr/#debug-ddr">Debugging DDR configs</a></li>
</ul>
</li>
</ul>
<p><span id="more-37"></span></p>
<h3><a style="text-decoration: none; color: #555555;" name="isdn-concepts">ISDN Concepts</a></h3>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="isdn-benefits">ISDN Benefits</a></strong></span></p>
<p>Traditional PSTN is based on an analog connection between the local exchange and the customer site. Analog links are limited in the available bandwidth.</p>
<p><span>ISDN was made possible by <span>telcos</span> upgrading switches to support digital signals over the local loop.</span></p>
<p>Some of the benefits include:</p>
<ul>
<li>Carries several different types of data</li>
<li>Faster to connect than analog</li>
<li><span>B channels offer more bandwidth than <span>dialup</span></span></li>
<li>B channels are able to be used with PPP</li>
</ul>
<p><span>The D channel is used to setup calls and signaling, and is either 16 or 64<span>kbps</span>.</span></p>
<p>Each B channel offers 64kbps of bandwidth.</p>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="isdn-standards">ISDN standards and access methods</a></strong></span></p>
<p>ISDN is made up by three series of protocols:</p>
<ul>
<li><strong>E protocols &#8211; </strong><span>defines telephone network <span>standards</span></span></li>
<li><strong>I protocols &#8211; </strong>defines concepts, terminology, and general methods. I.100 includes general ISDN concepts. I.200 defines service aspects. I.300 defines network aspects. I.400 defines how UNI is provided.</li>
<li><strong>Q protocols &#8211; </strong>defines how call setup and switching is handled.</li>
</ul>
<p><span>Unlike a standard TCP connection, ISDN uses out-of-band signalling, meaning all connections are <span>negotiatied</span> over the D channel, while data goes through the B channels.</span></p>
<p>B channels can carry digitized speech signals. They use either HDLC or PPP. PPP is more robust as it allows for authentication and negotiation of link and protocol configuration.</p>
<p>The D channel uses Link Access Procedure on the D Channel (LAPD) as its data link layer protocol.</p>
<p>North America and Japan PRI connections are 23B+D (giving T1), and most other countries use 30B+D (giving E1).</p>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="isdn-3-layer">ISDN 3-layer model and related standards</a><br />
</strong></span></p>
<p><span>BRI and PRI <span>pysical</span> layer specifications are  defined in ITU-T I.430 and I.431</span></p>
<p>ISDN data link layer is based on LAPD and is specified in ITU-T Q.920, Q.921, Q.922, and Q.923</p>
<p>The network layer is defined by ITU-T Q.930 and Q.931, also known as I.450 and I.451, respectively.</p>
<p>With a BRI connection, a standard phone line local loop is used. Although there is only one physical link, the 3 ISDN channels are multiplexed as to not require any extra physical links.</p>
<p>Each BRI frame on the physical layer has:</p>
<ul>
<li>8 bits from B1</li>
<li>8 bits from B2</li>
<li>2 bits from D</li>
<li>6 bits overhead</li>
</ul>
<p>4,000 frames are sent per second, giving a total of 192kbps, though 48kb of this is overhead, which makes for 144kbps of throughput.</p>
<p>The overhead bits are used for these purposes:</p>
<ul>
<li><strong>Framing &#8211; </strong>provides synchronization</li>
<li><strong>Load balancing &#8211; </strong>changes the average bit value</li>
<li><strong>Echo of previous D channel bits &#8211; </strong>used for contention resolution</li>
<li><strong>Activation bit &#8211; </strong>activates devices</li>
<li><strong>Spare bit &#8211; </strong>unassigned</li>
</ul>
<p>The ISDN signaling channel uses LAPD for Layer 2. The flag and control fields for LAPD are the same as in HDLC. The address field is 2 bytes long, made up of the following:</p>
<ul>
<li><strong>Service Address Point Identifier (SAPI) &#8211; </strong>identifies the  portal that is providing LAPD services to layer 3. One byte long</li>
<li><strong>Command/Response (C/R) bit &#8211; </strong>specifies if the command is a command or response</li>
<li><strong>Terminal Endpoint Identifier (TEI) &#8211; </strong>identifies the terminal, ranges between 0 and 63 if static, 64-126 if dynamic, and 127 for a broadcast. 7b long.</li>
</ul>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="isdn-functions">ISDN functions</a></strong></span></p>
<p>The D channel is always up, so that ISDN calls can be started.</p>
<p>The following steps are used to connect an ISDN call:</p>
<ol>
<li>Called number sent to local ISDN switch via D channel</li>
<li>The local switch sets up a connection to the remote ISDN switch using the SS7 protocol</li>
<li>The remote switch signals the remote site via the D channel</li>
<li>The remote site&#8217;s NT-1 device sends a call-connect message to the remote switch</li>
<li>The remote switch uses SS7 to forward the call-connect message to the local switch</li>
<li>The local switch connects one B channel to the remote site, leaving the other free for another conversation or data link, as both channels can be used at the same time.</li>
</ol>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="isdn-ref-points">ISDN reference points</a></strong></span></p>
<p>The following devices are used to facilitate ISDN connectivity:</p>
<ul>
<li><strong>Terminal Equipment 1 (TE1) &#8211; </strong><span>native ISDN device. <span>eg</span>. ISDN router or ISDN phone</span></li>
<li><strong>Terminal Equipment 2 (TE2) -</strong><span> non-ISDN device. <span>eg</span>. workstation or router. Requires TA to connect to ISDN service</span></li>
<li><strong>Terminal Adapter (TA) &#8211; </strong>Converts serial link into ISDN BRI</li>
<li><strong>Network Termination 2 &#8211; </strong>point at which the ISDN lines at the customer site are aggregated and switched using a customer switching device</li>
<li><strong>Network Termination 1 &#8211; </strong>controls the physical/electrical termination at the customer premises. Converts from 4 wire ISDN BRI to 2 line used over local loop</li>
</ul>
<p>The following are reference points used to identify connections between ISDN devices:</p>
<ul>
<li><strong>R &#8211; </strong>connection between TA and TE2</li>
<li><strong>S &#8211; </strong>connection between NT2 and customer premises equipment</li>
<li><strong>T &#8211; </strong>electrically identical to the S interface, referencing the outbound connection from the NT2 to the ISDN network or NT1</li>
<li><strong>U &#8211; </strong><span>link between the NT1 and the <span>telco</span> owned ISDN network</span></li>
</ul>
<p>As S and T connections are electrically identical, interfaces are often labeled as S/T, meaning they can perform either role.</p>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="isdn-interface">Determining the router ISDN interface</a></strong></span></p>
<p>For North America and Japan, a router should use an ISDN interface with the NT1 built in, as the NT1 is a customer premises device in these countries. These interfaces are labeled with a &#8216;U&#8217;</p>
<p><span>In other countries, the NT1 is usually provided by the <span>telco</span>, so the interface should not include an NT1. These interfaces are labeled with &#8216;S/T&#8217;</span></p>
<p>If the router doesn&#8217;t have a way to fit an ISDN interface, a TA is required, this will connect to a serial interface on the router.</p>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="isdn-switches">ISDN switch types</a></strong></span></p>
<p><span>As there are no fixed standards for D channel communication with ISDN switches, it is necessary </span>to specify the type on the router. The type of switch generally varies from country to country, though it can change within a country as well.</p>
<p>With some switches, a service profile identifier (SPID) is required. An SPID sets the line configuration, and allows for voice and data to both be carried over the local loop.</p>
<p>SPIDs are only used in North America and Japan.</p>
<p>Below is a table of the different switch types by country.</p>
<table border="0">
<tbody>
<tr>
<td><span style="text-decoration: underline;"><strong>Country</strong></span></td>
<td><span style="text-decoration: underline;"><strong>Switch Type</strong></span></td>
</tr>
<tr>
<td>US and Canada</td>
<td>AT&amp;T 5ESS and 4ESS; Northern Telecom DMS-100</td>
</tr>
<tr>
<td>France</td>
<td>VN2, VN3</td>
</tr>
<tr>
<td>Japan</td>
<td>NTT</td>
</tr>
<tr>
<td>UK</td>
<td>Net3 and Net5</td>
</tr>
<tr>
<td>Europe</td>
<td>Net3</td>
</tr>
</tbody>
</table>
<h3><a style="text-decoration: none; color: #555555;" name="isdn-config">ISDN Configuration</a></h3>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="isdn-config-bri">Configuring ISDN BRI</a></strong></span></p>
<p>To setup a BRI connection, use the following commands:</p>
<p><em>Router(config)# <strong>isdn switch-type [type]</strong></em></p>
<p><em>Router(config)#<strong> interface bri</strong><strong> [number]</strong></em></p>
<p>If required: <em>Router(config-if)# <strong>spid1 [spid-number] [ldn (optional)]<br />
</strong></em></p>
<p>If required: <em>Router(config-if)# <strong>spid2</strong></em><em><strong> [spid-number] [ldn (optional)]</strong></em></p>
<p><em><strong> </strong></em><em>Router(config-if)# <strong>no shutdown</strong></em></p>
<p><strong><span style="text-decoration: underline;"><a style="text-decoration: none; color: #555555;" name="isdn-config-pri">Configuring ISDN PRI</a></span></strong></p>
<p>To setup a PRI connection, use the following commands:</p>
<p><em>Router(config)#<strong> controller [t1 | e1]</strong><strong> </strong></em></p>
<p>For T1 lines: <em>Router(config-controller)# <strong>framing [sf | esf]<br />
</strong></em></p>
<p>For E1 lines: <em>Router(config-controller)# <strong>framing [crc4 | no-crc4] [australia (optional)]</strong></em></p>
<p><em>Router(config-controller)# <strong>linecode [ami | b8zs | hdb3]</strong></em> -  Nth America usually uses B8ZS, Europe usually uses HDB3.</p>
<p><em>Router(config-controller)# <strong>pri-group [timeslots range (1-24 for T1, 1-31 for E1)]</strong></em></p>
<p><em>Router(config)# <strong>interface serial [slot/port: | unit:] [23 (T1) | 15 (E1)]</strong></em></p>
<p><em>Router(config-if)# <strong>isdn switch-type [type]</strong></em></p>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="verify-isdn">Verifying ISDN configuration</a></strong></span></p>
<p><em>Router# <strong>show isdn status </strong></em>allows the isdn link to the local switch to be checked. When the link is working correctly, the layer 1 status will be &#8216;ACTIVE&#8217;, and the layer 2 status &#8216;MULTIPLE_FRAME_ESTABLISHED&#8217;</p>
<p><em>Router# <strong>show isdn active </strong></em>will give information regarding:</p>
<ul>
<li>called number</li>
<li>time until disconnect</li>
<li>Advice of Charge (AOC)</li>
<li>charging units used</li>
<li>whether AOC is provided during or after calls</li>
</ul>
<p><em>Router# <strong>show dialer</strong></em> shows the following details:</p>
<ul>
<li>current call status</li>
<li>dial timer config</li>
<li>dial reason</li>
<li>remote device that is connected</li>
</ul>
<p><em>Router# <strong>show interface bri 0/0 </strong></em>will display interface statistics.</p>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="troubleshoot-isdn">Troubleshooting ISDN configurations</a></strong></span></p>
<p><em>Router# <strong>debug isdn q921 </strong></em>displays layer 2 information related to the D channel. This command should be used if <em><strong>show isdn status</strong></em> doesn&#8217;t show layer 1 as &#8216;ACTIVE&#8217; and layer 2 as &#8216;MULTIPLE_FRAME_ESTABLISHED&#8217;</p>
<p><em>Router# <strong>debug isdn q931</strong></em> shows exchanged messages for call setup and teardown</p>
<p><em>Router# <strong>debug ppp authentication</strong></em> displays messages regarding PPP authentication</p>
<p><em>Router# <strong>debug ppp negotiation </strong></em>displays messages related to the PPP link configuration when the connection is started</p>
<p><em>Router# <strong>debug ppp error </strong></em>shows errors relating to PPP.</p>
<p>The <em><strong>debug ppp</strong></em> commands are for use when there are layer 2 issues and <em><strong>show isdn status</strong></em> doesn&#8217;t show any problems with the ISDN connection.</p>
<h3><a style="text-decoration: none; color: #555555;" name="ddr-config">DDR Configuration</a></h3>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="ddr-operation">DDR operation</a></strong></span></p>
<p>Dial-on-demand routing (DDR) is used to make a connection when an &#8216;interesting packet&#8217; needs to cross the link. Packets that are not interesting are forwarded only if the connection is already active. The protocols of which the packets are &#8216;interesing&#8217; are set with <strong><em>dialer-list.</em></strong></p>
<p>The following steps are used for an interesting packet to be forwarded using DDR:</p>
<ol>
<li>Router recieves packet, checks there is a valid route to the destination, and identifies the outbound interface</li>
<li>If the interface is connected to the next hop router, the packet is forwarded, if the interface is not connected, the packet is identified as interesting.</li>
<li>The router connects the the remote site. Now that the link is up, the packet is forwarded.</li>
<li>All packets to the remote site, whether interesting or not are forwarded over the link.</li>
<li>Once the set time limit has passed without an interesting packet, the call is terminated.</li>
</ol>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="legacy-ddr">Configuring legacy DDR</a></strong></span></p>
<p>Legacy DDR refers to having one connection set per interface.</p>
<p>Follow these steps to set up legacy DDR:</p>
<ol>
<li>Set the static routes</li>
<li>Define the interesting traffic</li>
<li>Set up the dialer information</li>
</ol>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="static-routes">Static Routes</a></strong></span></p>
<p>Static routes should be used over for connections with DDR, as using a dynamic routing protocol could cause the connection to be dialed more often than it is needed.</p>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="interesting-traffic">Defining interesting traffic</a></strong></span></p>
<p>Using <em><strong>dialer-list [no.] protocol ip permit</strong></em> allows all IP traffic, if more control is needed, an ACL can be used. Create the ACL and then use <em><strong>dialer-list [no.] protocol ip list [ACL no.]</strong></em></p>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="dialer-profiles">Dialer profiles</a></strong></span></p>
<p>Dialer profiles allow for a single ISDN interface to connect to different links as required. Several interfaces can also be used, so if, for example, there were three possible connections, but only 2 were ever required at once, the dialer could have 3 profiles in a pool with 2 interfaces.</p>
<p>When configuring dialer interfaces, the dialer pool membership is specified for the physical interface, with the other settings configured for each logical interface.</p>
<p><span style="text-decoration: underline;"><strong><a style="text-decoration: none; color: #555555;" name="debug-ddr">Debugging DDR configs</a></strong></span></p>
<p><em><strong>debug dialer [events | packets]</strong></em> will help diagnose problems with the DDR configuration.</p>
]]></content:encoded>
			<wfw:commentRss>http://wp.greenwood.net.nz/module-4-isdn-and-ddr/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
