VoIP bandwidth calculator...
Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors

Quintum Tenor 30 Minute Call Limit

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • 4th March 2008 at 13:03 #31719
    Stefan
    Guest

    Our company is currently running 1 Quintum DX and 2 Quintum AF gateways. We are experiencing an issue across all the gateways where a call has a limit of 30 minutes whereafter it will be disconnected.

    I have checked the MaxTalkTime under all the relevant IPRG’s and have tested with both “0” and “-1” settings, neither solved the problem.

    We are running a 3Com VCX server and I have communicated with them on this issue, but they insist that the problem has to be with the gateways are they are 100% sure that it can’t be the VCX server.

    Has anyone else experienced this issue?

    5th March 2008 at 03:58 #31720
    MikeM to Stefan
    Guest

    Interesting problem. If you have reviewed the maxtalk time (both iprg and tcrg) and see no setting there to 30, then it may not be the quintum. You first need to determine where the disconnect is orig from. To do this, you should run a ch event log from both orig and term side, put a call up and see where the call disc from.

    MikeM
    mike_voip@hotmail.com

    5th March 2008 at 06:59 #31721
    Stefan
    Guest

    I put up a call with the monitoring enabled on the gateway (the DX) and received the following output in the event log:

    ————— START LOG DATA —————

    ch |01/01| 2008/03/05|08:19:40:485 |sip[0/0]: chsipTG: SIP CallID :call-714BC969-B9CC-2A10-0A1A-2287
    sip[0/0]: SipReleaseComplete rcvd at SipTermCall
    sip[27527/0]: tsipcall:RcvRelComp, cause=16
    CallInfo[27527]: disconnected event. cause=16 legno=1 leg=1 sentLeg=0.

    CallInfo [27527]: discTickm(448245816) connTickm(447881608) duration (1821)
    .
    tsi disconnect: 1016 113 11
    OBCSM[27527]: Release from peer=0x960c8308 cause=0x10 redir=.
    TBCSM [27527]: Release complete from peer=0x9684fcc8.
    sip[0/0]: sipTG::term releaseCall:remove call from list

    OBCSM[27527]: pRouteInfo 968b44d8 state 8 ivrType 0 h323RetCode -1 cause 10.
    CallInfo[27527]: disconnected event. cause=16 legno=0 leg=1 sentLeg=0.

    CallInfo [27527]: discTickm(448245816) connTickm(447881608) duration (1821)
    .
    CallInfo[27527]: send eventDisconnected 1821.
    PRI(2,0,2,0×2286): sending DISC_REQ to L3.
    ch |01/01| 2008/03/05|08:19:40:530 |PRI(2,0,2,0×9581): received DISC_IND from L3.
    PRI(2,0,2,0×9581): sending CLEAR_REQ to L3.
    CallInfo[27526]: disconnected event. cause=16 legno=1 leg=1 sentLeg=0.

    CallInfo [27526]: discTickm(448245825) connTickm(447881618) duration (1821)
    .
    tsi disconnect: 093 1005 11
    OBCSM[27526]: Release from peer=0x967b3ccc cause=0x10 redir=.
    TBCSM [27526]: Release complete from peer=0x96024e10.
    OBCSM[27526]: pRouteInfo 96921cd8 state 8 ivrType 0 h323RetCode -1 cause 10.
    CallInfo[27526]: disconnected event. cause=16 legno=0 leg=1 sentLeg=0.

    CallInfo [27526]: discTickm(448245825) connTickm(447881618) duration (1821)
    .
    CallInfo[27526]: send eventDisconnected 1821.

    ————— END LOG DATA —————

    The cause code is 16 which translates to “Normal Call Clearing – This is one of the most common cause codes and is received for many reasons. It usually occurs
    because someone hung up the call at one side or the other.”

    This has me thinking that 3Com is wrong and that it must be some setting on the VCX.

    5th March 2008 at 14:23 #31722
    MikeM to Stefan
    Guest

    The msg that is telling is;

    sip[0/0]: SipReleaseComplete rcvd at SipTermCall

    Tells me that the other end of the SIP connection term. This could also be the SIP server itself.

    MikeM
    mike_voip@hotmail.com

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