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.

Few seconds of silence on inbound call

Discussion in '3CX Phone System - General' started by mitch2k, Jan 25, 2013.

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

    Joined:
    Nov 6, 2012
    Messages:
    3
    Likes Received:
    0
    Hi,

    when I receive an inbound call, and I pick up the phone, it takes 2-3 seconds before I hear the caller. This is pretty frustrating because if you say hello when you pick up, the caller won't hear it.

    I looked in the logs, and seen some errors, but not sure if they are 'normal'. These is the log of a recent call:

    Code:
    25-01-2013 09:36:28.706   Leg L:71.1[Line:10000<<3227588780] is terminated: Cause: BYE from PBX
    25-01-2013 09:36:28.706   [CM503008]: Call(C:71): Call is terminated
    25-01-2013 09:36:28.706   [CM503023]: Call(C:71): Call recording is stopped, audio file: C:\ProgramData\3CX\Data\Recordings\602\[Priv%C3%A9%3A3227588780]_3227588780-602_20130125093523(71).wav
    25-01-2013 09:36:28.705   Leg L:71.4[Extn] is terminated: Cause: BYE from 192.168.1.200:5060
    25-01-2013 09:36:11.240   Currently active calls - 1: [71]
    25-01-2013 09:35:39.238   Currently active calls - 1: [71]
    25-01-2013 09:35:25.170   Leg L:76.1[Queue] is terminated: Cause: BYE from PBX
    25-01-2013 09:35:25.169   Leg L:76.2[Extn] is terminated: Cause: 480 Temporarily not available/INVITE from 192.168.1.200:5060
    25-01-2013 09:35:25.169   [CM503020]: Call(C:76): Normal call termination. Call originator: Queue:251. Reason: Not available
    25-01-2013 09:35:25.169   Call to T:Extn:604@[Dev:sip:604@192.168.1.200:5060] from L:76.1[Queue] failed, cause: Cause: 480 Temporarily not available/INVITE from 192.168.1.200:5060
    25-01-2013 09:35:25.169   [CM503003]: Call(C:76): Call to <sip:604@192.168.1.3:5060> has failed; Cause: 480 Temporarily not available/INVITE from 192.168.1.200:5060
    25-01-2013 09:35:23.734   [CM503022]: Call(C:71): Call recording is started, audio file: C:\ProgramData\3CX\Data\Recordings\602\[Priv%C3%A9%3A3227588780]_3227588780-602_20130125093523(71).wav
    25-01-2013 09:35:23.732   Leg L:71.3[Queue] is terminated: Cause: BYE from 127.0.0.1:5488
    25-01-2013 09:35:23.526   [CM503007]: Call(C:71): Extn:602 has joined, contact <sip:602@192.168.1.200:5060>
    25-01-2013 09:35:23.525   L:71.4[Extn] has joined to L:71.1[Line:10000<<3227588780]
    25-01-2013 09:35:23.496   Leg L:73.1[Queue] is terminated: Cause: BYE from PBX
    25-01-2013 09:35:23.496   [CM503008]: Call(C:73): Call is terminated
    25-01-2013 09:35:23.495   Leg L:73.2[Extn] is terminated: Cause: BYE from 192.168.1.200:5060
    25-01-2013 09:35:20.666   Leg L:74.2[Extn] is terminated: Cause: 487 Request Cancelled/INVITE from 192.168.1.200:5060
    25-01-2013 09:35:20.666   [CM503003]: Call(C:74): Call to <sip:601@192.168.1.3:5060> has failed; Cause: 487 Request Cancelled/INVITE from 192.168.1.200:5060
    25-01-2013 09:35:20.567   Leg L:72.2[Extn] is terminated: Cause: 487 Request Cancelled/INVITE from 192.168.1.200:5060
    25-01-2013 09:35:20.567   [CM503003]: Call(C:72): Call to <sip:603@192.168.1.3:5060> has failed; Cause: 487 Request Cancelled/INVITE from 192.168.1.200:5060
    25-01-2013 09:35:20.080   [CM503025]: Call(C:71): Calling T:Extn:602@[Dev:sip:602@192.168.1.200:5060] for L:71.1[Line:10000<<3227588780]
    25-01-2013 09:35:20.077   [CM505003]: Provider:[Localphone (+3238081155)] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Vox Callcontrol] PBX contact: [sip:6364612@83.197.35.72:5060]
    25-01-2013 09:35:20.077   [CM503008]: Call(C:74): Call is terminated
    25-01-2013 09:35:20.076   Leg L:74.1[Queue] is terminated: Cause: CANCEL from 127.0.0.1:5488
    25-01-2013 09:35:20.076   [CM503008]: Call(C:72): Call is terminated
    25-01-2013 09:35:20.075   Leg L:72.1[Queue] is terminated: Cause: CANCEL from 127.0.0.1:5488
    25-01-2013 09:35:19.872   [CM503007]: Call(C:73): Extn:602 has joined, contact <sip:602@192.168.1.200:5060>
    25-01-2013 09:35:19.872   [CM503007]: Call(C:73): Queue:251 has joined, contact <sip:251@127.0.0.1:5488>
    25-01-2013 09:35:19.871   L:73.2[Extn] has joined to L:73.1[Queue]
    25-01-2013 09:35:16.721   [CM503025]: Call(C:76): Calling T:Extn:604@[Dev:sip:604@192.168.1.200:5060] for L:76.1[Queue]
    25-01-2013 09:35:16.672   [CM503027]: Call(C:76): From: Queue:251 ("Prive lijn:Privé:3227588780" <sip:3227588780@127.0.0.1:5060>)  to  T:Extn:604@[Dev:sip:604@192.168.1.200:5060]
    25-01-2013 09:35:16.672   [CM503004]: Call(C:76): Route 1: from L:76.1[Queue] to T:Extn:604@[Dev:sip:604@192.168.1.200:5060]
    25-01-2013 09:35:16.671   [CM503001]: Call(C:76): Incoming call from Queue:251 to <sip:604@127.0.0.1:5060>
    25-01-2013 09:35:15.166   Leg L:75.1[Queue] is terminated: Cause: BYE from PBX
    25-01-2013 09:35:15.166   Leg L:75.2[Extn] is terminated: Cause: 480 Temporarily not available/INVITE from 192.168.1.200:5060
    25-01-2013 09:35:15.165   [CM503020]: Call(C:75): Normal call termination. Call originator: Queue:251. Reason: Not available
    25-01-2013 09:35:15.165   Call to T:Extn:604@[Dev:sip:604@192.168.1.200:5060] from L:75.1[Queue] failed, cause: Cause: 480 Temporarily not available/INVITE from 192.168.1.200:5060
    25-01-2013 09:35:15.165   [CM503003]: Call(C:75): Call to <sip:604@192.168.1.3:5060> has failed; Cause: 480 Temporarily not available/INVITE from 192.168.1.200:5060
    25-01-2013 09:35:07.236   Currently active calls - 1: [71]
    25-01-2013 09:35:06.671   [CM503025]: Call(C:75): Calling T:Extn:604@[Dev:sip:604@192.168.1.200:5060] for L:75.1[Queue]
    25-01-2013 09:35:06.669   [CM503025]: Call(C:74): Calling T:Extn:601@[Dev:sip:601@192.168.1.200:5060] for L:74.1[Queue]
    25-01-2013 09:35:06.666   [CM503025]: Call(C:73): Calling T:Extn:602@[Dev:sip:602@192.168.1.200:5060] for L:73.1[Queue]
    25-01-2013 09:35:06.663   [CM503025]: Call(C:72): Calling T:Extn:603@[Dev:sip:603@192.168.1.200:5060] for L:72.1[Queue]
    25-01-2013 09:35:06.624   [CM503027]: Call(C:75): From: Queue:251 ("Prive lijn:Privé:3227588780" <sip:3227588780@127.0.0.1:5060>)  to  T:Extn:604@[Dev:sip:604@192.168.1.200:5060]
    25-01-2013 09:35:06.624   [CM503004]: Call(C:75): Route 1: from L:75.1[Queue] to T:Extn:604@[Dev:sip:604@192.168.1.200:5060]
    25-01-2013 09:35:06.624   [CM503027]: Call(C:74): From: Queue:251 ("Prive lijn:Privé:3227588780" <sip:3227588780@127.0.0.1:5060>)  to  T:Extn:601@[Dev:sip:601@192.168.1.200:5060]
    25-01-2013 09:35:06.624   [CM503004]: Call(C:74): Route 1: from L:74.1[Queue] to T:Extn:601@[Dev:sip:601@192.168.1.200:5060]
    25-01-2013 09:35:06.624   [CM503027]: Call(C:73): From: Queue:251 ("Prive lijn:Privé:3227588780" <sip:3227588780@127.0.0.1:5060>)  to  T:Extn:602@[Dev:sip:602@192.168.1.200:5060]
    25-01-2013 09:35:06.624   [CM503004]: Call(C:73): Route 1: from L:73.1[Queue] to T:Extn:602@[Dev:sip:602@192.168.1.200:5060]
    25-01-2013 09:35:06.623   [CM503027]: Call(C:72): From: Queue:251 ("Prive lijn:Privé:3227588780" <sip:3227588780@127.0.0.1:5060>)  to  T:Extn:603@[Dev:sip:603@192.168.1.200:5060]
    25-01-2013 09:35:06.623   [CM503004]: Call(C:72): Route 1: from L:72.1[Queue] to T:Extn:603@[Dev:sip:603@192.168.1.200:5060]
    25-01-2013 09:35:06.622   [CM503001]: Call(C:75): Incoming call from Queue:251 to <sip:604@127.0.0.1:5060>
    25-01-2013 09:35:06.619   [CM503001]: Call(C:74): Incoming call from Queue:251 to <sip:601@127.0.0.1:5060>
    25-01-2013 09:35:06.615   [CM503001]: Call(C:73): Incoming call from Queue:251 to <sip:602@127.0.0.1:5060>
    25-01-2013 09:35:06.611   [CM503001]: Call(C:72): Incoming call from Queue:251 to <sip:603@127.0.0.1:5060>
    25-01-2013 09:35:06.293   Leg L:71.2[Ivr] is terminated: Cause: BYE from 127.0.0.1:40600
    25-01-2013 09:35:06.087   [CM503007]: Call(C:71): Queue:251 has joined, contact <sip:251@127.0.0.1:5488>
    25-01-2013 09:35:06.085   L:71.3[Queue] has joined to L:71.1[Line:10000<<3227588780]
    25-01-2013 09:35:05.933   [CM503025]: Call(C:71): Calling T:Queue:251@[Dev:sip:251@127.0.0.1:5488] for L:71.1[Line:10000<<3227588780]
    25-01-2013 09:35:05.881   [CM503027]: Call(C:71): From: Line:10000<<3227588780 ("Privé:3227588780" <sip:3227588780@192.168.1.3:5060>)  to  T:Queue:251@[Dev:sip:251@127.0.0.1:5488]
    25-01-2013 09:35:05.881   [CM503004]: Call(C:71): Route 1: from L:71.1[Line:10000<<3227588780] to T:Queue:251@[Dev:sip:251@127.0.0.1:5488]
    25-01-2013 09:35:05.881   [CM505003]: Provider:[Localphone (+3238081155)] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Vox Callcontrol] PBX contact: [sip:6364612@83.197.35.72:5060]
    25-01-2013 09:34:53.173   [CM503007]: Call(C:71): Ivr:300 has joined, contact <sip:300@127.0.0.1:40600>
    25-01-2013 09:34:53.173   [CM503007]: Call(C:71): Line:10000<<3227588780 has joined, contact <sip:6364612@localphone.com:5060>
    25-01-2013 09:34:53.172   L:71.2[Ivr] has joined to L:71.1[Line:10000<<3227588780]
    25-01-2013 09:34:53.018   [CM503025]: Call(C:71): Calling T:Ivr:300@[Dev:sip:300@127.0.0.1:40600;rinstance=b7444e79b0e26ca9] for L:71.1[Line:10000<<3227588780]
    25-01-2013 09:34:53.013   [CM503027]: Call(C:71): From: Line:10000<<3227588780 ("Privé:3227588780" <sip:3227588780@192.168.1.3:5060>)  to  T:Ivr:300@[Dev:sip:300@127.0.0.1:40600;rinstance=b7444e79b0e26ca9]
    25-01-2013 09:34:53.013   [CM503004]: Call(C:71): Route 1: from L:71.1[Line:10000<<3227588780] to T:Ivr:300@[Dev:sip:300@127.0.0.1:40600;rinstance=b7444e79b0e26ca9]
    25-01-2013 09:34:53.013   [CM505003]: Provider:[Localphone (+3238081155)] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Vox Callcontrol] PBX contact: [sip:6364612@83.197.35.72:5060]
    25-01-2013 09:34:53.012   [CM503001]: Call(C:71): Incoming call from Line:10000<<3227588780 to <sip:300@192.168.1.3:5060>
    25-01-2013 09:34:53.012   Line limit check: Current # of calls for line Lc:10000(@Localphone (+3238081155)[<sip:6364612@localphone.com:5060>]) is 1; limit is 4
    25-01-2013 09:34:52.867   [CM503012]: Inbound any hours rule (Privé) for 10000 forwards to DN:300
    The inbound call route is like this: Inbound call -> ext 300 (IVR) -> ext 251 (call queue)

    Anyone an idea if I can fix this 'lag'. During conversation, there isn't any problem. It's just the 2-3 seconds of silence that bothers me.

    Thanks!
     
  2. 3CXfoxhallsolutions

    3CXfoxhallsolutions New Member

    Joined:
    Sep 8, 2012
    Messages:
    211
    Likes Received:
    0
    Hi
    I'm assuming you have SIP Trunks - yes??
    I've sometimes found that slow-connect issues are to do with DNS settings on my 3CX servers.
    Check to see if you have any issues opening a web-page on the 3CX server machine ... If you see a delay in opening the web-page, this can indicate that you have DNS resolution issues. To overcome this, set the NIC of the 3CX server with a static IP address and the DNS servers of the ISP you are using ... Usually it's best to have the 3CX set up to use the public IP address of the Internet service carrying the SIP Trunk group - in the Network settings, and in the Registration settings of the SIP Trunk group. But if the problem persists, and you already have that set ... Then try using STUN to get the proper location info in the registration header ...

    In a nutshell - When I've seen this problem, it's because the call doesn't quite know where to find the target extension.

    I hope that's helpful ....
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. 3cxBora

    Joined:
    Jun 17, 2015
    Messages:
    38
    Likes Received:
    0
    Hi, we are having random silence inbound call too on 3cx v14 hosted on remote extension.

    The remote extension on Yealink phones are using STUN and is behind SonicWALL firewall. We have disabled ALG, but we don't have confirmation the configuration and setup is correct since 3cx support does not validate the setup on firewall.

    Have anyone been in similar setup and have a config or more details to resolve this issue?

    Thanks,
    Bora
     
  4. NickD_3CX

    NickD_3CX Support Team
    Staff Member 3CX Support

    Joined:
    Jun 2, 2014
    Messages:
    1,379
    Likes Received:
    84
    When calls go to an extension though a Queue, when the Queue agent answers there is a very slight delay as the Queue performs what is called a Re-Invite, but usually the delay is ~1.5 seconds.
     
  5. johandezwaan

    Joined:
    Nov 13, 2013
    Messages:
    14
    Likes Received:
    0
    Hello NickD_3CX,

    Is it possible to speed this up in the future? our users are experiencing a lot of frustrations because of this.

    regards,
    Johan de Zwaan.
     
  6. NickD_3CX

    NickD_3CX Support Team
    Staff Member 3CX Support

    Joined:
    Jun 2, 2014
    Messages:
    1,379
    Likes Received:
    84
    This was mainly due to a delay from the phones/endpoints. In the latest firmware versions this has been improved somewhat from some preliminary tests I have done, e.g. for Yealink phones running a v80 firmware on my PBX it is now ~0.9 seconds delay and on a snom running 8.7.5.35 it is now ~0.7 seconds. I haven't had a chance to check other makes as well, this is just what I had available at the time.
     
Thread Status:
Not open for further replies.