Basic ISDN PRI E1 Configuration

[Muthurani Lavanya Paneerselvam]

• Introduction
• ISDN PRI E1 Configuration
• Related Information

Introduction

This document is intended to guide users who are new to Voice Technology and from other domain who need some basics on Integrated Service Digital Network ISDN PRI (Primary Rate Interface) E1 configuration for a Service Provider/ Telco and Enterprise Network.

ISDN PRI E1 Configuration

Customer Network has 2921 Router and there is a requirement to connect the ISDN PRI E1 with a Service Provider or Enterprise Network for Voice calls.

Procedure

1. Check the "Show Version" in 2921 Platform.

Below is 2921 with UCK9 Image: c2900-universalk9-mz.SPA.151-4.M4"

Show version on platform 29xx

2900-7#sh version System image file is "flash0:c2900-universalk9-mz.SPA.151-4.M4" Cisco CISCO2921/K9 (revision 1.0) with 479232K/45056K bytes of memory. 1 Channelized (E1 or T1)/PRI port License Info: License UDI: ------------------------------------------------- Device#   PID                   SN ------------------------------------------------- *0        CISCO2921/K9          FGL152611Y2 Technology Package License Information for Module:'c2900' ----------------------------------------------------------------- Technology    Technology-package           Technology-package                           Current          Type                Next reboot ------------------------------------------------------------------ ipbase             ipbasek9      Permanent      ipbasek9 security           None              None                None uc                     None              None               uck9 data                 None              None               None

2. Insert the VWIC card, and configure the Voice port.

3. With the UCK9 image, router doesnt allow to configure voice commands.

2900-7(config)#voice?

% Unrecognized command

4. From the "show version", UCK9 Technology package license is listed as "None" for both Current and Type.

We need to have the UCK9 Technology package license. For ISR-G2 29xx platform and the IOS being universal image, the package license is inbuilt and need to accept the User Agreement.

Configuration

Configuration Procedure: config t license boot module c2900 technology-package uck9 ACCEPT? [yes/no]:yes ! 2900-7(config)# Dec 25 06:11:14.767: %IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL: Module name = c2900 Next reboot level = uck9 and License = uck9 Dec 25 06:11:15.191: %LICENSE-6-EULA_ACCEPTED: EULA for feature uck9 1.0 has been accepted. UDI=CISCO2921/K9:FGL152611Y2; StoreIndex=1:Built-In License Storage Reload the 2900 Router and Accept the User Agreement as follows config t license accept end user agreement ACCEPT? [yes/no]:yes ! 2900-7(config)# Dec 25 06:11:46.467: %LICENSE-6-EULA_ACCEPT_ALL: The Right to Use End User License Agreement is accepted Save the Config and Reload the Router Give "Show version" and you can see the UCK9 Technology package as "EvalRightToUse" 2900-7#sh version System image file is "flash0:c2900-universalk9-mz.SPA.151-4.M4" Cisco CISCO2921/K9 (revision 1.0) with 479232K/45056K bytes of memory. 1 Channelized (E1 or T1)/PRI port License Info: License UDI: Technology Package License Information for Module:'c2900' ----------------------------------------------------------------- Technology    Technology-package           Technology-package                          Current                 Type           Next reboot ------------------------------------------------------------------ ipbase            ipbasek9              Permanent                 ipbasek9 security          None                      None                           None uc                    uck9                       EvalRightToUse       uck9 data                None                      None                           None Now you can start doing the Voice command configuration 2900-7(config)#voice? voice  voice-card

5. E1 PRI Configuration:

• Configure the card type for E1/T1 on ISR G2 platform

E1 PRI Configuration

1. Configure the E1/T1 card for the first time on ISR-G2 29xx platform config t card type e1 0 0 2900-7(config)# Dec 26 06:19:45.039: %CONTROLLER-5-UPDOWN: Controller E1 0/0/0, changed state to up 2.  E1/T1 card needs to be configured to use the Network clock for timings config t network-clock-participate wic 0 network-clock-select 1 e1 0/0/0 Dec 27 06:22:54.635: %MARS_NETCLK-3-CLK_TRANS: Network clock source transitioned from priority 10 to priority 1 3. Enable the ISDN Switch type as Primary-ni globally config t isdn switch-type primary-ni   4. Controller E1 and Pri group timeslot configuration. Example: Configure the Timeslot 1-10 for voice call to a specific service provider network. 2900-7(config)#controller e1 0/0/0 2900-7(config-controller)#pri-group timeslots 1-10 2900-7(config-controller)# Dec 27 06:23:10.155: %LINK-3-UPDOWN: Interface ISDN-VOICE 0/0/0:15(1), changed state to up Dec 27 06:23:10.155: %LINK-3-UPDOWN: Interface ISDN-VOICE 0/0/0:15(2), changed state to up Dec 27 06:23:10.155: %LINK-3-UPDOWN: Interface ISDN-VOICE 0/0/0:15(3), changed state to up Dec 27 06:23:10.155: %LINK-3-UPDOWN: Interface ISDN-VOICE 0/0/0:15(4), changed state to up Dec 27 06:23:10.155: %LINK-3-UPDOWN: Interface ISDN-VOICE 0/0/0:15(5), changed state to up Dec 27 06:23:10.155: %LINK-3-UPDOWN: Interface IS 2900-7(config-controller)#DN-VOICE 0/0/0:15(6), changed state to up Dec 27 06:23:10.155: %LINK-3-UPDOWN: Interface ISDN-VOICE 0/0/0:15(7), changed state to up Dec 27 06:23:10.155: %LINK-3-UPDOWN: Interface ISDN-VOICE 0/0/0:15(8), changed state to up Dec 27 06:23:10.155: %LINK-3-UPDOWN: Interface ISDN-VOICE 0/0/0:15(9), changed state to up Dec 27 06:23:10.155: %LINK-3-UPDOWN: Interface ISDN-VOICE 0/0/0:15(10), changed state to up Dec 27 06:23:11.123: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:0, changed state to down Dec 27 06:23:11.123: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:1, changed state to down Dec 27 06:23:11.123: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:2, changed state to down Dec 27 06:23:11.123: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:3, changed state to down Dec 27 06:23:11.123: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:4, changed state to down Dec 27 06:23:11.127: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial 2900-7(config-controller)#0/0/0:5, changed state to down Dec 27 06:23:11.127: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:6, changed state to down Dec 27 06:23:11.127: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:7, changed state to down Dec 27 06:23:11.127: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:8, changed state to down Dec 27 06:23:11.127: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0:9, changed state to down 5. Create the Serial interface for the PRI group and configure the D channel serial interface interface Serial0/0/0:15 no ip address encapsulation hdlc isdn switch-type primary-ni isdn incoming-voice voice no cdp enable ! 2900-7(config)#voice-port 0/0/0:15 2900-7(config-voiceport)#no shutdown ! 6. Give "Show isdn status" to check the PRI E1 activation status 2900-7#show isdn status Global ISDN Switchtype = primary-ni ISDN Serial0/0/0:15 interface         dsl 2, interface ISDN Switchtype = primary-ni     Layer 1 Status:         ACTIVE     Layer 2 Status:         TEI = 0, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED     Layer 3 Status:         0 Active Layer 3 Call(s)     Active dsl 2 CCBs = 0     The Free Channel Mask:  0x800003FF     Number of L2 Discards = 0, L2 Session ID = 0     Total Allocated ISDN CCBs = 0 MULTIPLE_FRAME_ESTABLISHED ---> Shows the PRI is successfull UP and Active.  Controller E1 is active and you can now route Calls to a Service provider /Enterprise network. 7. Configure the Dial-peer based on your number plans to route the Outgoing Calls and Incoming to the Service Provider / Enterprise network.

Related Information

• How to Route Outgoing calls through specific ISDN Channel in E1/T1?
• Configuring Trunk and Carrier based routing on Voice Gateway

[ceracaza08]

Dear mpaneers,

This post has been very informative and it's very beneficial for guys new to voice domain and i'm one of it.

Regards,

Chris

[Muthurani Lavanya Paneerselvam]

Thank you Christopher. I'm glad to hear you find it helpful.

Regards

Lavanya

[Jose Carlos Zamora Araya]

Very helpful. It is not very common to have a E1 configuration scenerio so you often forget the commands

[techsupport]

I do have valid license in place but my isdn interfaces doesn't came up as expected. find the relevant commands :

Technology Package License Information for Module:'c2900'

------------------------------------------------------------------------
Technology    Technology-package                  Technology-package
              Current              Type           Next reboot
------------------------------------------------------------------------
ipbase        ipbasek9             Permanent      ipbasek9
security      None                 None           None
uc            uck9                 Permanent      uck9
data          None                 None           None
NtwkEss       None                 None           None
CollabPro     None                 None           None

Configuration register is 0x2102

Router#

[Muthurani Lavanya Paneerselvam]

Hi

You can do the basic troubleshooting to bring up the isdn interface . Hope this link helps,

http://www.cisco.com/c/en/us/support/docs/wan/t1-e1-t3-e3/8131-T1-pri.html

Regards

Lavanya

[mutso]

Hope you can help me understand a bit more of the syntax if the E1 Serial Port?

I have my E1 ISDN working. Things are good.  I have a full 30 channel + D E1 connected to the Cisco.

This configuration line:

interface Serial0/0/0:15

Does this command suggest only 15 b channels?   I literally copied and pasted sample configurations to get this working.   Trying to change this to interface Serial0/0/0:30 does not work.

On initialization of the serial interface I will see all 30 channels go up:

Line protocol on Interface Serial0/0/1:30, changed state to up...

thanks in advance.

[Murali Gunnam]

Hi Mutso,

The ISDN serial interface would be created automatically after you configure the PRI channels and serial interface identification follows the below  syntax.

slot/sub-slot/port-number:B-Channel-Number

For E1 PRI, 16th channel(0-15) would be the B-Channel which is why the ISDN serial interface id would contain :15 and this cannot be altered.

It is :23 in case of T1 PRI as 24th Channel(0-23) is the B-Channel.

Kindly check below url for more information.

http://www.cisco.com/c/en/us/td/docs/ios/12_2/dial/configuration/guide/fdial_c/dafchant.html#wp1000918

Hope this answers your query....

[Ritesh Desai]

Thanks mate.... very usefull.

regards,

Ritesh Desai

[danielmaisu]

Thanks very useful.

I have one question. I have 2 e1 pri from same provider. First one is configured and working well.I want the second pri to be used as failover if first pri fails.

The same number range for direct in dials is mapped by the telco to both pri already.

How do I setup the voice gateway to give me failover on the e1 pri?

thanks

[Robert Shaw]

Hi,

Incoming calls can be serviced by one Dial-Peer using the statemements,

incoming called-number .

direct-inward-dial

forward-digits all

It doesn't matter which ISDN line calls come in on, your gateway will handle it.

As for outgoing, it depends on any restirctions from your Telco.  If you are able to use all channels available from both lines, I would use a Trunk Group to group the two lines together.  You then specify the trunk group in your outbound dial-peer.  That way oubound calls will always find a way out.

If you are only want to use one line at a time you will need to create two outbound dial-peers, specifically stating each port 0/0/0:15 and 0/0/1:15 for example and apply a preference to each Dial-peer to tell the gateway which port you want to use, then if that line is unavailable it will use the second preference.  It does also mean that it will attempt to use the second line if the number of calls is maxed out on the first line.  You should check with you provider to make sure you are able to use all channels assigned, usually you can with no problem.

This document contains some configuration examples for Trunkgroups and Dial-Peers.

http://www.cisco.com/c/en/us/td/docs/ios/12_2/dial/configuration/guide/fdial_c/dafntpri.pdf

Hope this helps, please rate useful posts.

Thanks
Rob

[danielmaisu]

Thanks Rob,

Very useful. I setup two outbound dial peers with preference and worked perfectly. Incoming calls also worked perfectly.

Thanks again

rgds,

Dan