Call out to 866 number delay

[saltech]

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:[email protected]:5074;transport=udp
13:16:42.227 [CM503007]: Call(1999): Device joined: sip:[email protected]:5060
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) 1.3.4.9] PBX contact: [sip:[email protected]:5060]
13:16:42.211 [CM503002]: Call(1999): Alerting sip:[email protected]:5074;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:[email protected]:5072;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:[email protected]:5070;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:[email protected]:5066;transport=udp]
13:04:50.959 [CM503004]: Call(1999): Route 1: PSTNline:18669068080@(Ln.10003@GS)@[Dev:sip:[email protected]:5066;transport=udp,Dev:sip:[email protected]:5070;transport=udp,Dev:sip:[email protected]:5072;transport=udp,Dev:sip:[email protected]:5074;transport=udp,Dev:sip:[email protected]:5068;transport=udp]
13:04:50.959 [CM503010]: Making route(s) to <sip:[email protected]>
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:[email protected]:5060]
13:04:50.943 [CM503001]: Call(1999): Incoming call from Ext.114 to <sip:[email protected]>

 

[leejor]

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.

 

[eagle2]

Check dialplan / codes in Grandstream - you may have this code doing something else.

Regards