Openvox B100P + mISDN drop L1link randomly

Discussion in 'Gateways' started by Tib85, Apr 8, 2010.

  1. Tib85

    Joined:
    Apr 8, 2010
    Messages:
    3
    Likes Received:
    0
    Hello!

    I have elastix 1.6 with Openvox B100P ISDN Bri card.
    Usually it works great, but sometimes misdn drop L1Link and then i cant dial-in or dial-out.
    In asterisk CLI I tried L1Link up, with misdn port up 1 command, but it did not work.

    Code:
    elastix*CLI> misdn show stacks
    BEGIN STACK_LIST:
      * Port 1 Type TE Prot. PMP L2Link DOWN L1Link:DOWN Blocked:0  Debug:2

    When i try call out:

    Code:
       -- Executing [s@macro-dialout-trunk:26] Dial("SIP/3002-09716d08", "misdn/1/458|300|") in new stack
    P[ 0]  --> * NEW CHANNEL dad:458 oad:(null)
    P[ 1] read_config: Getting Config
    P[ 1]  --> TON: Unknown
    P[ 1]  --> LTON: Unknown
    P[ 1]  --> CTON: Unknown
    P[ 1] * CALL: 1/458
    P[ 1]  --> * dad:2458 tech:mISDN/0-u6 ctx:ISDN-be
    P[ 1]  --> pres: -1 screen: -1
    P[ 1]  --> pres: 0
    P[ 1]  --> PRES: Allowed (0)
    P[ 1]  --> SCREEN: Unscreened (0)
    P[ 1] NO OPTS GIVEN
    P[ 1] I SEND:SETUP oad:3002 dad:458 pid:8
    P[ 1]  --> channel:0 mode:TE cause:16 ocause:16 rad: cad:
    P[ 1]  --> info_dad: onumplan:0 dnumplan:0 rnumplan:0 cpnnumplan:0
    P[ 1]  --> * SEND: State Dialing pid:8
        -- Called 1/458
    P[ 1]  --> queue_hangup
    P[ 1] * RELEASING CHANNEL pid:8 ctx:ISDN-be dad:458 oad:2458 state: CALLING
    P[ 1] empty_chan_in_stack: cannot empty channel 255
      == Everyone is busy/congested at this time (1:0/0/1)
        -- Executing [s@macro-dialout-trunk:27] Goto("SIP/3002-09716d08", "s-CHANUNAVAIL|1") in new stack
        -- Goto (macro-dialout-trunk,s-CHANUNAVAIL,1)
    
    When the L1link is up, everything works well.

    Why cant get L1link? misdn restart or elastix restart did not solve this problem. Its sometimes works sometimes does not.

    How can I fix L1Link?

    Sorry for my bad english:)

    Regards, Tib
     
  2. Joe.Yung

    Joined:
    Nov 5, 2009
    Messages:
    15
    Likes Received:
    0
    Hello Tib,
    If possible,please send your SSH account to me and let me have a check.

    joe.yung@openvox.cn
    Joe
     
  3. james.zhu

    Joined:
    Feb 13, 2008
    Messages:
    99
    Likes Received:
    0
    hello:
    please check the modem and service provider. sometimes, the ISDN modem or far-side server(NT) will be into sleeping mode to save power.
     
  4. Tib85

    Joined:
    Apr 8, 2010
    Messages:
    3
    Likes Received:
    0
    Hi guys,

    thank you for your help.
    I think my ISDN PBX is the source of problem.
    I tried with dahdi, the result is same.
    When everything OK, in asterisk CLI is saw the next DAHDI message:
    Code:
    
    > [ 00 81 01 1b ]
    
    > Supervisory frame:
    > SAPI: 00  C/R: 0 EA: 0
    >  TEI: 064        EA: 1
    > Zero: 0     S: 0 01: 1  [ RR (receive ready) ]
    > N(R): 013 P/F: 1
    > 0 bytes of data

    When disconnected:
    Code:
    -- Timeout occured, restarting PRI
    q921.c:468 t200_expire: q921_state now is Q921_LINK_CONNECTION_RELEASED
    q921.c:858 q921_reset: q921_state now is Q921_LINK_CONNECTION_RELEASED
    Sending TEI management message 1, TEI=127
    
    > [ fc ff 03 0f 37 cb 01 ff ]
    
    > Unnumbered frame:
    > SAPI: 63  C/R: 0 EA: 0
    >  TEI: 127        EA: 1
    >   M3: 0   P/F: 0 M2: 0 11: 3  [ UI (unnumbered information) ]
    > 5 bytes of data
    > MDL Message: TEI Identity Request (1)
    > RI: 14283
    > Ai: 127 E:1
    Sending TEI management message 1, TEI=127
    
    > [ fc ff 03 0f 44 3a 01 ff ]
    
    > Unnumbered frame:
    > SAPI: 63  C/R: 0 EA: 0
    >  TEI: 127        EA: 1
    >   M3: 0   P/F: 0 M2: 0 11: 3  [ UI (unnumbered information) ]
    > 5 bytes of data
    > MDL Message: TEI Identity Request (1)
    > RI: 17466
    > Ai: 127 E:1
    Sending TEI management message 1, TEI=127
    
    If I know the TEI:127 is a broadcast message, and I think problem that I am not getting a TEI number.
     
  5. Tib85

    Joined:
    Apr 8, 2010
    Messages:
    3
    Likes Received:
    0
    The problem is resolved, the problem was our ISDN PBX.
     

Share This Page