ISDN connection troubleshooting.

Discussion in 'Cisco' started by AM, Feb 21, 2005.

  1. AM

    AM Guest

    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.
     
    AM, Feb 21, 2005
    #1
    1. Advertising

  2. 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.
     
    M.C. van den Bovenkamp, Feb 21, 2005
    #2
    1. Advertising

  3. AM

    Ben Guest

    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.
     
    Ben, Feb 22, 2005
    #3
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. BobCov
    Replies:
    3
    Views:
    614
    Andre Beck
    Nov 21, 2003
  2. SkY
    Replies:
    0
    Views:
    983
  3. Martin Maurer
    Replies:
    5
    Views:
    14,752
    moc.hooha
    Nov 7, 2008
  4. sync
    Replies:
    0
    Views:
    593
  5. BE749309
    Replies:
    0
    Views:
    1,222
    BE749309
    Jun 9, 2010
Loading...

Share This Page