[c-nsp] pri problem
Vincent De Keyzer
vincent at dekeyzer.net
Thu Jan 27 05:29:14 EST 2005
Elke,
ISDN status should be :
eads#sh isdn status
Global ISDN Switchtype = primary-net5
ISDN Serial0/0/0:15 interface
dsl 0, interface ISDN Switchtype = primary-net5
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 0 CCBs = 0
The Free Channel Mask: 0xFFFF7FFF
Number of L2 Discards = 0, L2 Session ID = 1
Total Allocated ISDN CCBs = 0
(i'm in Belgium too)
You should send the output of the Q.921 debug to Belgacom showing that the
SABME messages are not answered.
"Show controller E1" looks fine, I imagine?...
Vincent
> -----Original Message-----
> From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-
> bounces at puck.nether.net] On Behalf Of CLAEREBOUDT Elke
> Sent: jeudi 27 janvier 2005 11:17
> To: Dave Temkin
> Cc: cisco-nsp at puck.nether.net
> Subject: RE: [c-nsp] pri problem
>
> For me it's also a provider problem, but they already went twice on site
> and concluded the rpoblem is on the router
>
> CPE-UNI-CENTRAL-01#sh isdn st
> ISDN Serial2/1:15 interface
> dsl 1, interface ISDN Switchtype = primary-net5
> Layer 1 Status:
> ACTIVE
> Layer 2 Status:
> TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED
> Layer 3 Status:
> 0 Active Layer 3 Call(s)
> Active dsl 1 CCBs = 0
> The Free Channel Mask: 0xFFFF7FFF
> Total Allocated ISDN CCBs = 0
> CPE-UNI-CENTRAL-01#
>
>
> -----Original Message-----
> From: Dave Temkin [mailto:dave at ordinaryworld.com]
> Sent: Thursday 27 January 2005 11:04
> To: CLAEREBOUDT Elke
> Cc: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] pri problem
>
> With the lack of any <- RX info coming back and the fact that TEI still
> shows as 0, I'd have to assume that it's a carrier or physical cabling
> issue.
>
> Can you send the output of show isdn stat?
>
>
>
> On Thu, 27 Jan 2005, CLAEREBOUDT Elke wrote:
>
> > Hi,
> >
> >
> >
> > Suddenly our isdn backup doesn't work anymore. We openend a ticket at
> > our provider (belgacom), but they claim the problem is on our router.
> We
> > changed the config from controler E1 2/0 to E1 2/1 but same problem.
> >
> > I include here some debugging information, because I can't find
> anything
> > on CCO
> >
> >
> >
> > controller E1 2/1
> >
> > pri-group timeslots 1-31
> >
> > !
> >
> > interface Serial2/1:15
> >
> > description === Local number = xxxx ===
> >
> > ip unnumbered FastEthernet2/0
> >
> > encapsulation ppp
> >
> > dialer string xxx
> >
> > dialer-group 1
> >
> > isdn switch-type primary-net5
> >
> > isdn T310 60000
> >
> > no cdp enable
> >
> > ppp authentication chap
> >
> > ppp chap hostname xxx
> >
> > ppp chap password xxx
> >
> > !
> >
> > !
> >
> > ip route 2.2.2.2 255.255.255.255 Serial2/1:15
> >
> >
> >
> > CPE-xxx-01#p 2.2.2.2
> >
> >
> >
> > Type escape sequence to abort.
> >
> > Sending 5, 100-byte ICMP Echos to 2.2.2.2, timeout is 2 seconds:
> >
> >
> >
> > Jan 27 10:10:56.012: Se2/1:15 DDR: Dialing cause ip (s=193.78.48.254,
> > d=2.2.2.2)
> >
> > Jan 27 10:10:56.012: Se2/1:15 DDR: Attempting to dial 038003510
> >
> > Jan 27 10:10:56.012: ISDN Se2/1:15: Outgoing call id = 0x8005, dsl 1
> >
> > Jan 27 10:10:56.012: ISDN Se2/1:15: Event: Call to 038003510 at 64
> Kb/s
> >
> > Jan 27 10:10:56.012: ISDN Se2/1:15: process_pri_call(): call id
> 0x8005,
> > number 038003510, speed 64, call type DATA
> >
> > Jan 27 10:10:56.012: building outgoing channel id for call nfas_int
> is
> > 0 len is 0
> >
> > Jan 27 10:10:56.016: ISDN Se2/1:15: TX -> SABMEp c/r = 0 sapi = 0
> tei
> > = 0.
> >
> > Jan 27 10:10:57.016: ISDN Se2/1:15: TX -> SABMEp c/r = 0 sapi = 0
> tei
> > = 0
> >
> > Jan 27 10:10:58.016: ISDN Se2/1:15: TX -> SABMEp c/r = 0 sapi = 0
> tei
> > = 0.
> >
> > Jan 27 10:10:59.016: ISDN Se2/1:15: TX -> SABMEp c/r = 0 sapi = 0
> tei
> > = 0
> >
> > Jan 27 10:11:00.020: ISDN Se2/1:15: Event: received NL_REL_IND
> >
> > Jan 27 10:11:00.020: ISDN Se2/1:15: CCPRI_ReleaseCall(): bchan 31,
> call
> > id 0x8005, call type DATA
> >
> > Jan 27 10:11:00.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 31
> >
> > Jan 27 10:11:00.024: CCPRI_ReleaseChan released b_dsl 1 B_Chan 31
> >
> > Jan 27 10:11:00.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 1
> >
> > Jan 27 10:11:00.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 2
> >
> > Jan 27 10:11:00.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 3
> >
> > Jan 27 10:11:00.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 4
> >
> > Jan 27 10:11:00.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 5
> >
> > Jan 27 10:11:00.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 6
> >
> > Jan 27 10:11:00.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 7
> >
> > Jan 27 10:11:00.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 8
> >
> > Jan 27 10:11:00.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 9
> >
> > Jan 27 10:11:00.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 10
> >
> > Jan 27 10:11:00.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 11
> >
> > Jan 27 10:11:00.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 12
> >
> > Jan 27 10:11:00.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 13
> >
> > Jan 27 10:11:00.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 14
> >
> > Jan 27 10:11:00.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 15
> >
> > Jan 27 10:11:00.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 17
> >
> > Jan 27 10:11:00.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 18
> >
> > Jan 27 10:11:00.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 19
> >
> > Jan 27 10:11:00.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 20
> >
> > Jan 27 10:11:00.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 21
> >
> > Jan 27 10:11:00.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 22
> >
> > Jan 27 10:11:00.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 23
> >
> > Jan 27 10:11:00.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 24
> >
> > Jan 27 10:11:00.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 25
> >
> > Jan 27 10:11:00.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 26
> >
> > Jan 27 10:11:00.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 27
> >
> > Jan 27 10:11:00.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 28
> >
> > Jan 27 10:11:00.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 29
> >
> > Jan 27 10:11:00.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 30
> >
> > Jan 27 10:11:00.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 31
> >
> > Jan 27 10:11:00.028: ISDN Se2/1:15: LIF_EVENT: ces/callid 1/0x8005
> > CALL_DISC
> >
> > Jan 27 10:11:00.028: ISDN Se2/1:15: Got a disconnect on a non-existent
> > call id = 0x8005.
> >
> > Jan 27 10:11:00.028: Serial2/1:15: wait for isdn carrier timeout, call
> > id=0x8005
> >
> > Jan 27 10:11:00.032: ISDN Se2/1:15: LIF_EVENT: ces/callid 1/0x8005
> > CALL_CLEARED
> >
> > Jan 27 10:11:00.032: ISDN Se2/1:15: received CALL_CLEARED call_id
> > 0x8005
> >
> > Jan 27 10:11:00.032: ISDN Se2/1:15: Got a disconnect on a non-existent
> > call id = 0x8005..
> >
> > Jan 27 10:11:02.012: Se2/1:15 DDR: Dialing cause ip (s=193.78.48.254,
> > d=2.2.2.2)
> >
> > Jan 27 10:11:02.012: Se2/1:15 DDR: Attempting to dial 038003510
> >
> > Jan 27 10:11:02.012: ISDN Se2/1:15: Outgoing call id = 0x8006, dsl 1
> >
> > Jan 27 10:11:02.012: ISDN Se2/1:15: Event: Call to 038003510 at 64
> Kb/s
> >
> > Jan 27 10:11:02.012: ISDN Se2/1:15: process_pri_call(): call id
> 0x8006,
> > number 038003510, speed 64, call type DATA
> >
> > Jan 27 10:11:02.012: building outgoing channel id for call nfas_int
> is
> > 0 len is 0
> >
> > Jan 27 10:11:02.016: ISDN Se2/1:15: TX -> SABMEp c/r = 0 sapi = 0
> tei
> > = 0.
> >
> > Jan 27 10:11:03.016: ISDN Se2/1:15: TX -> SABMEp c/r = 0 sapi = 0
> tei
> > = 0
> >
> > Jan 27 10:11:04.016: ISDN Se2/1:15: TX -> SABMEp c/r = 0 sapi = 0
> tei
> > = 0.
> >
> > Success rate is 0 percent (0/5)
> >
> > CPE-UNI-CENTRAL-01#
> >
> > CPE-UNI-CENTRAL-01#
> >
> > CPE-UNI-CENTRAL-01#
> >
> > Jan 27 10:11:05.016: ISDN Se2/1:15: TX -> SABMEp c/r = 0 sapi = 0
> tei
> > = 0
> >
> > Jan 27 10:11:06.024: ISDN Se2/1:15: Event: received NL_REL_IND
> >
> > Jan 27 10:11:06.024: ISDN Se2/1:15: CCPRI_ReleaseCall(): bchan 31,
> call
> > id 0x8006, call type DATA
> >
> > Jan 27 10:11:06.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 31
> >
> > Jan 27 10:11:06.024: CCPRI_ReleaseChan released b_dsl 1 B_Chan 31
> >
> > Jan 27 10:11:06.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 1
> >
> > Jan 27 10:11:06.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 2
> >
> > Jan 27 10:11:06.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 3
> >
> > Jan 27 10:11:06.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 4
> >
> > Jan 27 10:11:06.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 5
> >
> > Jan 27 10:11:06.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 6
> >
> > Jan 27 10:11:06.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 7
> >
> > Jan 27 10:11:06.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 8
> >
> > Jan 27 10:11:06.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 9
> >
> > Jan 27 10:11:06.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 10
> >
> > Jan 27 10:11:06.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 11
> >
> > Jan 27 10:11:06.024: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 12
> >
> > Jan 27 10:11:06.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 13
> >
> > Jan 27 10:11:06.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 14
> >
> > Jan 27 10:11:06.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 15
> >
> > Jan 27 10:11:06.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 17
> >
> > Jan 27 10:11:06.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 18
> >
> > Jan 27 10:11:06.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 19
> >
> > Jan 27 10:11:06.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 20
> >
> > Jan 27 10:11:06.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 21
> >
> > Jan 27 10:11:06.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 22
> >
> > Jan 27 10:11:06.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 23
> >
> > Jan 27 10:11:06.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 24
> >
> > Jan 27 10:11:06.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 25
> >
> > Jan 27 10:11:06.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 26
> >
> > Jan 27 10:11:06.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 27
> >
> > Jan 27 10:11:06.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 28
> >
> > Jan 27 10:11:06.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 29
> >
> > Jan 27 10:11:06.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 30
> >
> > Jan 27 10:11:06.028: CC_CHAN_ReleaseChanpri for DSL 1 B-chan 31
> >
> > Jan 27 10:11:06.028: ISDN Se2/1:15: LIF_EVENT: ces/callid 1/0x8006
> > CALL_DISC
> >
> > Jan 27 10:11:06.028: ISDN Se2/1:15: Got a disconnect on a non-existent
> > call id = 0x8006.
> >
> > Jan 27 10:11:06.032: Serial2/1:15: wait for isdn carrier timeout, call
> > id=0x8006
> >
> > Jan 27 10:11:06.032: ISDN Se2/1:15: LIF_EVENT: ces/callid 1/0x8006
> > CALL_CLEARED
> >
> > Jan 27 10:11:06.032: ISDN Se2/1:15: received CALL_CLEARED call_id
> > 0x8006
> >
> > Jan 27 10:11:06.032: ISDN Se2/1:15: Got a disconnect on a non-existent
> > call id = 0x8006.
> >
> > CPE-UNI-CENTRAL-01#
> >
> > CPE-UNI-CENTRAL-01#und all
> >
> > All possible debugging has been turned off
> >
> > CPE-UNI-CENTRAL-01#
> >
> >
> >
> > Thx for any feedback
> >
> >
> >
> > Elke
> >
> >
> >
> > *****DISCLAIMER*****
> >
> > This electronic transmission (and any attached document) is intended
> > exclusively for the person or entity to whom it is addressed and may
> > contain confidential and/or privileged material.
> > Any disclosure, copying, distribution or other action based upon
> > the information by persons or entities other than the intended
> recipient
> > is prohibited. If you receive this message in error, please contact
> the
> > sender and delete the material from any and all computers.
> > Mobistar does not warrant a proper and complete transmission of this
> > information, nor does it accept liability for any delays.
> >
> > *****END OF DISCLAIMER*****
> >
> > _______________________________________________
> > cisco-nsp mailing list cisco-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
>
>
> *****DISCLAIMER*****
>
> This electronic transmission (and any attached document) is intended
> exclusively for the person or entity to whom it is addressed and may
> contain confidential and/or privileged material.
> Any disclosure, copying, distribution or other action based upon
> the information by persons or entities other than the intended recipient
> is prohibited. If you receive this message in error, please contact the
> sender and delete the material from any and all computers.
> Mobistar does not warrant a proper and complete transmission of this
> information, nor does it accept liability for any delays.
>
> *****END OF DISCLAIMER*****
>
>
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
More information about the cisco-nsp
mailing list