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.

Call drops after 20-30 seconds remote to remote call

Discussion in '3CX Phone System - General' started by malimar, Jan 23, 2011.

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

    Joined:
    Oct 26, 2010
    Messages:
    10
    Likes Received:
    0
    Hi, we are testing a remote phone calling to another remote location running Andriod through a bridge. After 20-30 seconds the calls disconnects.

    Diagram of the call.
    Polycom 550 Phone remote (ext 111) -> 3CX system -> Bridge -> 3CX System -> Andriod remote ext 222

    Bridge = 1000

    Here's what it shows on the log on Polycom side of 3CX:

    20:07:53.708 [CM503008]: Call(122): Call is terminated
    20:07:53.708 [CM503021]: Call(122): ACK is not received
    20:07:32.850 [CM503008]: Call(121): Call is terminated
    20:07:32.850 [CM503021]: Call(121): ACK is not received
    20:07:25.097 Currently active calls - 2: [121,122]
    20:07:21.587 [CM503007]: Call(122): Device joined: sip:1000@192.168.10.15:5060
    20:07:21.587 [CM503007]: Call(122): Device joined: sip:111@68.111.254.169:5060
    20:07:21.587 [MS210003] C:122.1:Answer provided. Connection(transcoding mode[unsecure]):98.175.250.85:9014(9015)
    20:07:21.587 [MS210001] C:122.2:Answer received. RTP connection[unsecure]: 192.168.200.5:10066(10067)
    20:07:21.587 Remote SDP is set for legC:122.2
    20:07:16.376 [CM503008]: Call(120): Call is terminated
    20:07:16.376 [CM503021]: Call(120): ACK is not received
    20:07:08.389 [CM505004]: Bridge:[Bridge to Lao Star] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhoneSystem 9.0.15776.0] PBX contact: [sip:1000@192.168.200.5:5060]
    20:07:08.389 [CM503002]: Call(122): Alerting sip:1000@192.168.10.15:5060
    20:07:05.628 [CM503025]: Call(122): Calling PBXline:222@(Ln.1000@Bridge to Lao Star)@[Dev:sip:1000@192.168.10.15:5060]
    20:07:05.628 [MS210002] C:122.2:Offer provided. Connection(transcoding mode): 192.168.200.5:7140(7141)
    20:07:05.596 [CM503004]: Call(122): Route 1: PBXline:222@(Ln.1000@Bridge to Lao Star)@[Dev:sip:1000@192.168.10.15:5060]
    20:07:05.581 [CM503010]: Making route(s) to <sip:222@192.168.200.5:5060;user=phone>
    20:07:05.581 [MS210000] C:122.1:Offer received. RTP connection: 68.111.254.169:2234(2235)
    20:07:05.565 Remote SDP is set for legC:122.1
    20:07:05.565 [CM505001]: Ext.111: Device info: Device Identified: [Man: Polycom;Mod: SoundPoint IP Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [PolycomSoundPointIP-SPIP_550-UA/3.3.1.0769] PBX contact: [sip:111@98.175.250.85:5060]
    20:07:05.565 [CM503001]: Call(122): Incoming call from Ext.111 to <sip:222@192.168.200.5:5060;user=phone>
    20:07:05.565 [CM500002]: Info on incoming INVITE:
    INVITE sip:222@192.168.200.5:5060;user=phone SIP/2.0
    Via: SIP/2.0/UDP 68.111.254.169;branch=z9hG4bK34025520DC4D58DF
    Max-Forwards: 70
    Contact: <sip:111@68.111.254.169>
    To: <sip:222@192.168.200.5:5060;user=phone>
    From: "Denny Home"<sip:111@192.168.200.5:5060>;tag=9E350597-EE213FDA
    Call-ID: 61bdb59b-4c3a3a4e-a068c215@68.111.254.169
    CSeq: 2 INVITE
    Accept-Language: en
    Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
    Proxy-Authorization: Digest username="111",realm="3CXPhoneSystem",nonce="414d535c034c3a6986:1fee98276b916fa21b94db16f8803d5d",uri="sip:222@98.175.250.85:5060;user=phone",response="9370e56e340bfb9688789e64f1fb110c",algorithm=MD5
    Supported: 100rel, replaces
    User-Agent: PolycomSoundPointIP-SPIP_550-UA/3.3.1.0769
    Allow-Events: talk, hold, conference
    Content-Length: 0


    Here's what it shows on the log on the Andriod side of 3CX:

    11:07:56.675 [CM503008]: Call(11): Call is terminated
    11:07:35.771 [CM503008]: Call(10): Call is terminated
    11:07:30.841 Currently active calls - 2: [10,11]
    11:07:24.227 Session 14789 of leg C:11.1 is confirmed
    11:07:23.041 [CM503007]: Call(11): Device joined: sip:222@192.168.10.154:5060
    11:07:23.041 [CM503007]: Call(11): Device joined: sip:1000@192.168.200.5:5060;rinstance=b85b1ec96573bf17
    11:07:23.026 [MS210003] C:11.1:Answer provided. Connection(transcoding mode[unsecure]):192.168.10.15:7036(7037)
    11:07:23.026 [MS210001] C:11.2:Answer received. RTP connection[unsecure]: 192.168.10.154:4000(4001)
    11:07:23.026 Remote SDP is set for legC:11.2
    11:07:19.235 [CM503008]: Call(9): Call is terminated
    11:07:10.125 [CM505001]: Ext.222: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone for Android 1.2.9] PBX contact: [sip:222@192.168.10.15:5060]
    11:07:10.125 [CM503002]: Call(11): Alerting sip:222@192.168.10.154:5060
    11:07:09.984 [CM503025]: Call(11): Calling Ext:Ext.222@[Dev:sip:222@192.168.10.154:5060]
    11:07:09.984 [MS210002] C:11.2:Offer provided. Connection(transcoding mode): 192.168.10.15:7038(7039)
    11:07:09.953 [CM503004]: Call(11): Route 1: Ext:Ext.222@[Dev:sip:222@192.168.10.154:5060]
    11:07:09.953 [MS210000] C:11.1:Offer received. RTP connection: 192.168.10.15:10022(10023)
    11:07:09.937 [CM503010]: Making route(s) to <sip:222@192.168.10.15:5060>
    11:07:09.937 Remote SDP is set for legC:11.1
    11:07:09.937 [CM505004]: Bridge:[Bridge to Malimar San Diego] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhoneSystem 9.0.15776.0] PBX contact: [sip:1000@192.168.10.15:5060]
    11:07:09.937 [CM503001]: Call(11): Incoming call from 8774007733@(Ln.1000@Bridge to Malimar San Diego) to <sip:222@192.168.10.15:5060>
    11:07:09.922 [CM503012]: Inbound out-of-office hours rule (unnamed) for 1000 forwards to DN:200
    11:07:09.922 Looking for inbound target: called=222; caller=8774007733
    11:07:09.922 [CM500002]: Info on incoming INVITE:
    INVITE sip:222@192.168.10.15:5060 SIP/2.0
    Via: SIP/2.0/UDP 192.168.10.15:5081;branch=z9hG4bK-d8754z-4a7d601117620638-2---d8754z-;rport=5081
    Via: SIP/2.0/UDP 98.175.250.85:5090;branch=z9hG4bK-d8754z-tunneltid-1---d8754z-;rport
    Via: SIP/2.0/UDP 192.168.200.5:5060;branch=z9hG4bK-d8754z-4a7d601117620638-1---d8754z-;rport=5060
    Max-Forwards: 68
    Record-Route: <sip:3cxBridge@192.168.10.15:5081;user=proxy;uri="98.175.250.85:5090">
    Contact: <sip:1000@192.168.200.5:5060>
    To: <sip:222@192.168.10.15:5060>
    From: "Denny Home"<sip:1000@192.168.10.15:5060>;tag=a85d9972
    Call-ID: MzNhZTJjOGNiYjM2ODg5OGQxYTZjODgzMmJhMWZlZDE.
    CSeq: 2 INVITE
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
    Proxy-Authorization: Digest username="1000",realm="3CXPhoneSystem",nonce="414d535c034c3a6c15:a0845a9d9054b87367a1e4b6e5f0f438",uri="sip:222@192.168.10.15:5060",response="b8fe1a167ae194001d54c89a8098af95",algorithm=MD5
    Supported: replaces
    User-Agent: 3CXPhoneSystem 9.0.15776.0
    Content-Length: 0
    Remote-Party-ID: "Denny Home"<sip:8774007733@malimar.net:5060>;party=calling
     
  2. malimar

    Joined:
    Oct 26, 2010
    Messages:
    10
    Likes Received:
    0
    Confirmed to be working just fine the other way around.

    Andriod remote ext 222 -> 3CX -> bridge -> 3CX -> Polycom 550 remote ext 111


    Here's the log from the Andriod side 3CX:

    11:31:07.378 Currently active calls - 1: [13]
    11:30:37.351 Currently active calls - 1: [13]
    11:30:05.351 Currently active calls - 1: [13]
    11:29:46.807 Session 15083 of leg C:13.1 is confirmed
    11:29:46.671 [CM503007]: Call(13): Device joined: sip:1000@192.168.200.5:5060;rinstance=b85b1ec96573bf17
    11:29:46.668 [CM503007]: Call(13): Device joined: sip:222@192.168.10.154:5060
    11:29:46.665 [MS210003] C:13.1:Answer provided. Connection(transcoding mode[unsecure]):192.168.10.15:7044(7045)
    11:29:46.660 [MS210001] C:13.2:Answer received. RTP connection[unsecure]: 192.168.10.15:10030(10031)
    11:29:46.658 Remote SDP is set for legC:13.2
    11:29:43.741 [CM505004]: Bridge:[Bridge to Malimar San Diego] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhoneSystem 9.0.15776.0] PBX contact: [sip:1000@192.168.10.15:5060]
    11:29:43.741 [CM503002]: Call(13): Alerting sip:1000@192.168.200.5:5060;rinstance=b85b1ec96573bf17
    11:29:40.730 [CM503025]: Call(13): Calling PBXline:111@(Ln.1000@Bridge to Malimar San Diego)@[Dev:sip:1000@192.168.200.5:5060;rinstance=b85b1ec96573bf17]
    11:29:40.727 [MS210002] C:13.2:Offer provided. Connection(transcoding mode): 192.168.10.15:7046(7047)
    11:29:40.696 [CM503004]: Call(13): Route 1: PBXline:111@(Ln.1000@Bridge to Malimar San Diego)@[Dev:sip:1000@192.168.200.5:5060;rinstance=b85b1ec96573bf17]
    11:29:40.684 [CM503010]: Making route(s) to <sip:111@192.168.10.15>
    11:29:40.684 [MS210000] C:13.1:Offer received. RTP connection: 192.168.10.154:4004(4005)
    11:29:40.680 Remote SDP is set for legC:13.1
    11:29:40.680 [CM505001]: Ext.222: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone for Android 1.2.9] PBX contact: [sip:222@192.168.10.15:5060]
    11:29:40.673 [CM503001]: Call(13): Incoming call from Ext.222 to <sip:111@192.168.10.15>
    11:29:40.667 [CM500002]: Info on incoming INVITE:
    INVITE sip:111@192.168.10.15 SIP/2.0
    Via: SIP/2.0/UDP 192.168.10.154:5060;rport=5060;branch=z9hG4bKPjqF5qSZ34vPsC3HIe6NXSiEnBOlk2V-Pr
    Max-Forwards: 70
    Contact: <sip:222@192.168.10.154:5060>
    To: <sip:111@192.168.10.15>
    From: <sip:222@192.168.10.15>;tag=1CKVM06yd6K0h5wt1BVzlueVM1-1uJC5
    Call-ID: fzJH54TjsmF0u4ic01ZMVMQEludalDgh
    CSeq: 31857 INVITE
    Session-Expires: 1800
    Min-SE: 90
    Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
    Proxy-Authorization: Digest username="222",realm="3CXPhoneSystem",nonce="414d535c034c3fb421:575bdcf55d6ef3fa2612cd27ce2b3e7b",uri="sip:111@192.168.10.15",response="c447686d62c8512b75c40a2d37f09aea",algorithm=MD5
    Supported: replaces, 100rel, timer, norefersub
    User-Agent: 3CXPhone for Android 1.2.9
    Content-Length: 0

    Here is the log from the Polycom side of 3CX:

    20:32:04.249 Currently active calls - 1: [125]
    20:31:34.062 Currently active calls - 1: [125]
    20:31:03.875 Currently active calls - 1: [125]
    20:30:33.688 Currently active calls - 1: [125]
    20:30:03.502 Currently active calls - 1: [125]
    20:29:44.844 Session 36072 of leg C:125.1 is confirmed
    20:29:43.658 [CM503007]: Call(125): Device joined: sip:111@68.111.254.169:5060
    20:29:43.658 [CM503007]: Call(125): Device joined: sip:1000@192.168.10.15:5060
    20:29:43.658 [MS210003] C:125.1:Answer provided. Connection(transcoding mode[unsecure]):192.168.200.5:7144(7145)
    20:29:43.642 [MS210001] C:125.2:Answer received. RTP connection[unsecure]: 68.111.254.169:2240(2241)
    20:29:43.642 Remote SDP is set for legC:125.2
    20:29:41.146 [CM505001]: Ext.111: Device info: Device Identified: [Man: Polycom;Mod: SoundPoint IP Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [PolycomSoundPointIP-SPIP_550-UA/3.3.1.0769] PBX contact: [sip:111@98.175.250.85:5060]
    20:29:41.146 [CM503002]: Call(125): Alerting sip:111@68.111.254.169:5060
    20:29:40.944 [CM503025]: Call(125): Calling Ext:Ext.111@[Dev:sip:111@68.111.254.169:5060]
    20:29:40.944 [MS210002] C:125.2:Offer provided. Connection(transcoding mode): 98.175.250.85:9020(9021)
    20:29:40.866 [CM503004]: Call(125): Route 1: Ext:Ext.111@[Dev:sip:111@68.111.254.169:5060]
    20:29:40.866 [MS210000] C:125.1:Offer received. RTP connection: 192.168.200.5:10074(10075)
    20:29:40.866 [CM503010]: Making route(s) to <sip:111@192.168.200.5:5060>
    20:29:40.866 Remote SDP is set for legC:125.1
    20:29:40.866 [CM505004]: Bridge:[Bridge to Lao Star] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhoneSystem 9.0.15776.0] PBX contact: [sip:1000@192.168.200.5:5060]
    20:29:40.850 [CM503001]: Call(125): Incoming call from 1000@(Ln.1000@Bridge to Lao Star) to <sip:111@192.168.200.5:5060>
    20:29:40.850 [CM503012]: Inbound out-of-office hours rule (unnamed) for 1000 forwards to DN:100
    20:29:40.834 Looking for inbound target: called=111; caller=1000
    20:29:40.834 [CM500002]: Info on incoming INVITE:
    INVITE sip:111@192.168.200.5:5060;rinstance=b85b1ec96573bf17 SIP/2.0
    Via: SIP/2.0/UDP 192.168.200.5:5081;branch=z9hG4bK-d8754z-fc0f245b1a356d59-2---d8754z-;rport=5081
    Via: SIP/2.0/UDP 202.144.190.48:5090;branch=z9hG4bK-d8754z-tunneltid-1---d8754z-;rport
    Via: SIP/2.0/UDP 192.168.10.15:5060;branch=z9hG4bK-d8754z-fc0f245b1a356d59-1---d8754z-;rport=5060
    Max-Forwards: 68
    Record-Route: <sip:3cxBridge@192.168.200.5:5081;user=proxy;uri="202.144.190.48:5090">
    Contact: <sip:1000@192.168.10.15:5060>
    To: <sip:111@192.168.200.5:5060;rinstance=b85b1ec96573bf17>
    From: <sip:1000@192.168.200.5:5060;rinstance=b85b1ec96573bf17>;tag=8e19a317
    Call-ID: MTQ2OGI5M2Y0Njc2ZWE2MWY1YTllYzZkM2NkMjVhYTE.
    CSeq: 2 INVITE
    Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE
    Proxy-Authorization: Digest username="1000",realm="3CXPhoneSystem",nonce="414d535c034c3fb271:76089d22d066f7c760c6e02a742776fe",uri="sip:111@192.168.200.5:5060;rinstance=b85b1ec96573bf17",response="6a5e70c7d3abfc7417af358d112027db",algorithm=MD5
    Supported: replaces
    User-Agent: 3CXPhoneSystem 9.0.15776.0
    Content-Length: 0
    Remote-Party-ID: "Zak Malimar"<sip:1000@192.168.10.15:5060>;party=calling
     
  3. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    11,129
    Likes Received:
    330
    This is the problem, I'm assuming that for whatever reason, firewall, provider, router, etc., packets are not able to get through in that direction.
     
  4. mfm

    mfm Active Member

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

    ACK is not received is generally an indication of incorrect NAT, can you kindly post the output of your firewall checker?

    Settings > FIrewall checker
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. wzaatar

    Joined:
    Aug 1, 2007
    Messages:
    90
    Likes Received:
    0
    I fought with this a lot! Effectively, it is a NAT issue. First, try your firewall checker on 3CX. Also, try using fixed port forwards for the external ports as per the 3CX instructions in the Firewall checker.

    W.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. malimar

    Joined:
    Oct 26, 2010
    Messages:
    10
    Likes Received:
    0
    Heres our 3cx firewall checker log:

    3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved.

    <22:32:07>: Phase 1, checking servers connection, please wait...
    <22:32:07>: Stun Checker service is reachable. Phase 1 check passed.
    <22:32:07>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
    <22:32:08>: UDP SIP Port is set to 5060. Response received WITH TRANSLATION 16185::5060. Phase 2a check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/

    <22:32:08>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
    <22:32:08>: TCP SIP Port is set to 5060. Response received WITH TRANSLATION 16185::5060. Phase 2b check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/

    <22:32:08>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
    <22:32:08>: TCP TUNNEL Port is set to 5090. Response received WITH TRANSLATION 16215::5090. Phase 3 check passed with WARNINGS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/

    <22:32:08>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
    <22:32:13>: UDP RTP Port 9000. Response received WITH TRANSLATION 20125::9000. Phase 4-01 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9001. Response received WITH TRANSLATION 20126::9001. Phase 4-02 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9002. Response received WITH TRANSLATION 20127::9002. Phase 4-03 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9003. Response received WITH TRANSLATION 20128::9003. Phase 4-04 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9004. Response received WITH TRANSLATION 20129::9004. Phase 4-05 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9005. Response received WITH TRANSLATION 20130::9005. Phase 4-06 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9006. Response received WITH TRANSLATION 20131::9006. Phase 4-07 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9007. Response received WITH TRANSLATION 20132::9007. Phase 4-08 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9008. Response received WITH TRANSLATION 20133::9008. Phase 4-09 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9009. Response received WITH TRANSLATION 20134::9009. Phase 4-10 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9010. Response received WITH TRANSLATION 20135::9010. Phase 4-11 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9011. Response received WITH TRANSLATION 20136::9011. Phase 4-12 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9012. Response received WITH TRANSLATION 20137::9012. Phase 4-13 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9013. Response received WITH TRANSLATION 20138::9013. Phase 4-14 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9014. Response received WITH TRANSLATION 20139::9014. Phase 4-15 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9015. Response received WITH TRANSLATION 20140::9015. Phase 4-16 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9016. Response received WITH TRANSLATION 20141::9016. Phase 4-17 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9017. Response received WITH TRANSLATION 20142::9017. Phase 4-18 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9018. Response received WITH TRANSLATION 20143::9018. Phase 4-19 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9019. Response received WITH TRANSLATION 20144::9019. Phase 4-20 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9020. Response received WITH TRANSLATION 20145::9020. Phase 4-21 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9021. Response received WITH TRANSLATION 20146::9021. Phase 4-22 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9022. Response received WITH TRANSLATION 20147::9022. Phase 4-23 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9023. Response received WITH TRANSLATION 20148::9023. Phase 4-24 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9024. Response received WITH TRANSLATION 20149::9024. Phase 4-25 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9025. Response received WITH TRANSLATION 20150::9025. Phase 4-26 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9026. Response received WITH TRANSLATION 20151::9026. Phase 4-27 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9027. Response received WITH TRANSLATION 20152::9027. Phase 4-28 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9028. Response received WITH TRANSLATION 20153::9028. Phase 4-29 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9029. Response received WITH TRANSLATION 20154::9029. Phase 4-30 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9030. Response received WITH TRANSLATION 20155::9030. Phase 4-31 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9031. Response received WITH TRANSLATION 20156::9031. Phase 4-32 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9032. Response received WITH TRANSLATION 20157::9032. Phase 4-33 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9033. Response received WITH TRANSLATION 20158::9033. Phase 4-34 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9034. Response received WITH TRANSLATION 20159::9034. Phase 4-35 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9035. Response received WITH TRANSLATION 20160::9035. Phase 4-36 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9036. Response received WITH TRANSLATION 20161::9036. Phase 4-37 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9037. Response received WITH TRANSLATION 20162::9037. Phase 4-38 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9038. Response received WITH TRANSLATION 20163::9038. Phase 4-39 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9039. Response received WITH TRANSLATION 20164::9039. Phase 4-40 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9040. Response received WITH TRANSLATION 20165::9040. Phase 4-41 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9041. Response received WITH TRANSLATION 20166::9041. Phase 4-42 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9042. Response received WITH TRANSLATION 20167::9042. Phase 4-43 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9043. Response received WITH TRANSLATION 20168::9043. Phase 4-44 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9044. Response received WITH TRANSLATION 20169::9044. Phase 4-45 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9045. Response received WITH TRANSLATION 20170::9045. Phase 4-46 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9046. Response received WITH TRANSLATION 20171::9046. Phase 4-47 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9047. Response received WITH TRANSLATION 20172::9047. Phase 4-48 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9048. Response received WITH TRANSLATION 20173::9048. Phase 4-49 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/
    <22:32:13>: UDP RTP Port 9049. Response received WITH TRANSLATION 20174::9049. Phase 4-50 check passed with WARNINGS. Some functionality may be IMPAIRED. For more information, please visit http://www.3cx.com/blog/docs/firewall-checker/


    Application exit code is 53
     
  7. abc123

    abc123 Active Member

    Joined:
    Nov 9, 2009
    Messages:
    712
    Likes Received:
    1
    As the others said, it is a NAT issue.

    1. Get a static ip as it solves a lot of problems and means you can turn off stun.
    2. Give your PBX an internal static ip (e.g. 10.10.10.2)
    3. Port forward all the sip ports (TCP and UDP) that need to go in and out over the internet (e.g. 5060, etc. see the user guide) - do port forward not port translation (eg 5060 - 5060).
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. mfm

    mfm Active Member

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

    What firewall are you using, it looks to me that you did not set up any port forwarding at all, stun is used to check fiewall ports so i dont think the issue lies there.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. wzaatar

    Joined:
    Aug 1, 2007
    Messages:
    90
    Likes Received:
    0
    Effectively, your log is reporting an asymmetric port forwarding. So you need to access your router/modem/etc... and do a static mapping between the outside and inside direct to your 3CX workstation for the SIP and RTP ports.

    Cheers,

    W.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. davidcaughman

    Joined:
    Jun 28, 2011
    Messages:
    2
    Likes Received:
    0
    I have run the firewall checker with all tests coming back as passed,
    have put my remote phone in a dmz on its local router, but still get the dropped call after exactly 30 seconds.
    what now
    ?
     
Thread Status:
Not open for further replies.