isdn doesn't identify itself

Discussion in 'Cisco' started by Sierp, Aug 6, 2004.

  1. Sierp

    Sierp Guest

    Hello all,

    I've got problem with isdn calling configuration (for future backup of FR).
    I've got cisco 3640A, on the other side there is cisco too.
    The problem is, that connection always disconnects after 20s.

    gateway#show isdn history
    --------------------------------------------------------------------------------
    ISDN CALL HISTORY
    --------------------------------------------------------------------------------
    Call History contains all active calls, and a maximum of 100 inactive calls.
    Inactive call data will be retained for a maximum of 15 minutes.
    --------------------------------------------------------------------------------
    Call Calling Called Remote Seconds Seconds Seconds Charges
    Type Number Number Name Used Left Idle Units/Currency
    --------------------------------------------------------------------------------
    Out 4422 06490128 20 1
    --------------------------------------------------------------------------------

    and I don't know why.. the other side tells me, that my router doesn't identify
    itself

    Jul 12 15:42:11 USERNAME 2515347: Jul 12 15:42:09.883: ISDN BR0: Event: Received a DATA call from <unknown> on <???> at 64 Kb/s

    and I think that is a problem...
    My configuration looks like this:

    username USERNAME password 7 10710534C335E95848
    isdn switch-type basic-net3


    interface BRI3/0
    ip address 1.1.1.2 255.255.255.252
    encapsulation ppp
    no ip route-cache
    no ip mroute-cache
    dialer map ip 1.1.1.1 name USERNAME broadcast 06490128
    isdn switch-type basic-net3
    isdn spid1 2264944220101
    isdn calling-number 4422
    isdn outgoing display-ie
    ppp authentication chap
    ppp chap hostname myUSERNAME
    ppp multilink
    !

    I'm testing it with
    isdn test call interface bri3/0 06490128

    Do you have any idea what can be wrong?

    And q931 logs below

    11w0d: %LINK-3-UPDOWN: Interface BRI3/0:1, changed state to up
    11w0d: %ISDN-6-CONNECT: Interface BRI3/0:1 is now connected to 06490128
    11w0d: %ISDN-6-DISCONNECT: Interface BRI3/0:1 disconnected from 06490128 , call lasted 20 seconds
    11w0d: %LINK-3-UPDOWN: Interface BRI3/0:1, changed state to down

    and event logs while calling

    11w0d: ISDN BR3/0: Outgoing call id = 0x8033, dsl 24
    11w0d: ISDN BR3/0: Event: Call to 06490128 at 64 Kb/s
    11w0d: ISDN BR3/0: process_bri_call(): call id 0x8033, called_number 06490128, speed 64, call type DATA
    11w0d: CCBRI_Go Fr Host InPkgInfo (Len=31) :
    11w0d: 1 18 1 80 33 0 4 2 88 90 18 1 83 6C 5 80 38 33 34 31 70 9 80 30 36 39 36 30 35 32 38
    11w0d:
    11w0d: CC_CHAN_GetIdleChanbri: dsl 24
    11w0d: Found idle channel B1
    11w0d: ISDN BR3/0: trigger_calling_called_debug, dsl 24, callref 0x32, outgoing TRUE
    11w0d: CCBRI_Go Fr L3 pkt (Len=7) :
    11w0d: 2 1 32 98 18 1 89
    11w0d:
    11w0d: ISDN BR3/0: LIF_EVENT: ces/callid 1/0x8033 HOST_PROCEEDING
    11w0d: CCBRI_Go Fr L3 pkt (Len=4) :
    11w0d: 1 1 32 94
    11w0d:
    11w0d: ISDN BR3/0: LIF_EVENT: ces/callid 1/0x8033 HOST_ALERTING
    11w0d: CCBRI_Go Fr L3 pkt (Len=24) :
    11w0d: 7 1 32 91 29 5 4 7 D C 1B 4C B 1 81 32 32 36 39 36 30 35 32 38
    11w0d:
    11w0d: ISDN BR3/0: LIF_EVENT: ces/callid 1/0x8033 HOST_CONNECT
    11w0d: %LINK-3-UPDOWN: Interface BRI3/0:1, changed state to up
    11w0d: ISDN: get_isdn_service_state(): idb 0x6211C9E0 bchan 2 is_isdn 1 Not a Pri
    11w0d: ISDN BR3/0: Event: Connected to 06490128 on B1 at 64 Kb/s
    11w0d: CCBRI_Go Fr L3 pkt (Len=27) :
    11w0d: 62 1 32 BD 1C 15 91 A1 12 2 1 22 2 1 22 30 A A1 5 30 3 2 1 1 82 1 0
    11w0d:
    11w0d: ISDN BR3/0: LIF_EVENT: ces/callid 1/0x8033 HOST_FACILITY_INVOKE
    11w0d: ISDN BR3/0: LIF_EVENT: ces/callid 1/0x8033 HOST_FACILITY
    11w0d: %ISDN-6-CONNECT: Interface BRI3/0:1 is now connected to 06490128
    11w0d: ISDN BR3/0: Event: Hangup call to call id 0x8033
    11w0d: ISDN BR3/0: process_disconnect(): call id 0x8033, call type is DATA, b_idb 0x6211C9E0, ces 1, cause Normal call clearing(0x10)
    11w0d: %ISDN-6-DISCONNECT: Interface BRI3/0:1 disconnected from 06490128 , call lasted 20 seconds
    11w0d: ISDN: get_isdn_service_state(): idb 0x6211C9E0 bchan 2 is_isdn 1 Not a Pri
    11w0d: CCBRI_Go Fr Host InPkgInfo (Len=13) :
    11w0d: 5 18 1 80 33 3 8 1 90 8 2 80 90
    11w0d:
    11w0d: CCBRI_Go Fr L3 pkt (Len=8) :
    11w0d: 4D 1 32 97 8 2 81 90
    11w0d:
    11w0d: ISDN BR3/0: LIF_EVENT: ces/callid 1/0x8033 HOST_DISCONNECT_ACK
    11w0d: ISDN: get_isdn_service_state(): idb 0x6211C9E0 bchan 2 is_isdn 1 Not a Pri
    11w0d: ISDN BR3/0: HOST_DISCONNECT_ACK: call type is DATA
    11w0d: %LINK-3-UPDOWN: Interface BRI3/0:1, changed state to down

    TIA for help, if any... :)

    Mariusz Preiss
     
    Sierp, Aug 6, 2004
    #1
    1. Advertisements

  2. Hi !
    Declare on each router all possible callers, and choose NOT-encrypted
    same passwords, here is relevant example for a 3620 which may be called
    by "rta" & "rtc" :

    hostname r_3620
    !
    username r_3620 password 0 isdn
    username rta password 0 isdn
    username rtc password 0 isdn
    !
    .............................
    !
    interface Serial0/0:15
    .............................
    encapsulation ppp
    dialer idle-timeout 60
    dialer map ip 10.2.2.3 name rta 210
    dialer map ip 10.2.2.4 name rtc 220
    .............................
    ppp authentication chap pap
    .............................

    Of course this is much too permissive but it "cannot" not work this way.
    You will enforce access after successul connections. In particular your
    levels of encryption may be uncompatible even if same level if chosen on
    both sides.

    Best regards.
     
    Eric LEMAITRE, Aug 6, 2004
    #2
    1. Advertisements

  3. Sierp

    Sierp Guest

    what do you mean by "all possible callers"?
    do I have to set both dialer maps on oeach router? or only the other
    side? (now I have only the other one)
    One more question - this 210 and 220 numbers - this are the telephone
    numbers, right?
    this I thought before :)
    but for sure my router doesn't identify by number - this is very strange
    not only for me..

    There is now no encryption (as shown in my configuration in first post)
    so I really don't understand what could be wrong...

    regards,

    Mariusz
     
    Sierp, Aug 9, 2004
    #3
  4. Hi !
    I mean all "username" lines.
    On each machine, dialer map for each machine you want to ping, each
    pingable IP address has a phone number.
    Yes, "210" and "220" are internal phone numbers for a PBX.

    Best regards.
     
    Eric LEMAITRE, Aug 10, 2004
    #4
    1. Advertisements

Ask a Question

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

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.