Call dropping after 30 seconds, Ack not received

Discussion in '3CX Phone System - General' started by sunstate, Dec 1, 2010.

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

    sunstate Member

    Joined:
    Dec 16, 2009
    Messages:
    257
    Likes Received:
    0
    I am using a VoIP provider called CallWithUs at a client to do some testing. We use this same account on our 3CX system with no issues, but at the client site (3CX v9 fully patched) after 30 seconds calls via the VoIP provider are dropping with the famous "Ack is not received" error. I have tried with Stun on and off in Settings > Network and tried with Stun and manually specifying the public IP in the VoIP provider settings directly. Same result. I don't have access to the firewall, but I know that it is a Linksys. I will need to contact their IT guy to get more information on the firewall. Here is the log. Any ideas?

    Code:
    13:34:49.671  [CM503008]: Call(1): Call is terminated
    13:34:49.671  [CM503021]: Call(1): ACK is not received
    13:34:40.312  Currently active calls - 1: [1]
    13:34:21.468  [MS211000] C:1.1: 127.0.0.1:10002 is delivering DTMF using RTP payload (RFC2833). In-Band DTMF tone detection is disabled for this call segment.
    13:34:17.609  [CM503007]: Call(1): Device joined: sip:245900132@sip.callwithus.com:5060
    13:34:17.609  [CM503007]: Call(1): Device joined: sip:1000@172.24.32.195:5061;user=phone;transport=udp
    13:34:15.296  [CM505003]: Provider:[CallWithUs] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:245900132@70.166.105.77:5060]
    13:34:15.296  [CM503002]: Call(1): Alerting sip:245900132@sip.callwithus.com:5060
    13:34:14.234  [CM503025]: Call(1): Calling VoIPline:16023143333@(Ln.10001@CallWithUs)@[Dev:sip:245900132@sip.callwithus.com:5060]
    13:34:14.203  [CM503004]: Call(1): Route 1: VoIPline:16023143333@(Ln.10001@CallWithUs)@[Dev:sip:245900132@sip.callwithus.com:5060]
    13:34:14.187  [CM503010]: Making route(s) to <sip:6023143333@192.168.0.6>
    13:34:14.187  [CM505001]: Ext.1000: Device info: Device Identified: [Man: Cisco;Mod: 7940;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [Cisco-CP7940G/8.0] PBX contact: [sip:1000@127.0.0.1:5060]
    13:34:14.187  [CM503001]: Call(1): Incoming call from Ext.1000 to <sip:6023143333@192.168.0.6>
    13:33:48.421  [CM504001]: Ext.IVRForward: new contact is registered. Contact(s): [sip:IVRForward@127.0.0.1:40600;rinstance=16fdaa71d205fde0/IVRForward]
    13:33:48.421  [CM504001]: Ext.EndCall: new contact is registered. Contact(s): [sip:EndCall@127.0.0.1:40600;rinstance=fed54938a51d9e4a/EndCall]
    13:33:48.406  [CM504001]: Ext.8000: new contact is registered. Contact(s): [sip:8000@127.0.0.1:40600;rinstance=c2757f25d9a3240c/8000]
    13:33:48.312  [CM504001]: Ext.9999: new contact is registered. Contact(s): [sip:9999@127.0.0.1:40600;rinstance=253e266106a99545/9999]
    13:33:46.625  [CM504004]: Registration succeeded for: 10001@CallWithUs
    13:33:46.578  [CM504001]: Ext.1000: new contact is registered. Contact(s): [sip:1000@172.24.32.195:5061;user=phone;transport=udp/1000]
    13:33:46.468  [CM504003]: Sent registration request for 10000@TruCom
    13:33:46.421  [CM504003]: Sent registration request for 10001@CallWithUs
    13:33:46.328  IP(s) added:[192.168.0.6,192.168.209.1,192.168.30.1]
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. mfm

    mfm Active Member

    Joined:
    Mar 4, 2010
    Messages:
    641
    Likes Received:
    2
    Hi,

    Without access to the firewall your not going to get very far. The port forwarding has to be done to obtain the full functionality on this device.

    Please run the firewall checker and paste the output in code and /code tags/
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. hornetsoft

    Joined:
    Nov 6, 2009
    Messages:
    10
    Likes Received:
    0
    If your router supports sip alg switch it off its worked for me on several routers
     
  4. hornetsoft

    Joined:
    Nov 6, 2009
    Messages:
    10
    Likes Received:
    0
    Not sure what model you use of linksys but found this below

    To disable SIP ALG on WRT610N: Web Interface: Administration, Management, under side heading 'Advanced Features' SIP ALG, can be disabled.
     
  5. sunstate

    sunstate Member

    Joined:
    Dec 16, 2009
    Messages:
    257
    Likes Received:
    0
    I am waiting to hear back from their IT guy, hopefully he'll just give me access to it directly. For some reason I'm remember him saying it was an older Linksys, so I don't think it's got the ALG, but if it does I'll definitely be turning it off. In the meantime here is the firewall checker log:

    Code:
    3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved.
    
    <17:02:10>: Phase 1, checking servers connection, please wait...
    <17:02:10>: Stun Checker service is reachable. Phase 1 check passed.
    <17:02:10>: Phase 2a,  Check Port Forwarding to UDP SIP port, please wait...
    <17:02:50>: UDP SIP Port is set to 5060. Response received correctly with no translation. Phase 2a check passed.
    
    <17:02:50>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
    <17:02:50>: TCP SIP Port is set to 5060. Response received correctly with no translation. Phase 2b check passed.
    
    <17:02:50>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
    <17:02:50>: TCP TUNNEL Port is set to 5090. Response received correctly with no translation. Phase 3 check passed.
    
    <17:02:50>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
    <17:02:55>: UDP RTP Port 9000. Response received correctly with no translation. Phase 4-01 check passed.
    <17:02:55>: UDP RTP Port 9001. Response received correctly with no translation. Phase 4-02 check passed.
    <17:02:55>: UDP RTP Port 9002. Response received correctly with no translation. Phase 4-03 check passed.
    <17:02:56>: UDP RTP Port 9003. Response received correctly with no translation. Phase 4-04 check passed.
    <17:02:56>: UDP RTP Port 9004. Response received correctly with no translation. Phase 4-05 check passed.
    <17:02:56>: UDP RTP Port 9005. Response received correctly with no translation. Phase 4-06 check passed.
    <17:02:56>: UDP RTP Port 9006. Response received correctly with no translation. Phase 4-07 check passed.
    <17:02:56>: UDP RTP Port 9007. Response received correctly with no translation. Phase 4-08 check passed.
    <17:02:56>: UDP RTP Port 9008. Response received correctly with no translation. Phase 4-09 check passed.
    <17:02:56>: UDP RTP Port 9009. Response received correctly with no translation. Phase 4-10 check passed.
    <17:02:56>: UDP RTP Port 9010. Response received correctly with no translation. Phase 4-11 check passed.
    <17:02:56>: UDP RTP Port 9011. Response received correctly with no translation. Phase 4-12 check passed.
    <17:02:56>: UDP RTP Port 9012. Response received correctly with no translation. Phase 4-13 check passed.
    <17:02:56>: UDP RTP Port 9013. Response received correctly with no translation. Phase 4-14 check passed.
    <17:02:56>: UDP RTP Port 9014. Response received correctly with no translation. Phase 4-15 check passed.
    <17:02:56>: UDP RTP Port 9015. Response received correctly with no translation. Phase 4-16 check passed.
    <17:02:56>: UDP RTP Port 9016. Response received correctly with no translation. Phase 4-17 check passed.
    <17:02:56>: UDP RTP Port 9017. Response received correctly with no translation. Phase 4-18 check passed.
    <17:02:56>: UDP RTP Port 9018. Response received correctly with no translation. Phase 4-19 check passed.
    <17:02:56>: UDP RTP Port 9019. Response received correctly with no translation. Phase 4-20 check passed.
    <17:02:56>: UDP RTP Port 9020. Response received correctly with no translation. Phase 4-21 check passed.
    <17:02:56>: UDP RTP Port 9021. Response received correctly with no translation. Phase 4-22 check passed.
    <17:02:56>: UDP RTP Port 9022. Response received correctly with no translation. Phase 4-23 check passed.
    <17:02:56>: UDP RTP Port 9023. Response received correctly with no translation. Phase 4-24 check passed.
    <17:02:56>: UDP RTP Port 9024. Response received correctly with no translation. Phase 4-25 check passed.
    <17:02:56>: UDP RTP Port 9025. Response received correctly with no translation. Phase 4-26 check passed.
    <17:02:56>: UDP RTP Port 9026. Response received correctly with no translation. Phase 4-27 check passed.
    <17:02:56>: UDP RTP Port 9027. Response received correctly with no translation. Phase 4-28 check passed.
    <17:02:56>: UDP RTP Port 9028. Response received correctly with no translation. Phase 4-29 check passed.
    <17:02:56>: UDP RTP Port 9029. Response received correctly with no translation. Phase 4-30 check passed.
    <17:02:56>: UDP RTP Port 9030. Response received correctly with no translation. Phase 4-31 check passed.
    <17:02:56>: UDP RTP Port 9031. Response received correctly with no translation. Phase 4-32 check passed.
    <17:02:56>: UDP RTP Port 9032. Response received correctly with no translation. Phase 4-33 check passed.
    <17:02:56>: UDP RTP Port 9033. Response received correctly with no translation. Phase 4-34 check passed.
    <17:02:56>: UDP RTP Port 9034. Response received correctly with no translation. Phase 4-35 check passed.
    <17:02:56>: UDP RTP Port 9035. Response received correctly with no translation. Phase 4-36 check passed.
    <17:02:56>: UDP RTP Port 9036. Response received correctly with no translation. Phase 4-37 check passed.
    <17:02:56>: UDP RTP Port 9037. Response received correctly with no translation. Phase 4-38 check passed.
    <17:02:56>: UDP RTP Port 9038. Response received correctly with no translation. Phase 4-39 check passed.
    <17:02:56>: UDP RTP Port 9039. Response received correctly with no translation. Phase 4-40 check passed.
    <17:02:56>: UDP RTP Port 9040. Response received correctly with no translation. Phase 4-41 check passed.
    <17:02:56>: UDP RTP Port 9041. Response received correctly with no translation. Phase 4-42 check passed.
    <17:02:56>: UDP RTP Port 9042. Response received correctly with no translation. Phase 4-43 check passed.
    <17:02:56>: UDP RTP Port 9043. Response received correctly with no translation. Phase 4-44 check passed.
    <17:02:56>: UDP RTP Port 9044. Response received correctly with no translation. Phase 4-45 check passed.
    <17:02:56>: UDP RTP Port 9045. Response received correctly with no translation. Phase 4-46 check passed.
    <17:02:56>: UDP RTP Port 9046. Response received correctly with no translation. Phase 4-47 check passed.
    <17:02:56>: UDP RTP Port 9047. Response received correctly with no translation. Phase 4-48 check passed.
    <17:02:56>: UDP RTP Port 9048. Response received correctly with no translation. Phase 4-49 check passed.
    <17:02:56>: UDP RTP Port 9049. Response received correctly with no translation. Phase 4-50 check passed.
    
    
    Application exit code is 0
    
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. mfm

    mfm Active Member

    Joined:
    Mar 4, 2010
    Messages:
    641
    Likes Received:
    2
    Hi,

    everything seems to be passing,

    Could you set the PBX in static ip mode and then follow by doing it in the voip provider as I believe you allready have. Ack not recieved is an issue when the remote party either does not send ack, or there is something blocking it (maybe sip ALG as previously mentioned ). Have a look at try from there.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. happy1

    Joined:
    Aug 2, 2010
    Messages:
    1
    Likes Received:
    0
    I have not had good luck with linksys routers with 3cx or any voip.

    The best router is the edgemarc.

    :mrgreen:
     
Thread Status:
Not open for further replies.