Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Receiving Ux_DLRelInd: DL_REL_IND received from L2 From Telco on E1

Hi,

This is a new E1 PRI line which we have taken from Telco in australia(Sydney), but the E1 is not coming up. As always Telco says everything is up on their side.

Layer 1 is active and Layer 2 is fluctuating between AWAITING_ESTABLISHMENT and TEI_ASSIGNED

Following is the configuration on the E1 PRI on voice gateway :

card type e1 0 0
card type e1 0 1

clock timezone GMT 0 0
network-clock-participate wic 0
network-clock-participate wic 1
network-clock-select 1 E1 0/0/0
network-clock-select 2 E1 0/0/1
network-clock-select 3 E1 0/1/0

controller E1 0/1/0
pri-group timeslots 1-31

interface Serial0/1/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-net5
isdn incoming-voice voice
!
ip forward-protocol nd


voice-port 0/0/1:15
echo-cancel coverage 64
cptone AU

Debug q921 output:

nvs-auno-ipt-vg01#

Jul 15 10:53:56.229 GMT: ISDN Se0/1/0:15 Q921: L2_EstablishDataLink: sending SABME

Jul 15 10:53:56.229 GMT: ISDN Se0/1/0:15 Q921: User TX -> SABMEp sapi=0 tei=0

Jul 15 10:53:57.229 GMT: ISDN Se0/1/0:15 Q921: User TX -> SABMEp sapi=0 tei=0

nvs-auno-ipt-vg01#

Jul 15 10:53:58.229 GMT: ISDN Se0/1/0:15 Q921: User TX -> SABMEp sapi=0 tei=0

Jul 15 10:53:59.229 GMT: ISDN Se0/1/0:15 Q921: User TX -> SABMEp sapi=0 tei=0

nvs-auno-ipt-vg01#

Jul 15 10:53:59.257 GMT: ISDN Se0/0/0:15 Q921: User RX <- RRp sapi=0 tei=0 nr=5

Jul 15 10:53:59.257 GMT: ISDN Se0/0/0:15 Q921: User TX -> RRf sapi=0 tei=0 nr=67

Jul 15 10:54:00.229 GMT: ISDN Se0/1/0:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2

Can somebody Advise what coule be the problem.

Thanks

Everyone's tags (5)
12 REPLIES
Hall of Fame Super Gold

Receiving Ux_DLRelInd: DL_REL_IND received from L2 From Telco on

Can somebody Advise what coule be the problem.

Most likely, not the router. Invite telso on premises, have them place test calls using their own test equipment, observe the results.

New Member

Any advice I can give to the

Any advice I can give to the Telco ?

We are getting this error in Abuja Nigeria on a new PRI install.

VIP Super Bronze

Keanej,How is Abuja this

Keanej,

How is Abuja this morning?

There are usually two things that could cause this issue..

1. cabling problem

2. Wrong setup on the telco side..

We need to see the ff:

sh controller e1 and debug isdn q921

If you are sending SABME packets to your telco and you are not getting any replies, then ask them to check that their end is setup correctly

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
New Member

No change ... Basically

No change ...

 

Basically getting this over and over

 


Apr 30 09:11:21.713 WAT: ISDN Se0/0/0:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2
Apr 30 09:11:26.713 WAT: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME
Apr 30 09:11:26.713 WAT: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Apr 30 09:11:27.713 WAT: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Apr 30 09:11:28.713 WAT: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Apr 30 09:11:29.713 WAT: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Apr 30 09:11:30.713 WAT: ISDN Se0/0/0:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2
Apr 30 09:11:35.713 WAT: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME
Apr 30 09:11:35.713 WAT: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Apr 30 09:11:36.713 WAT: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Apr 30 09:11:37.713 WAT: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Apr 30 09:11:38.713 WAT: ISDN Se0/0/0:15 Q921: User TX -> SABMEp sapi=0 tei=0
Apr 30 09:11:39.713 WAT: ISDN Se0/0/0:15 Q931: Ux_DLRelInd: DL_REL_IND received from L2
Apr 30 09:11:44.713 WAT: ISDN Se0/0/0:15 Q921: L2_EstablishDataLink: sending SABME

 

 

I have asked the Telco to

 

  1. Check Protocol set to Euro ISDN  / PRI Net5
  2. They are set to 'Protocol Emulate Network' / They are the network side, not user side
  3. and finally that their cabling is ok.

 

Its not looking like  much is happening ... sad

VIP Super Bronze

Your provider isn't

Your provider isn't responding to the SABME with a UA.  This is a provider issue.  Perhaps they don't have the circuit turned up completely.  If they push back, you will need to have them get a q.921 trap on their side and see if they see the SABME coming in, and if they show a UA in response.

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
New Member

Turned out to be a framing

Turned out to be a framing configuration issue (on my side !)

Cisco Employee

Re: Receiving Ux_DLRelInd: DL_REL_IND received from L2 From Telc

Have you verified that is the correct switch type for the far side?

Sent from Cisco Technical Support iPhone App

Hall of Fame Super Gold

Receiving Ux_DLRelInd: DL_REL_IND received from L2 From Telco on

Ronald Fallara wrote:

Have you verified that is the correct switch type for the far side?

Sent from Cisco Technical Support iPhone App

E1 PRI always use primary-net5. And even a 'wrong' switch type does not prevent circuit from coming up.

VIP Super Bronze

Receiving Ux_DLRelInd: DL_REL_IND received from L2 From Telco on

Hi,

All you can do is to check that everything is fine on your side. You can put the card into loopback mode and check that evrything comes up on the interface. You can do this by configuring

controller e1 0/0/0

loopback

You can also do a extensive hardplug loopback test

http://www.cisco.com/en/US/tech/tk713/tk628/technologies_tech_note09186a008010059a.shtml

Or you if you have a spare router you can configure them back to back. One of these tests will eliminate any doubt that you have a faulty hardware..You can then boldly match to your provider and let them earn their wages!

Please rate all useful posts

"'Nature is too thin a screen, the glory of the omnipresent God bursts through it everywhere"-Ralph Waldo Emerson

Please rate all useful posts "The essence of christianity is not the enthronement but the obliteration of self --William Barclay"
New Member

Ux_DLRelInd: DL_REL_IND

Ux_DLRelInd: DL_REL_IND received from L2

 

Getting this on a new PRI install in Africa.

 

Nightmare install - any ideas ?

New Member

Can you try bouncing the E1,

Can you try bouncing the E1, it may resolve the issue..

If bouncing the card doesnt

If bouncing the card doesnt fix the problem try to set the emulated mode to network.

 

int s0/0/0:15

isdn protocol-emulate network

 

Ideally your telco should be network and your side the user. But I have seen cases where the telco dont do this.

 

If the command doesnt fix the problem please take it off 

7397
Views
0
Helpful
12
Replies
CreatePlease to create content