Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors

Tenor -DX ISDN Issue

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • 29th January 2007 at 16:16 #31321
    Kalpan
    Guest

    I get a cause code 96 returned from the ISDN side when I make an outbound call from the Quintum. I do not know what information element I am missing. Here is the setup message being sent to L3:

    TBCSM[52]: Setup from peer=0x960ccca0 NP=0x1 NT=0x2.
    OrigNum=9739460103 NormNum=9739460103 TranNum=9739460103 OrigDest=.
    PriTermCall: [52] PRI: Using default ANI=8662489355.
    ch |01/01| 2007/01/29|11:46:41:495 |PRI(2,0,1,0×8002): sending SETUP_REQ to L3.
    Set TxPayload(101) and RxPayload(101)
    sproto |01/01| 2007/01/29|11:46:41:495 |[ua]:Received Iuca Message from CH

    Here is the return code from the PRI-ISDN side:

    PRI(2,0,1,0×8002): received CLEAR_IND from L3.
    CallInfo[52]: disconnected event. cause=96 legno=1 leg=1 sentLeg=0.

    CallInfo [52]: discTickm(288678) connTickm(0) duration (0)

    Please help.
    Thanks,
    Kalpan

    30th January 2007 at 19:38 #31322
    MikeM to Kalpan
    Guest

    Kalpan,

    This could be a difficult thing to troubleshoot without getting your ISDN provider involved to tell you what is missing.

    You may want to look at the ISDN events by doing the following;

    ev l3 pri_dec 1..1
    ev c
    ev qu

    Mikem
    mike_voip@hotmail.com

    2nd May 2007 at 12:31 #31323
    Julian
    Guest

    I have the same problem, but it is a outgoing call originating at my PBX then isdn to Tenor DX then SIP to a SIP gateway.

    Did you find a solution?

    2nd May 2007 at 20:07 #31324
    MikeM to Julian
    Guest

    Julian,

    Then again, my answer is pretty much the same. I would need to see logs and such to check out the ISDN message and the real cause code and other information to see what is exactly happening.

    MikeM
    mike_voip@hotmail.com

    3rd May 2007 at 09:05 #31325
    Julian
    Guest

    I seemed to fix the problem.
    I switched from NI2 Signalling to QSIG which I have read as being the best for “inter PBX signalling”
    I no longer get the information element missing problem. My logs gave exactly the same return code from the PRI-ISDN side as Kalpan.

    3rd May 2007 at 12:51 #31326
    MikeM Julian
    Guest

    Julian,

    that is good news.

    MikeM
    mike_voip@hotmail.com

  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 total)
  • The forum ‘Voice over IP’ is closed to new topics and replies.