3CX Phone vs 3CX Server with same VoIP provider

Discussion in '3CX Phone System - General' started by jorgebraga, Jun 14, 2011.

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

    Joined:
    Jun 10, 2011
    Messages:
    4
    Likes Received:
    0
    My problem is the following.

    I have a Portuguese Voip Provider called SAPO.

    My ID is something like +3513020XXXXX

    I configure the correct settings in X-Lite - works fine.
    I configure the correct settings in 3Cx Phone - works fine.
    I configure possible settings in Server (there is a problem with using the plus (+) sign in external name in the server - the phone aparently doesnt have this problem) and i dont get inbound calls.

    Probably its a NAT problem. I have a ZyXel P660W-T1 V3 with port forwarding enabled(but i have some doubts i'm doing everything right there). The LED light in the port status doenst even blink on incoming calls (so the problem is not an inbound rule i think).

    But my questions are:

    Why does it work with X-Lite, and the 3CX Phone, but not with the 3Cx server?
    How come the 3CX phone suports the + sign but not the server?
    How come the 3Cx phone connects to the VoIP provider with no aditional NAT settings or firewall twiking, and the server doesnt?

    Thanks in advance for your time.
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,375
    Likes Received:
    231
    What does the 3CX server logs sow during registration and during an incoming call?
     
  3. jorgebraga

    Joined:
    Jun 10, 2011
    Messages:
    4
    Likes Received:
    0
    The log for registering is attached.

    The log for a received call simply doesnt exist since i cant receive the call (i checked the log continuosly while making a call to the number).

    Nevertheless my question remains. How come X-Lite with the exact same network config works just fine?

    Thank you for your time.
     

    Attached Files:

  4. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,375
    Likes Received:
    231
    It shows that you registered successfully with your provider, but, the log shows that there may be a port translation issue.

    21:40:18.899 [CM306003]: SIP IP:port mapping (2.80.185.49:20469) resolved by STUN server 216.93.246.16:3478 differs from the one (2.80.185.49:20470 resolved by STUN server 178.238.134.190

    If the 3CX log shows no sign of an incoming call, then run the 3CX firewall test to check that all of your ports are open and forwarded properly.
     
  5. jorgebraga

    Joined:
    Jun 10, 2011
    Messages:
    4
    Likes Received:
    0
    Thanks for your time.

    The problem is precisely that. Ports are suposed to be forward but still downt work.

    On the other hand i tried to connect remotely to my IP-PBX (using a 3Cx soft phone) and it worked!

    So the only thing i cannot do is receive calls in VoIP provider.
    Here are the results of the firewall test.

    Code:
    3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved.
    
    <18:54:47>: Phase 1, checking servers connection, please wait...
    <18:54:47>: Stun Checker service is reachable. Phase 1 check passed.
    <18:54:47>: Phase 2a,  Check Port Forwarding to UDP SIP port, please wait...
    <18:54:48>: UDP SIP Port is set to 5060. Response received WITH TRANSLATION 20258::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/
    
    <18:54:48>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
    <18:54:48>: TCP SIP Port is set to 5060. Response received WITH TRANSLATION 20258::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/
    
    <18:54:48>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
    <18:54:49>: TCP TUNNEL Port is set to 5090. Response received WITH TRANSLATION 20262::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/
    
    <18:54:49>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
    <18:54:56>: UDP RTP Port 9000. Response received WITH TRANSLATION 20263::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/
    <18:54:56>: UDP RTP Port 9001. Response received WITH TRANSLATION 20264::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/
    <18:54:56>: UDP RTP Port 9002. Response received WITH TRANSLATION 20265::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/
    <18:54:56>: UDP RTP Port 9003. Response received WITH TRANSLATION 20266::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/
    <18:54:56>: UDP RTP Port 9004. Response received WITH TRANSLATION 20267::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/
    <18:54:56>: UDP RTP Port 9005. Response received WITH TRANSLATION 20268::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/
    <18:54:56>: UDP RTP Port 9006. Response received WITH TRANSLATION 20269::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/
    <18:54:56>: UDP RTP Port 9007. Response received WITH TRANSLATION 20270::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/
    <18:54:56>: UDP RTP Port 9008. Response received WITH TRANSLATION 20271::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/
    <18:54:56>: UDP RTP Port 9009. Response received WITH TRANSLATION 20272::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/
    <18:54:56>: UDP RTP Port 9010. Response received WITH TRANSLATION 20273::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/
    <18:54:56>: UDP RTP Port 9011. Response received WITH TRANSLATION 20274::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/
    <18:54:56>: UDP RTP Port 9012. Response received WITH TRANSLATION 20275::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/
    <18:54:56>: UDP RTP Port 9013. Response received WITH TRANSLATION 20276::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/
    <18:54:56>: UDP RTP Port 9014. Response received WITH TRANSLATION 20277::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/
    <18:54:56>: UDP RTP Port 9015. Response received WITH TRANSLATION 20278::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/
    <18:54:56>: UDP RTP Port 9016. Response received WITH TRANSLATION 20279::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/
    <18:54:56>: UDP RTP Port 9017. Response received WITH TRANSLATION 20280::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/
    <18:54:56>: UDP RTP Port 9018. Response received WITH TRANSLATION 20281::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/
    <18:54:56>: UDP RTP Port 9019. Response received WITH TRANSLATION 20282::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/
    <18:54:56>: UDP RTP Port 9020. Response received WITH TRANSLATION 20283::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/
    <18:54:56>: UDP RTP Port 9021. Response received WITH TRANSLATION 20284::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/
    <18:54:56>: UDP RTP Port 9022. Response received WITH TRANSLATION 20285::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/
    <18:54:56>: UDP RTP Port 9023. Response received WITH TRANSLATION 20286::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/
    <18:54:56>: UDP RTP Port 9024. Response received WITH TRANSLATION 20287::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/
    <18:54:56>: UDP RTP Port 9025. Response received WITH TRANSLATION 20288::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/
    <18:54:56>: UDP RTP Port 9026. Response received WITH TRANSLATION 20289::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/
    <18:54:56>: UDP RTP Port 9027. Response received WITH TRANSLATION 20290::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/
    <18:54:56>: UDP RTP Port 9028. Response received WITH TRANSLATION 20291::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/
    <18:54:56>: UDP RTP Port 9029. Response received WITH TRANSLATION 20292::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/
    <18:54:56>: UDP RTP Port 9030. Response received WITH TRANSLATION 20293::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/
    <18:54:56>: UDP RTP Port 9031. Response received WITH TRANSLATION 20294::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/
    <18:54:56>: UDP RTP Port 9032. Response received WITH TRANSLATION 20295::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/
    <18:54:56>: UDP RTP Port 9033. Response received WITH TRANSLATION 20296::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/
    <18:54:56>: UDP RTP Port 9034. Response received WITH TRANSLATION 20297::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/
    <18:54:56>: UDP RTP Port 9035. Response received WITH TRANSLATION 20298::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/
    <18:54:56>: UDP RTP Port 9036. Response received WITH TRANSLATION 20299::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/
    <18:54:56>: UDP RTP Port 9037. Response received WITH TRANSLATION 20300::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/
    <18:54:56>: UDP RTP Port 9038. Response received WITH TRANSLATION 20301::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/
    <18:54:56>: UDP RTP Port 9039. Response received WITH TRANSLATION 20302::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/
    <18:54:56>: UDP RTP Port 9040. Response received WITH TRANSLATION 20303::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/
    <18:54:56>: UDP RTP Port 9041. Response received WITH TRANSLATION 20304::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/
    <18:54:56>: UDP RTP Port 9042. Response received WITH TRANSLATION 20305::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/
    <18:54:56>: UDP RTP Port 9043. Response received WITH TRANSLATION 20306::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/
    <18:54:56>: UDP RTP Port 9044. Response received WITH TRANSLATION 20307::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/
    <18:54:56>: UDP RTP Port 9045. Response received WITH TRANSLATION 20308::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/
    <18:54:56>: UDP RTP Port 9046. Response received WITH TRANSLATION 20309::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/
    <18:54:56>: UDP RTP Port 9047. Response received WITH TRANSLATION 20310::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/
    <18:54:56>: UDP RTP Port 9048. Response received WITH TRANSLATION 20311::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/
    <18:54:56>: UDP RTP Port 9049. Response received WITH TRANSLATION 20312::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
    
    It stills bafles me because suposely all ports are correctly forward in the router. I even tried accessing port 5000 (my phone web interface) from outside and it worked fine. When i run tests from outside (for instance in port 5060 in site http://www.yougetsignal.com/tools/open-ports/) they appear opened or close as service in IP PBX was or not running.

    So who the heck is translating port addresses?!?

    Thanks again for your time.
     
  6. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    http://en.wikipedia.org/wiki/Network_address_translation (serious)
    h t t p : / / w w w . h o w s t u f f w o r k s . c o m / n a t . h t m (funny)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. jorgebraga

    Joined:
    Jun 10, 2011
    Messages:
    4
    Likes Received:
    0
    Eureka - Problem solved!!!

    The router does not do NAT but PAt (in Zyxel's SUA mode the router changes all ports, and port forwarding changes port number as well!!)

    Th full-cone NAT is only achieved with a One-to-one NAT mode.

    Going to the store to buy a new router!!!

    Thanks to all for the help. Hope i can giveback to the community soon the help given.

    But my initial question prevales: How come i dont have this problem with X-Lite? How do this free software solves the problem and 3Cx doesnt?
     
Thread Status:
Not open for further replies.