Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Computing > Cisco > ISDN connection troubleshooting.

Reply
Thread Tools

ISDN connection troubleshooting.

 
 
AM
Guest
Posts: n/a
 
      02-21-2005
This is the debug output of outgoing ISDN call

Feb 21 11:22:54.391 CET: ISDN Se3/0:15: Outgoing call id = 0x9099
Feb 21 11:22:54.391 CET: ISDN Se3/0:15: Event: Call to 0**9040368 at 64 Kb/s
Feb 21 11:22:54.395 CET: building outgoing channel id for call nfas_int is 0 le
n is 0
Feb 21 11:22:54.395 CET: ISDN Se3/0:15: TX -> SETUP pd = 8 callref = 0x0057
Feb 21 11:22:54.395 CET: Bearer Capability i = 0x8890
Feb 21 11:22:54.395 CET: Channel ID i = 0xA9838F
Feb 21 11:22:54.395 CET: Called Party Number i = 0x80, '0**9040368'
Feb 21 11:22:54.467 CET: ISDN Se3/0:15: RX <- SETUP_ACK pd = 8 callref = 0x805
7
Feb 21 11:22:54.471 CET: Channel ID i = 0xA9838F
Feb 21 11:22:54.471 CET: ISDN Se3/0:15: received CALL_ACCEPT call_id 0x9099
Feb 21 11:22:54.471 CET: ISDN Se3/0:15: PRI Event: CALL_ACCEPT, bchan = 14
Feb 21 11:22:57.859 CET: ISDN Se3/0:15: RX <- ALERTING pd = 8 callref = 0x8057
Feb 21 11:22:57.863 CET: ISDN Se3/0:15: received CALL_PROGRESSing call_id 0x9099
Feb 21 11:22:57.899 CET: ISDN Se3/0:15: RX <- CONNECT pd = 8 callref = 0x8057
Feb 21 11:22:57.899 CET: Connected Number i = 0x2183313139303430333638
Feb 21 11:22:57.899 CET: Locking Shift to Codeset 6
Feb 21 11:22:57.899 CET: Codeset 6 IE 0x1A i = 0xC2010000
Feb 21 11:22:57.903 CET: ISDN Se3/0:15: received CALL_CONNECT call_id 0x9099
Feb 21 11:22:57.935 CET: %LINK-3-UPDOWN: Interface Serial3/0:14, changed state to up
Feb 21 11:22:57.939 CET: ISDN Se3/0:15: received CALL_PROGRESSing call_id 0x9099
Feb 21 11:22:57.939 CET: ISDN Se3/0:15: TX -> CONNECT_ACK pd = 8 callref = 0x0057
Feb 21 11:22:58.183 CET: ISDN Se3/0:15: Event: Hangup call to call id 0x9099
Feb 21 11:22:58.183 CET: ISDN Se3/0:15: TX -> DISCONNECT pd = 8 callref = 0x0057
Feb 21 11:22:58.183 CET: Cause i = 0x8090 - Normal call clearing
Feb 21 11:22:58.263 CET: ISDN Se3/0:15: RX <- RELEASE pd = 8 callref = 0x8057
Feb 21 11:22:58.263 CET: Locking Shift to Codeset 6
Feb 21 11:22:58.263 CET: Codeset 6 IE 0x1A i = 0xC4010000
Feb 21 11:22:58.263 CET: ISDN Se3/0:15: entering process_rxstate, CALL_CLEARED call_id 0x9099
Feb 21 11:22:58.311 CET: %LINK-3-UPDOWN: Interface Serial3/0:14, changed state to down
Feb 21 11:22:58.315 CET: ISDN Se3/0:15: TX -> RELEASE_COMP pd = 8 callref = 0x0057
Feb 21 11:22:58.391 CET: ISDN Se3/0:15: Outgoing call id = 0x909A
Feb 21 11:22:58.391 CET: ISDN Se3/0:15: Event: Call to 0**9040368 at 64 Kb/s
Feb 21 11:22:58.391 CET: building outgoing channel id for call nfas_int is 0 len is 0
Feb 21 11:22:58.391 CET: ISDN Se3/0:15: TX -> SETUP pd = 8 callref = 0x0058
Feb 21 11:22:58.391 CET: Bearer Capability i = 0x8890
Feb 21 11:22:58.395 CET: Channel ID i = 0xA9838F
Feb 21 11:22:58.395 CET: Called Party Number i = 0x80, '0**9040368'
Feb 21 11:22:58.467 CET: ISDN Se3/0:15: RX <- SETUP_ACK pd = 8 callref = 0x8058
Feb 21 11:22:58.467 CET: Channel ID i = 0xA9838F
Feb 21 11:22:58.471 CET: ISDN Se3/0:15: received CALL_ACCEPT call_id 0x909A
Feb 21 11:22:58.471 CET: ISDN Se3/0:15: PRI Event: CALL_ACCEPT, bchan = 14
Feb 21 11:23:01.099 CET: ISDN Se3/0:15: RX <- ALERTING pd = 8 callref = 0x8058
Feb 21 11:23:01.103 CET: ISDN Se3/0:15: received CALL_PROGRESSing call_id 0x909A
Feb 21 11:23:01.143 CET: ISDN Se3/0:15: RX <- CONNECT pd = 8 callref = 0x8058
Feb 21 11:23:01.143 CET: Connected Number i = 0x2183313139303430333638
Feb 21 11:23:01.143 CET: Locking Shift to Codeset 6
Feb 21 11:23:01.147 CET: Codeset 6 IE 0x1A i = 0xC2010000
Feb 21 11:23:01.147 CET: ISDN Se3/0:15: received CALL_CONNECT call_id 0x909A
Feb 21 11:23:01.179 CET: %LINK-3-UPDOWN: Interface Serial3/0:14, changed state to up
Feb 21 11:23:01.183 CET: ISDN Se3/0:15: received CALL_PROGRESSing call_id 0x909A
Feb 21 11:23:01.183 CET: ISDN Se3/0:15: TX -> CONNECT_ACK pd = 8 callref = 0x0058
Feb 21 11:23:01.411 CET: ISDN Se3/0:15: Event: Hangup call to call id 0x909A
Feb 21 11:23:01.415 CET: ISDN Se3/0:15: TX -> DISCONNECT pd = 8 callref = 0x0058
Feb 21 11:23:01.415 CET: Cause i = 0x8090 - Normal call clearing
Feb 21 11:23:01.511 CET: ISDN Se3/0:15: RX <- RELEASE pd = 8 callref = 0x8058
Feb 21 11:23:01.511 CET: Locking Shift to Codeset 6
Feb 21 11:23:01.511 CET: Codeset 6 IE 0x1A i = 0xC4010000
Feb 21 11:23:01.511 CET: ISDN Se3/0:15: entering process_rxstate, CALL_CLEARED call_id 0x909A
Feb 21 11:23:01.559 CET: %LINK-3-UPDOWN: Interface Serial3/0:14, changed state to down
Feb 21 11:23:01.563 CET: ISDN Se3/0:15: TX -> RELEASE_COMP pd = 8 callref = 0x0058
Feb 21 11:23:02.391 CET: ISDN Se3/0:15: Outgoing call id = 0x909B
Feb 21 11:23:02.391 CET: ISDN Se3/0:15: Event: Call to 0**9040368 at 64 Kb/s
Feb 21 11:23:02.391 CET: building outgoing channel id for call nfas_int is 0 len is 0
Feb 21 11:23:02.391 CET: ISDN Se3/0:15: TX -> SETUP pd = 8 callref = 0x0059
Feb 21 11:23:02.391 CET: Bearer Capability i = 0x8890
Feb 21 11:23:02.395 CET: Channel ID i = 0xA9838F
Feb 21 11:23:02.395 CET: Called Party Number i = 0x80, '0**9040368'
Feb 21 11:23:02.467 CET: ISDN Se3/0:15: RX <- SETUP_ACK pd = 8 callref = 0x8059
Feb 21 11:23:02.471 CET: Channel ID i = 0xA9838F
Feb 21 11:23:02.471 CET: ISDN Se3/0:15: received CALL_ACCEPT call_id 0x909B
Feb 21 11:23:02.471 CET: ISDN Se3/0:15: PRI Event: CALL_ACCEPT, bchan = 14
Feb 21 11:23:05.159 CET: ISDN Se3/0:15: RX <- ALERTING pd = 8 callref = 0x8059
Feb 21 11:23:05.159 CET: ISDN Se3/0:15: received CALL_PROGRESSing call_id 0x909B
Feb 21 11:23:05.203 CET: ISDN Se3/0:15: RX <- CONNECT pd = 8 callref = 0x8059
Feb 21 11:23:05.203 CET: Connected Number i = 0x2183313139303430333638
Feb 21 11:23:05.203 CET: Locking Shift to Codeset 6
Feb 21 11:23:05.203 CET: Codeset 6 IE 0x1A i = 0xC2010000
Feb 21 11:23:05.207 CET: ISDN Se3/0:15: received CALL_CONNECT call_id 0x909B
Feb 21 11:23:05.239 CET: %LINK-3-UPDOWN: Interface Serial3/0:14, changed state to up
Feb 21 11:23:05.243 CET: ISDN Se3/0:15: received CALL_PROGRESSing call_id 0x909B
Feb 21 11:23:05.243 CET: ISDN Se3/0:15: TX -> CONNECT_ACK pd = 8 callref = 0x0059
Feb 21 11:23:05.487 CET: ISDN Se3/0:15: Event: Hangup call to call id 0x909B
Feb 21 11:23:05.487 CET: ISDN Se3/0:15: TX -> DISCONNECT pd = 8 callref = 0x0059
Feb 21 11:23:05.487 CET: Cause i = 0x8090 - Normal call clearing
Feb 21 11:23:05.567 CET: ISDN Se3/0:15: RX <- RELEASE pd = 8 callref = 0x8059
Feb 21 11:23:05.567 CET: Locking Shift to Codeset 6
Feb 21 11:23:05.567 CET: Codeset 6 IE 0x1A i = 0xC4010000
Feb 21 11:23:05.571 CET: ISDN Se3/0:15: entering process_rxstate, CALL_CLEARED call_id 0x909B
Feb 21 11:23:05.619 CET: %LINK-3-UPDOWN: Interface Serial3/0:14, changed state to down
Feb 21 11:23:05.623 CET: ISDN Se3/0:15: TX -> RELEASE_COMP pd = 8 callref = 0x0059

The link is not established but I don't know why.
I'm not used to work with ISDN devices. Can you tell me why the disconnection has cleared normally when it should be up?

Thanks a lot,

Alex.
 
Reply With Quote
 
 
 
 
M.C. van den Bovenkamp
Guest
Posts: n/a
 
      02-21-2005
AM wrote:

> The link is not established but I don't know why.
> I'm not used to work with ISDN devices. Can you tell me why the
> disconnection has cleared normally when it should be up?


It looks like the problem is at a higher layer. Try 'debug ppp
authentication' to see whether you have the correct
usernames/passwords/authentication method(s) set up.

Regards,

Marco.

 
Reply With Quote
 
 
 
 
Ben
Guest
Posts: n/a
 
      02-22-2005
M.C. van den Bovenkamp wrote:
> AM wrote:
>
>> The link is not established but I don't know why.
>> I'm not used to work with ISDN devices. Can you tell me why the
>> disconnection has cleared normally when it should be up?

>
>
> It looks like the problem is at a higher layer. Try 'debug ppp
> authentication' to see whether you have the correct
> usernames/passwords/authentication method(s) set up.
>
> Regards,
>
> Marco.
>


debug ppp negotiation also be a good bet to reveal something.
 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
CISCO 804 & ISDN PPP connect ISDN PMP BE749309 Cisco 0 06-09-2010 03:20 PM
VoIP to ISDN (to use old ISDN phones over VoIP) ? Martin Maurer UK VOIP 5 11-07-2008 02:35 PM
pc with isdn modem not connecte isdn 1841 router with isdn module sync Cisco 0 06-05-2007 10:10 AM
Cisco ISDN to Windows RAS ISDN SkY Cisco 0 03-31-2005 08:06 AM
Can you have failover to ISDN in a bridging environment with a standalone ISDN box? BobCov Cisco 3 11-21-2003 06:11 PM



Advertisments