Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Call out to 866 number delay

Discussion in '3CX Phone System - General' started by saltech, Aug 12, 2011.

Thread Status:
Not open for further replies.
  1. saltech

    Oct 9, 2009
    Likes Received:
    I am using latest 3cx v9.
    Cisco SPA-504g phones.
    Grandtstream gxw4108 with 8 lines.

    Things seem to be working ok, except when we try to call a particular 866 number:

    It takes 14 min to connect. I am stumped. Attached are log entrys for the particular call. Please offer some insight if you can. Thank you.

    13:18:21.412 [CM503008]: Call(1999): Call is terminated
    13:16:42.227 [CM503007]: Call(1999): Device joined: sip:10007@;transport=udp
    13:16:42.227 [CM503007]: Call(1999): Device joined: sip:114@
    13:16:42.211 [CM505002]: Gateway:[GS] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXW4108 (HW 2.0, Ch:15)] PBX contact: [sip:10007@]
    13:16:42.211 [CM503002]: Call(1999): Alerting sip:10007@;transport=udp
    13:16:41.384 Currently active calls - 1: [1999]
    13:16:11.198 Currently active calls - 1: [1999]
    13:15:41.012 Currently active calls - 1: [1999]
    13:15:10.826 Currently active calls - 1: [1999]
    13:13:10.082 Currently active calls - 1: [1999]
    13:12:39.896 Currently active calls - 1: [1999]
    13:10:51.023 [CM503025]: Call(1999): Calling PSTNline:18669068080@(Ln.10003@GS)@[Dev:sip:10006@;transport=udp]
    13:10:39.152 Currently active calls - 1: [1999]
    13:07:50.999 [CM503025]: Call(1999): Calling PSTNline:18669068080@(Ln.10003@GS)@[Dev:sip:10005@;transport=udp]
    13:05:37.291 Currently active calls - 2: [1995,1999]
    13:05:07.105 Currently active calls - 2: [1995,1999]
    13:04:50.990 [CM503025]: Call(1999): Calling PSTNline:18669068080@(Ln.10003@GS)@[Dev:sip:10003@;transport=udp]
    13:04:50.959 [CM503004]: Call(1999): Route 1: PSTNline:18669068080@(Ln.10003@GS)@[Dev:sip:10003@;transport=udp,Dev:sip:10005@;transport=udp,Dev:sip:10006@;transport=udp,Dev:sip:10007@;transport=udp,Dev:sip:10004@;transport=udp]
    13:04:50.959 [CM503010]: Making route(s) to <sip:18669068080@>
    13:04:50.959 [CM505001]: Ext.114: Device info: Device Identified: [Man: Cisco;Mod: SPA Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco/SPA504G-7.4.3a] PBX contact: [sip:114@]
    13:04:50.943 [CM503001]: Call(1999): Incoming call from Ext.114 to <sip:18669068080@>
  2. leejor

    leejor Well-Known Member

    Jan 22, 2008
    Likes Received:
    It almost looks like a gateway issue. The call is being sent to various trunks but doesn't seen to have success until it reaches 10007. Perhaps Wireshark could show you the messaging passing between 3Cx and the gateway. You could compare a working call and the difference between a call to one of the first "failed" trunks and then 10007. Is it alway able to complete on 10007, or does it eventually go through on other trunks? You may want to try some experiments (during off-hours) and busy out some of the trunks forcing calls out over specific trunks.

    I'm not sure why this would only happen on one specific number. With an analogue gateway, after 3CX sends the digits most gateways will act as if the called party has answered and an audio pathway will cut through. The only thing that may happen later, when the called party actually answers, is a current reversal, if the PSTN line, and the gateway is optioned to support this.
  3. eagle2

    eagle2 Well-Known Member

    Apr 27, 2011
    Likes Received:
    Check dialplan / codes in Grandstream - you may have this code doing something else.

    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.