Incoming calls take a long time to reach the auto attendant

Discussion in '3CX Phone System - General' started by Don_Zalmrol, May 30, 2012.

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

    Joined:
    Apr 25, 2012
    Messages:
    45
    Likes Received:
    0
    As the title says, again we are experiencing problems with our 3CX Phone System.

    Outgoing calls no problems…
    Incoming calls take a very long time to receive the auto attendant message & DTMF options.

    When I look at the incoming calls, they are guided properly towards the auto attendant. Yet it takes a very long time before the prompt starts to play…

    The firewall is properly configured and following ports are opened for 3CX:

    5060, 5061, 5090, 9000-9063, 10000

    Here is the log of my 3CX server:
    Code:
    15:53:14.245  [CM503025]: Call(143): Calling PSTNline:0486858660@(Ln.10002@Simbox)@[Dev:sip:10002@10.0.0.10:5060]
    15:53:14.237  [CM503005]: Call(143): Forwarding: VoIPline:0486858660@(Ln.10001@WeePee Backup)@[Dev:sip:329919013472@ssw3.bruges.weepee.org:5060]
    15:53:14.237  [CM503005]: Call(143): Forwarding: VoIPline:0486858660@(Ln.10000@WeePee)@[Dev:sip:329909013472@ssw2.brussels.weepee.org:5060]
    15:53:14.236  [CM503005]: Call(143): Forwarding: PSTNline:0486858660@(Ln.10002@Simbox)@[Dev:sip:10002@10.0.0.10:5060]
    15:53:14.235  [CM503016]: Call(143): Attempt to reach <sip:800@127.0.0.1:5060> failed. Reason: Temporarily Unavailable
    15:53:14.235  [CM503026]: Call(143): Target is not available: RingAll800[]
    15:53:14.234  [CM503010]: Making route(s) to <sip:800@127.0.0.1:5060>
    15:53:14.203  [CM503025]: Call(144): Calling RingAll700[Ext.200,Ext.201,Ext.202,Ext.203,Ext.204,Ext.205,Ext.210]@[Dev:sip:210@10.0.0.11:5066]
    15:53:14.200  [CM503025]: Call(144): Calling RingAll700[Ext.200,Ext.201,Ext.202,Ext.203,Ext.204,Ext.205,Ext.210]@[Dev:sip:205@10.0.0.12:5060]
    15:53:14.197  [CM503025]: Call(144): Calling RingAll700[Ext.200,Ext.201,Ext.202,Ext.203,Ext.204,Ext.205,Ext.210]@[Dev:sip:205@10.0.0.29:5065;ob]
    15:53:14.194  [CM503025]: Call(144): Calling RingAll700[Ext.200,Ext.201,Ext.202,Ext.203,Ext.204,Ext.205,Ext.210]@[Dev:sip:204@10.0.0.12:5060]
    15:53:14.191  [CM503025]: Call(144): Calling RingAll700[Ext.200,Ext.201,Ext.202,Ext.203,Ext.204,Ext.205,Ext.210]@[Dev:sip:203@10.0.0.12:5060]
    15:53:14.188  [CM503025]: Call(144): Calling RingAll700[Ext.200,Ext.201,Ext.202,Ext.203,Ext.204,Ext.205,Ext.210]@[Dev:sip:202@10.0.0.12:5060]
    15:53:14.185  [CM503025]: Call(144): Calling RingAll700[Ext.200,Ext.201,Ext.202,Ext.203,Ext.204,Ext.205,Ext.210]@[Dev:sip:201@10.0.0.17:5062]
    15:53:14.182  [CM503025]: Call(144): Calling RingAll700[Ext.200,Ext.201,Ext.202,Ext.203,Ext.204,Ext.205,Ext.210]@[Dev:sip:200@10.0.0.16:5062]
    15:53:14.135  [CM503004]: Call(144): Route 1: RingAll700[Ext.200,Ext.201,Ext.202,Ext.203,Ext.204,Ext.205,Ext.210]@[Dev:sip:200@10.0.0.16:5062,Dev:sip:201@10.0.0.17:5062,Dev:sip:202@10.0.0.12:5060,Dev:sip:203@10.0.0.12:5060,Dev:sip:204@10.0.0.12:5060,Dev:sip:205@10.0.0.29:5065;ob,Dev:sip:205@10.0.0.12:5060,Dev:sip:210@10.0.0.11:5066]
    15:53:14.133  [CM503010]: Making route(s) to <sip:700@10.0.0.2>
    15:53:14.133  [CM505001]: Ext.208: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [Grandstream GXW-4004  V1.5A 1.0.3.10] PBX contact: [sip:208@10.0.0.2:5060]
    15:53:14.132  [CM503001]: Call(144): Incoming call from Ext.208 to <sip:700@10.0.0.2>
    15:53:12.208  [MS205001] C:143.1 RTCP: Party address changed from 91.213.251.133:11485 to 91.208.12.132:14551
    15:53:11.768  [MS205001] C:143.1 RTCP: Party address changed from 91.208.12.132:14551 to 91.213.251.133:11485
    15:53:10.531  [MS211000] C:143.1: 91.213.251.133:11484 is delivering DTMF using RTP payload (RFC2833). In-Band DTMF tone detection is disabled for this call segment.
    15:53:07.208  [MS205001] C:143.1 RTCP: Party address changed from 91.213.251.133:11485 to 91.208.12.132:14551
    15:53:06.769  [MS205001] C:143.1 RTCP: Party address changed from 91.208.12.132:14551 to 91.213.251.133:11485
    15:53:02.208  [MS205001] C:143.1 RTCP: Party address changed from 91.213.251.133:11485 to 91.208.12.132:14551
    15:53:01.290  [CM503007]: Call(143): Device joined: sip:802@127.0.0.1:40600;rinstance=cfd1e65c614fde4d
    15:53:01.290  [CM503007]: Call(143): Device joined: sip:329909013472@ssw2.brussels.weepee.org:5060
    15:53:01.286  [CM505001]: Ext.802: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX IVR;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVR] PBX contact: [sip:802@127.0.0.1:5060]
    15:53:01.286  [CM503002]: Call(143): Alerting sip:802@127.0.0.1:40600;rinstance=cfd1e65c614fde4d
    15:53:01.137  [CM503025]: Call(143): Calling Ext:Ext.802@[Dev:sip:802@127.0.0.1:40600;rinstance=cfd1e65c614fde4d]
    15:53:01.093  [CM503004]: Call(143): Route 1: Ext:Ext.802@[Dev:sip:802@127.0.0.1:40600;rinstance=cfd1e65c614fde4d]
    15:53:01.092  [CM503010]: Making route(s) to <sip:802@10.0.0.2:5060>
    15:53:01.092  [CM505003]: Provider:[WeePee] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [weepee] PBX contact: [sip:329909013472@81.83.22.28:5060]
    15:53:01.091  [CM503001]: Call(143): Incoming call from 0473210087@(Ln.10000@WeePee) to <sip:802@10.0.0.2:5060>
    15:53:01.086  [CM503012]: Inbound office hours rule (Klanten) for 10000 forwards to DN:802
    15:53:00.251  [CM503008]: Call(142): Call is terminated
    15:53:00.250  [CM503021]: Call(142): ACK is not received
    15:52:55.953  Currently active calls - 1: [142]
    15:52:28.161  [CM503007]: Call(142): Device joined: sip:802@127.0.0.1:40600;rinstance=cfd1e65c614fde4d
    15:52:28.160  [CM503007]: Call(142): Device joined: sip:329909013472@ssw2.brussels.weepee.org:5060
    15:52:28.157  [CM505001]: Ext.802: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX IVR;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVR] PBX contact: [sip:802@127.0.0.1:5060]
    15:52:28.157  [CM503002]: Call(142): Alerting sip:802@127.0.0.1:40600;rinstance=cfd1e65c614fde4d
    15:52:28.008  [CM503025]: Call(142): Calling Ext:Ext.802@[Dev:sip:802@127.0.0.1:40600;rinstance=cfd1e65c614fde4d]
    15:52:27.964  [CM503004]: Call(142): Route 1: Ext:Ext.802@[Dev:sip:802@127.0.0.1:40600;rinstance=cfd1e65c614fde4d]
    15:52:27.964  [CM503010]: Making route(s) to <sip:802@10.0.0.2:5060>
    15:52:27.963  [CM505003]: Provider:[WeePee] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [weepee] PBX contact: [sip:329909013472@81.83.22.28:5060]
    15:52:27.962  [CM503001]: Call(142): Incoming call from 0473210087@(Ln.10000@WeePee) to <sip:802@10.0.0.2:5060>
    15:52:27.956  [CM503012]: Inbound office hours rule (Klanten) for 10000 forwards to DN:802
    
    Then it gets weirder, the auto attendant for our business is having that problem and the other one for our private home lines is being dropped…

    Code:
    16:08:13.477  [MS105000] C:146.1: No RTP packets were received:remoteAddr=91.208.12.132:27424,extAddr=0.0.0.0:0,localAddr=81.83.22.28:9012
    16:08:12.490  [CM503008]: Call(146): Call is terminated
    16:08:12.489  [CM503021]: Call(146): ACK is not received
    16:08:10.029  Currently active calls - 1: [146]
    16:07:40.416  [CM503007]: Call(146): Device joined: sip:803@127.0.0.1:40600;rinstance=173f35c29b8e1170
    16:07:40.415  [CM503007]: Call(146): Device joined: sip:329909013472@ssw2.brussels.weepee.org:5060
    16:07:40.412  [CM505001]: Ext.803: Device info: Device Identified: [Man: 3CX Ltd.;Mod: 3CX IVR;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX IVR] PBX contact: [sip:803@127.0.0.1:5060]
    16:07:40.412  [CM503002]: Call(146): Alerting sip:803@127.0.0.1:40600;rinstance=173f35c29b8e1170
    16:07:40.262  [CM503025]: Call(146): Calling Ext:Ext.803@[Dev:sip:803@127.0.0.1:40600;rinstance=173f35c29b8e1170]
    16:07:40.219  [CM503004]: Call(146): Route 1: Ext:Ext.803@[Dev:sip:803@127.0.0.1:40600;rinstance=173f35c29b8e1170]
    16:07:40.218  [CM503010]: Making route(s) to <sip:803@10.0.0.2:5060>
    16:07:40.218  [CM505003]: Provider:[WeePee] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [weepee] PBX contact: [sip:329909013472@81.83.22.28:5060]
    16:07:40.216  [CM503001]: Call(146): Incoming call from 0473210087@(Ln.10000@WeePee) to <sip:803@10.0.0.2:5060>
    16:07:40.211  [CM503012]: Inbound any hours rule (Prive) for 10000 forwards to DN:803
    16:03:26.053  [MS105000] C:145.1: No RTP packets were received:remoteAddr=91.208.12.132:25276,extAddr=0.0.0.0:0,localAddr=81.83.22.28:9008
    16:03:24.359  [CM503008]: Call(145): Call is terminated
    16:03:24.358  [CM503021]: Call(145): ACK is not received
    
    I'm starting to think there is a problem with our network card, yet this card is replaced by a new one…
    I'm thinking this, because we had a similar problem, but the callers never received any of the auto attendants on any line at all…

    Thank you for your help in advance!

    Cheers,

    Laurens
     
  2. Don_Zalmrol

    Joined:
    Apr 25, 2012
    Messages:
    45
    Likes Received:
    0
    Re: Incoming calls take a long time to reach the auto attend

    I've tested my system with our simbox, and there the problem doesn't exists…

    The problem is between our server and voip provider (weepee).

    Our network is as follows:

    WAN (Telenet) -> Router (DSR-1000N) -> Switch (DGS-1500-28) -> Server (HP Pro Liant 350)
    81.82.x.x 10.0.0.1 10.0.0.3 10.0.0.2
     
  3. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,878
    Likes Received:
    307
    Re: Incoming calls take a long time to reach the auto attend

    It would appear that some SIP messages are not able to get through your Router/Firewall/Network.
     
  4. Don_Zalmrol

    Joined:
    Apr 25, 2012
    Messages:
    45
    Likes Received:
    0
    Re: Incoming calls take a long time to reach the auto attend

    Apparently SIP calls from the WAN side to the LAN side fails or "hangs" in de auto attendant "queue" when you enable traffic management on your router…

    Problem solved :D
     
Thread Status:
Not open for further replies.