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.

Outbound Calling Delay

Discussion in '3CX Phone System - General' started by ashon, Jan 12, 2017.

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

    Jan 12, 2017
    Likes Received:
    Trying to figure out what is causing a 10+ second outbound dialing delay. Version 14 on Server 2012 R2 64bit.

    Firewall Checker shows all green.

    Delay happens with 3CX softphone on Windows PCs as well as with Yealink desk phones.

    Below shows a problem call. Started call, nothing seemed to happen for 12 seconds, then call went out and was answered.

    11-Jan-2017 18:00:44.505 Leg L:10.2[Line:10000>>1616xxxxxxx] is terminated: Cause: BYE from PBX
    11-Jan-2017 18:00:44.504 [CM503008]: Call(C:10): Call is terminated
    11-Jan-2017 18:00:44.504 Leg L:10.1[Extn:117] is terminated: Cause: BYE from
    11-Jan-2017 18:00:41.823 [CM503007]: Call(C:10): Line:10000>>1616xxxxxxx has joined, contact <sip:231xxxxxxx@voip.acd.net:5060>
    11-Jan-2017 18:00:41.821 [CM503007]: Call(C:10): Extn:117 has joined, contact <sip:117@>
    11-Jan-2017 18:00:41.820 L:10.2[Line:10000>>1616xxxxxxx] has joined to L:10.1[Extn:117]
    11-Jan-2017 18:00:41.820 NAT/ALG check:L:10.2[Line:10000>>1616xxxxxxx] RESPONSE 200 on 'INVITE' - some of SIP/SDP headers contain inconsistent information or modified by intermediate hop
    SIP contact header is not equal to the SIP packet source(IP:port):
    Contact address:voip.acd.net:5060
    Received from :207.179.106.xxx:5060
    Media session IP ('c=' attribute) is not equal to the IP specified in contact header:
    Media session IP:207.179.106.xxx
    Contact IP:voip.acd.net
    Media session IP ('c=' attribute) is not equal to the SIP packet source(IP:port):
    Media session IP: 207.179.106.xxx
    Received from: 69.2.27.xxx
    11-Jan-2017 18:00:34.780 [CM505003]: Provider:[ACD] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:231xxxxxxx@69.2.27.xxx:5060]
    11-Jan-2017 18:00:22.972 [CM503025]: Call(C:10): Calling T:Line:10000>>1616xxxxxxx@[Dev:sip:231xxxxxxx@voip.acd.net:5060] for L:10.1[Extn:117]
    11-Jan-2017 18:00:22.921 [CM503027]: Call(C:10): From: Extn:117 ("Administrator" <sip:117@>) to T:Line:10000>>1616xxxxxxx@[Dev:sip:231xxxxxxx@voip.acd.net:5060]
    11-Jan-2017 18:00:22.921 [CM503004]: Call(C:10): Route 1: from L:10.1[Extn:117] to T:Line:10000>>1616xxxxxxx@[Dev:sip:231xxxxxxx@voip.acd.net:5060]
    11-Jan-2017 18:00:22.921 Line limit check: Current # of calls for line Lc:10000(@ACD[<sip:231xxxxxxx@voip.acd.net:5060>]) is 0; limit is 6
    11-Jan-2017 18:00:22.921 Call(C:10): Call from Extn:117 to 1616xxxxxxx matches outbound rule 'Rule for ACD'
    11-Jan-2017 18:00:22.920 [CM503001]: Call(C:10): Incoming call from Extn:117 to <sip:1616xxxxxxx@>

    I'm a bit lost on what to look at next. Any insight would be appreciated.
    Thank you.
  2. GiannosC_3CX

    GiannosC_3CX Guest

    Dear ashon,

    Please check below the call flow from your logs:

    The extension number 117 called to 1616xxxx external number.
    then the PBX matched with outbound rule 'Rule for ACD'
    and then the PBX sent an INVITE message to Voip provider

    The process has been completed between 18:00:22.920 and 18:00:22.972. At this point the PBX sent an INVITE Message to Voip Provider at 18:00:22.972 and the Voip Provider responded to your invite at 18:00:41.820,

    So the soft phones, IP phones and 3CX system phones as above logs, have been working properly. Please investigate more this issue between your network and Voip provider.

  3. ashon

    Jan 12, 2017
    Likes Received:
    Thank you for your response. I have put in a ticket in with the SIP Trunk provider.
Thread Status:
Not open for further replies.