Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Cisco: VOIP

Layer 2 down douring conversation: router does not receive Q921: Net RX <- UAf sapi=0 tei=0

 

 

Cisco voip RSS feed   Index | Next | Previous | View Threaded


akoul at dataways

Feb 6, 2007, 9:19 AM

Post #1 of 2 (17253 views)
Permalink
Layer 2 down douring conversation: router does not receive Q921: Net RX <- UAf sapi=0 tei=0

I have a cisco 2811 (CME, running 12.4(11)T) with one vic2-2bri connected with a Alcatel 4400 .
BRI port is configured as following:


interface BRI0/1/0
 no ip address
 isdn switch-type basic-qsig
 isdn timer T310 120000
 isdn overlap-receiving
 isdn protocol-emulate network
 isdn point-to-point-setup
 isdn layer1-emulate network
 isdn incoming-voice voice
 isdn static-tei 0
 isdn skipsend-idverify
!

!
voice-port 0/1/0
 compand-type a-law
 timeouts interdigit 5
 bearer-cap
Speech

!

Sometimes, during a call through that port, the call gets disconnected with the following message (marked red):


*Feb  6 10:55:17.949: ISDN BR0/1/0 Q931: RX <- SETUP pd = 8  callref = 0x0026
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech 
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA18382
                Preferred, Channel 2
        Progress Ind i = 0x8083 - Origination address is non-ISDN 
        Progress Ind i = 0xA090 - Reserved value 
        Calling Party Number i = 0x0181, '2310803800'
                Plan:ISDN, Type:Unknown
        Called Party Number i = 0x80, '999'
                Plan:Unknown, Type:Unknown
        High Layer Compat i = 0x9181
        Locking Shift to Codeset 5
        Codeset 5 IE 0x32  i = 0x80
*Feb  6 10:55:17.969: ISDN BR0/1/0 Q931: TX -> CALL_PROC pd = 8  callref = 0x8026
        Channel ID i = 0xA98382
                Exclusive, Channel 2
*Feb  6 10:55:17.993: ISDN BR0/1/0 Q931: TX -> ALERTING pd = 8  callref = 0x8026
*Feb  6 10:55:24.701: ISDN BR0/1/0 Q931: TX -> CONNECT pd = 8  callref = 0x8026
        Channel ID i = 0xA98382
                Exclusive, Channel 2
        Connected Number i = 0x80, '999'
*Feb  6 10:55:24.765: ISDN BR0/1/0 Q931: RX <- CONNECT_ACK pd = 8  callref = 0x0026
*Feb  6 10:56:31.977: ISDN BR0/1/0 **ERROR**: L2_AdvanceVA: TX_ack_queue empty
*Feb  6 11:08:07.312: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 0 changed to down
*Feb  6 11:08:07.312: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

*Feb  6 11:08:20.568: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 0 changed to up
*Feb  6 11:09:19.177: ISDN BR0/1/0 Q931: RX <- DISCONNECT pd = 8  callref = 0x0026
        Cause i = 0x809080 - Normal call clearing
*Feb  6 11:09:19.177: ISDN BR0/1/0 **ERROR**: L3_BadPeerMsg: event 0x45 cr 0x8026 callid 0x0
*Feb  6 11:09:19.181: ISDN BR0/1/0 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x8026
        Cause i = 0x80D1 - Invalid call reference value
*Feb  6 11:13:49.722: ISDN BR0/1/0 **ERROR**: L2_AdvanceVA: TX_ack_queue empty
voicegw#


when i turned q921 debug i saw that:
at some point, cisco sends a SABME message for multiple frame establish (why?).
If the router gets a reply:
RX <- UAf sapi=0 tei=0 the call does not fail (see debugging) and so RRp and RRf continue:

*Feb  6 12:26:00.165: ISDN BR0/1/0 Q921: Net TX -> RRf sapi=0 tei=0 nr=0
*Feb  6 12:26:01.089: ISDN BR0/1/0 Q921: L2_EstablishDataLink: sending SABME
*Feb  6 12:26:01.089: ISDN BR0/1/0 Q921: Net TX -> SABMEp sapi=0 tei=0
*Feb  6 12:26:01.185: ISDN BR0/1/0 Q921: Net RX <- SABMEp sapi=0 tei=0
*Feb  6 12:26:01.185: ISDN BR0/1/0 Q921: Net TX -> UAf sapi=0 tei=0
*Feb  6 12:26:02.089: ISDN BR0/1/0 Q921: Net TX -> SABMEp sapi=0 tei=0
*Feb  6 12:26:02.205: ISDN BR0/1/0 Q921: Net RX <- SABMEp sapi=0 tei=0
*Feb  6 12:26:02.205: ISDN BR0/1/0 Q921: Net TX -> UAf sapi=0 tei=0
*Feb  6 12:26:03.089: ISDN BR0/1/0 Q921: Net TX -> SABMEp sapi=0 tei=0

*Feb  6 12:26:03.101: ISDN BR0/1/0 Q921: Net RX <- UAf sapi=0 tei=0
*Feb  6 12:26:03.221: ISDN BR0/1/0 Q921: Net RX <- SABMEp sapi=0 tei=0
*Feb  6 12:26:03.225: ISDN BR0/1/0 Q921: Net TX -> UAf sapi=0 tei=0
*Feb  6 12:26:13.225: ISDN BR0/1/0 Q921: Net TX -> RRp sapi=0 tei=0 nr=0
*Feb  6 12:26:13.237: ISDN BR0/1/0 Q921: Net RX <- RRf sapi=0 tei=0 nr=0
*Feb  6 12:26:23.237: ISDN BR0/1/0 Q921: Net TX -> RRp sapi=0 tei=0 nr=0
*Feb  6 12:26:23.241: ISDN BR0/1/0 Q921: Net RX <- RRp sapi=0 tei=0 nr=0


if it gets no reply, the router (or alcatel?) drops L2 TEI 0, and so the call is dropped (see debugging of a dropped call)

*Feb  6 12:30:19.570: ISDN BR0/1/0 Q921: L2_EstablishDataLink: sending SABME
*Feb  6 12:30:19.570: ISDN BR0/1/0 Q921: Net TX -> SABMEp sapi=0 tei=0
*Feb  6 12:30:19.658: ISDN BR0/1/0 Q921: Net RX <- SABMEp sapi=0 tei=0
*Feb  6 12:30:19.658: ISDN BR0/1/0 Q921: Net TX -> UAf sapi=0 tei=0
*Feb  6 12:30:20.570: ISDN BR0/1/0 Q921: Net TX -> SABMEp sapi=0 tei=0
*Feb  6 12:30:20.678: ISDN BR0/1/0 Q921: Net RX <- SABMEp sapi=0 tei=0
*Feb  6 12:30:20.678: ISDN BR0/1/0 Q921: Net TX -> UAf sapi=0 tei=0
*Feb  6 12:30:21.570: ISDN BR0/1/0 Q921: Net TX -> SABMEp sapi=0 tei=0
*Feb  6 12:30:21.698: ISDN BR0/1/0 Q921: Net RX <- SABMEp sapi=0 tei=0
*Feb  6 12:30:21.698: ISDN BR0/1/0 Q921: Net TX -> UAf sapi=0 tei=0
*Feb  6 12:30:22.570: ISDN BR0/1/0 Q921: Net TX -> SABMEp sapi=0 tei=0
*Feb  6 12:30:22.718: ISDN BR0/1/0 Q921: Net RX <- SABMEp sapi=0 tei=0
*Feb  6 12:30:22.718: ISDN BR0/1/0 Q921: Net TX -> UAf sapi=0 tei=0
*Feb  6 12:30:23.570: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 0 changed to down
*Feb  6 12:30:23.570: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

*Feb  6 12:30:23.574: ISDN BR0/1/0 Q921: Net TX -> IDCKRQ ri=0 ai=0
*Feb  6 12:30:23.590: ISDN BR0/1/0 Q921: Net RX <- IDCKRP ri=0 ai=0
*Feb  6 12:30:58.734: ISDN BR0/1/0 Q921: Net RX <- SABMEp sapi=0 tei=0
*Feb  6 12:30:58.734: ISDN BR0/1/0 Q921: S4_SABME: Sending UA
*Feb  6 12:30:58.734: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 0 changed to up
*Feb  6 12:30:58.734: ISDN BR0/1/0 Q921: Net TX -> UAf sapi=0 tei=0
*Feb  6 12:30:58.790: ISDN BR0/1/0 Q921: Net RX <- INFO sapi=0 tei=0, ns=0 nr=0

Is there any possible idea why is this happening? In monday, i have a rendez-vous with the man who configured alcatel. Is there anything i can do till then?
Why the negotiation of multiple frame begins? Isn't multiple frame established since is point-to-point?
Since it gets established, why the router tries again?
And why sometimes alcatel does not reply?
I think i am going mad. That's why i don't like qsig and old PBXs interconnections with voip!!!

Thanks
Anthony



akoul at dataways

Feb 29, 2008, 3:37 AM

Post #2 of 2 (17059 views)
Permalink
Re: Layer 2 down douring conversation: router does not receive Q921: Net RX <- UAf sapi=0 tei=0 [In reply to]

Hi Oleksandr,
it was a matter of clocking!
All i had to do was make the Alcatel's side bri to be master (network side) and i configured my BRIs as slave (user side) with and the problem was immediately solved!!
It was very difficult for the Alcatel because they had no one to do it. But when the company hired a tech guy  supporting alcalel he found the solution and it worked!!
I don't know how you can configure Alcatel to be Network side but here is what i have for my cisco:

network-clock-participate wic 0
network-clock-participate wic 1
network-clock-select 1 BRI0/0/0
!
interface BRI0/0/0
 no ip address
 isdn switch-type basic-net3
 isdn overlap-receiving
 isdn point-to-point-setup
 isdn incoming-voice voice
 isdn static-tei 0
!
interface BRI0/0/1
 no ip address
 isdn switch-type basic-net3
 isdn overlap-receiving
 isdn point-to-point-setup
 isdn incoming-voice voice
 isdn static-tei 0
!
interface BRI0/1/0
 no ip address
 isdn switch-type basic-net3
 isdn overlap-receiving
 isdn point-to-point-setup
 isdn incoming-voice voice
 isdn static-tei 0
!
interface BRI0/1/1
 no ip address
 isdn switch-type basic-net3
 isdn overlap-receiving
 isdn point-to-point-setup
 isdn incoming-voice voice
 isdn static-tei 0

!      
2811voicegw#sh network-clocks
  Network Clock Configuration
  ---------------------------
  Priority      Clock Source    Clock State     Clock Type

     1          BRI0/0/0        GOOD            BRI        
    10          Backplane       GOOD            PLL        

  Current Primary Clock Source
  ---------------------------
  Priority      Clock Source    Clock State     Clock Type

     1          BRI0/0/0        GOOD            BRI        

2811voicegw#


I hope you don't mind if i post it in the cisco voip so anyone could have feedback on that.

Cheers
Anthony

AStrijchenko [at] microtest wrote:

Hi Anthony!

I have just read your post about BRI->Alcatel problem you had last February:

 

&#8220;I have a cisco 2811 (CME, running 12.4(11)T) with one vic2-2bri connected with a Alcatel 4400 .

BRI port is configured as following:&#8221;&#8230;&#8230;&#8230;&#8230;

 

*Feb  6 11:09:19.177: ISDN BR0/1/0 **ERROR**: L3_BadPeerMsg: event 0x45 cr 0x8026 callid 0x0

*Feb  6 11:09:19.181: ISDN BR0/1/0 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x8026

        Cause i = 0x80D1 - Invalid call reference value

*Feb  6 11:13:49.722: ISDN BR0/1/0 **ERROR**: L2_AdvanceVA: TX_ack_queue empty

voicegw#

 

when i turned q921 debug i saw that:

at some point, cisco sends a SABME message for multiple frame establish (why?).

If the router gets a reply: RX <- UAf sapi=0 tei=0 the call does not fail &#8230;&#8230;&#8230;&#8230;..

 

 

I am facing the same problem now. Were you able to fix the problem??? If yes, could you please tell  how ????

 

 

Best regards,

 

Oleksandr Stryzhchenko

Systems Engineer, Multiservice & Voice Team,

Anthony Kouloglou wrote:
I have a cisco 2811 (CME, running 12.4(11)T) with one vic2-2bri connected with a Alcatel 4400 .
BRI port is configured as following:


interface BRI0/1/0
 no ip address
 isdn switch-type basic-qsig
 isdn timer T310 120000
 isdn overlap-receiving
 isdn protocol-emulate network
 isdn point-to-point-setup
 isdn layer1-emulate network
 isdn incoming-voice voice
 isdn static-tei 0
 isdn skipsend-idverify
!

!
voice-port 0/1/0
 compand-type a-law
 timeouts interdigit 5
 bearer-cap
Speech

!

Sometimes, during a call through that port, the call gets disconnected with the following message (marked red):


*Feb  6 10:55:17.949: ISDN BR0/1/0 Q931: RX <- SETUP pd = 8  callref = 0x0026
        Sending Complete
        Bearer Capability i = 0x8090A3
                Standard = CCITT
                Transfer Capability = Speech 
                Transfer Mode = Circuit
                Transfer Rate = 64 kbit/s
        Channel ID i = 0xA18382
                Preferred, Channel 2
        Progress Ind i = 0x8083 - Origination address is non-ISDN 
        Progress Ind i = 0xA090 - Reserved value 
        Calling Party Number i = 0x0181, '2310803800'
                Plan:ISDN, Type:Unknown
        Called Party Number i = 0x80, '999'
                Plan:Unknown, Type:Unknown
        High Layer Compat i = 0x9181
        Locking Shift to Codeset 5
        Codeset 5 IE 0x32  i = 0x80
*Feb  6 10:55:17.969: ISDN BR0/1/0 Q931: TX -> CALL_PROC pd = 8  callref = 0x8026
        Channel ID i = 0xA98382
                Exclusive, Channel 2
*Feb  6 10:55:17.993: ISDN BR0/1/0 Q931: TX -> ALERTING pd = 8  callref = 0x8026
*Feb  6 10:55:24.701: ISDN BR0/1/0 Q931: TX -> CONNECT pd = 8  callref = 0x8026
        Channel ID i = 0xA98382
                Exclusive, Channel 2
        Connected Number i = 0x80, '999'
*Feb  6 10:55:24.765: ISDN BR0/1/0 Q931: RX <- CONNECT_ACK pd = 8  callref = 0x0026
*Feb  6 10:56:31.977: ISDN BR0/1/0 **ERROR**: L2_AdvanceVA: TX_ack_queue empty
*Feb  6 11:08:07.312: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 0 changed to down
*Feb  6 11:08:07.312: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

*Feb  6 11:08:20.568: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 0 changed to up
*Feb  6 11:09:19.177: ISDN BR0/1/0 Q931: RX <- DISCONNECT pd = 8  callref = 0x0026
        Cause i = 0x809080 - Normal call clearing
*Feb  6 11:09:19.177: ISDN BR0/1/0 **ERROR**: L3_BadPeerMsg: event 0x45 cr 0x8026 callid 0x0
*Feb  6 11:09:19.181: ISDN BR0/1/0 Q931: TX -> RELEASE_COMP pd = 8  callref = 0x8026
        Cause i = 0x80D1 - Invalid call reference value
*Feb  6 11:13:49.722: ISDN BR0/1/0 **ERROR**: L2_AdvanceVA: TX_ack_queue empty
voicegw#


when i turned q921 debug i saw that:
at some point, cisco sends a SABME message for multiple frame establish (why?).
If the router gets a reply:
RX <- UAf sapi=0 tei=0 the call does not fail (see debugging) and so RRp and RRf continue:

*Feb  6 12:26:00.165: ISDN BR0/1/0 Q921: Net TX -> RRf sapi=0 tei=0 nr=0
*Feb  6 12:26:01.089: ISDN BR0/1/0 Q921: L2_EstablishDataLink: sending SABME
*Feb  6 12:26:01.089: ISDN BR0/1/0 Q921: Net TX -> SABMEp sapi=0 tei=0
*Feb  6 12:26:01.185: ISDN BR0/1/0 Q921: Net RX <- SABMEp sapi=0 tei=0
*Feb  6 12:26:01.185: ISDN BR0/1/0 Q921: Net TX -> UAf sapi=0 tei=0
*Feb  6 12:26:02.089: ISDN BR0/1/0 Q921: Net TX -> SABMEp sapi=0 tei=0
*Feb  6 12:26:02.205: ISDN BR0/1/0 Q921: Net RX <- SABMEp sapi=0 tei=0
*Feb  6 12:26:02.205: ISDN BR0/1/0 Q921: Net TX -> UAf sapi=0 tei=0
*Feb  6 12:26:03.089: ISDN BR0/1/0 Q921: Net TX -> SABMEp sapi=0 tei=0

*Feb  6 12:26:03.101: ISDN BR0/1/0 Q921: Net RX <- UAf sapi=0 tei=0
*Feb  6 12:26:03.221: ISDN BR0/1/0 Q921: Net RX <- SABMEp sapi=0 tei=0
*Feb  6 12:26:03.225: ISDN BR0/1/0 Q921: Net TX -> UAf sapi=0 tei=0
*Feb  6 12:26:13.225: ISDN BR0/1/0 Q921: Net TX -> RRp sapi=0 tei=0 nr=0
*Feb  6 12:26:13.237: ISDN BR0/1/0 Q921: Net RX <- RRf sapi=0 tei=0 nr=0
*Feb  6 12:26:23.237: ISDN BR0/1/0 Q921: Net TX -> RRp sapi=0 tei=0 nr=0
*Feb  6 12:26:23.241: ISDN BR0/1/0 Q921: Net RX <- RRp sapi=0 tei=0 nr=0


if it gets no reply, the router (or alcatel?) drops L2 TEI 0, and so the call is dropped (see debugging of a dropped call)

*Feb  6 12:30:19.570: ISDN BR0/1/0 Q921: L2_EstablishDataLink: sending SABME
*Feb  6 12:30:19.570: ISDN BR0/1/0 Q921: Net TX -> SABMEp sapi=0 tei=0
*Feb  6 12:30:19.658: ISDN BR0/1/0 Q921: Net RX <- SABMEp sapi=0 tei=0
*Feb  6 12:30:19.658: ISDN BR0/1/0 Q921: Net TX -> UAf sapi=0 tei=0
*Feb  6 12:30:20.570: ISDN BR0/1/0 Q921: Net TX -> SABMEp sapi=0 tei=0
*Feb  6 12:30:20.678: ISDN BR0/1/0 Q921: Net RX <- SABMEp sapi=0 tei=0
*Feb  6 12:30:20.678: ISDN BR0/1/0 Q921: Net TX -> UAf sapi=0 tei=0
*Feb  6 12:30:21.570: ISDN BR0/1/0 Q921: Net TX -> SABMEp sapi=0 tei=0
*Feb  6 12:30:21.698: ISDN BR0/1/0 Q921: Net RX <- SABMEp sapi=0 tei=0
*Feb  6 12:30:21.698: ISDN BR0/1/0 Q921: Net TX -> UAf sapi=0 tei=0
*Feb  6 12:30:22.570: ISDN BR0/1/0 Q921: Net TX -> SABMEp sapi=0 tei=0
*Feb  6 12:30:22.718: ISDN BR0/1/0 Q921: Net RX <- SABMEp sapi=0 tei=0
*Feb  6 12:30:22.718: ISDN BR0/1/0 Q921: Net TX -> UAf sapi=0 tei=0
*Feb  6 12:30:23.570: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/1/0, TEI 0 changed to down
*Feb  6 12:30:23.570: ISDN BR0/1/0 Q931: Ux_DLRelInd: DL_REL_IND received from L2

*Feb  6 12:30:23.574: ISDN BR0/1/0 Q921: Net TX -> IDCKRQ ri=0 ai=0
*Feb  6 12:30:23.590: ISDN BR0/1/0 Q921: Net RX <- IDCKRP ri=0 ai=0
*Feb  6 12:30:58.734: ISDN BR0/1/0 Q921: Net RX <- SABMEp sapi=0 tei=0
*Feb  6 12:30:58.734: ISDN BR0/1/0 Q921: S4_SABME: Sending UA
*Feb  6 12:30:58.734: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/1/0, TEI 0 changed to up
*Feb  6 12:30:58.734: ISDN BR0/1/0 Q921: Net TX -> UAf sapi=0 tei=0
*Feb  6 12:30:58.790: ISDN BR0/1/0 Q921: Net RX <- INFO sapi=0 tei=0, ns=0 nr=0

Is there any possible idea why is this happening? In monday, i have a rendez-vous with the man who configured alcatel. Is there anything i can do till then?
Why the negotiation of multiple frame begins? Isn't multiple frame established since is point-to-point?
Since it gets established, why the router tries again?
And why sometimes alcatel does not reply?
I think i am going mad. That's why i don't like qsig and old PBXs interconnections with voip!!!

Thanks
Anthony


_______________________________________________ cisco-voip mailing list cisco-voip [at] puck https://puck.nether.net/mailman/listinfo/cisco-voip"]https://puck.nether.net/mailman/listinfo/cisco-voip

Cisco voip RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.