One-Way Audio with only one VOIP Provider - all others are f

Discussion in '3CX Phone System - General' started by HunterJoe, Jul 31, 2012.

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

    Joined:
    Jul 31, 2012
    Messages:
    2
    Likes Received:
    0
    I have multiple VoIP Providers that supply lines to multiple businesses all managed by one 3CX system.

    All of the VoIP Providers lines work fine except for one (NexVortex) where I get one-way audio on Outbound calls only.

    I am using an Apple Airport on Windows 7 network, have run Firewall Checker and recieve a failure on Phase 2a with exit code 2.

    I have been searching these forums for DAYS trying to figure out why this is happening on this VoIP provider only and not the others.

    Any help would be appreciated.

    Joe.
     
  2. redmond1

    Joined:
    Jul 31, 2012
    Messages:
    2
    Likes Received:
    0
    Re: One-Way Audio with only one VOIP Provider - all others a

    when you have an answer send it over my way I have just about the same problem, I have no sound at all over the Wan but on the Lan works fine.
     
  3. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,083
    Likes Received:
    61
    Re: One-Way Audio with only one VOIP Provider - all others a

    More detail is needed.

    What version of 3CX. Did you follow the setup guide on the blog related to firewall port forward settings? Is PBX provides audio checked for nexVortex? Is the one-way audio experienced on both inbound and outbound calls? It is likely that the firewall issue will need to be resolved in order to eliminate the possibility that it is the culprit - despite the fact that other providers are working. Can you post a copy of a verbose log showing the issue?
     
  4. HunterJoe

    Joined:
    Jul 31, 2012
    Messages:
    2
    Likes Received:
    0
    Re: One-Way Audio with only one VOIP Provider - all others a

    Sorry it has taken me so long to get back to this post.

    I have been busy doing other IT things, but did find the time to try to figure this out. I finally got the firewall checker to run in an effort to eliminate the firewall as the culprit. What I found was a bit disturbing. I am now experiencing a lot of other issues as well, but will make separate posts for those.

    The 3CX version is Version 10. Below is the output of the Firewall checker.

    Code:
    3CX Firewall Checker, v1.0. Copyright (C) 3CX Ltd. All rights reserved.
    
    <07:45:54>: Phase 1, checking servers connection, please wait...
    <07:45:54>: Stun Checker service is reachable. Phase 1 check passed.
    <07:45:54>: Phase 2a,  Check Port Forwarding to UDP SIP port, please wait...
    <07:45:54>: UDP SIP Port is set to 5060. Response received correctly with no translation. Phase 2a check passed.
    
    <07:45:54>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
    <07:45:54>: TCP SIP Port is set to 5060. Response received correctly with no translation. Phase 2b check passed.
    
    <07:45:54>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
    <07:45:55>: TCP TUNNEL Port is set to 5090. Response received correctly with no translation. Phase 3 check passed.
    
    <07:45:55>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
    <07:45:58>: UDP RTP Port 9000. Response received correctly with no translation. Phase 4-01 check passed.
    <07:45:58>: UDP RTP Port 9001. Response received WITH TRANSLATION 45288::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/
    <07:45:58>: UDP RTP Port 9002. Response received WITH TRANSLATION 37522::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/
    <07:45:58>: UDP RTP Port 9003. Response received WITH TRANSLATION 48463::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/
    <07:45:58>: UDP RTP Port 9004. Response received WITH TRANSLATION 41692::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/
    <07:45:58>: UDP RTP Port 9005. Response received WITH TRANSLATION 45558::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/
    <07:45:58>: UDP RTP Port 9006. Response received WITH TRANSLATION 42217::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/
    <07:45:58>: UDP RTP Port 9007. Response received WITH TRANSLATION 41777::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/
    <07:45:58>: UDP RTP Port 9008. Response received WITH TRANSLATION 43955::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/
    <07:45:58>: UDP RTP Port 9009. Response received WITH TRANSLATION 47531::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/
    <07:45:58>: UDP RTP Port 9010. Response received WITH TRANSLATION 39955::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/
    <07:45:58>: UDP RTP Port 9011. Response received WITH TRANSLATION 34353::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/
    <07:45:58>: UDP RTP Port 9012. Response received WITH TRANSLATION 38462::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/
    <07:45:58>: UDP RTP Port 9013. Response received WITH TRANSLATION 45854::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/
    <07:45:58>: UDP RTP Port 9014. Response received WITH TRANSLATION 34621::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/
    <07:45:58>: UDP RTP Port 9015. Response received WITH TRANSLATION 46937::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/
    <07:45:58>: UDP RTP Port 9016. Response received WITH TRANSLATION 43117::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/
    <07:45:58>: UDP RTP Port 9017. Response received WITH TRANSLATION 47878::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/
    <07:45:58>: UDP RTP Port 9018. Response received WITH TRANSLATION 39334::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/
    <07:45:58>: UDP RTP Port 9019. Response received WITH TRANSLATION 33458::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/
    <07:45:58>: UDP RTP Port 9020. Response received WITH TRANSLATION 34659::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/
    <07:45:58>: UDP RTP Port 9021. Response received WITH TRANSLATION 38284::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/
    <07:45:58>: UDP RTP Port 9022. Response received WITH TRANSLATION 36685::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/
    <07:45:58>: UDP RTP Port 9023. Response received WITH TRANSLATION 39412::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/
    <07:45:58>: UDP RTP Port 9024. Response received WITH TRANSLATION 37223::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/
    <07:45:58>: UDP RTP Port 9025. Response received WITH TRANSLATION 45997::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/
    <07:45:58>: UDP RTP Port 9026. Response received WITH TRANSLATION 48885::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/
    <07:45:58>: UDP RTP Port 9027. Response received WITH TRANSLATION 39623::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/
    <07:45:58>: UDP RTP Port 9028. Response received WITH TRANSLATION 39387::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/
    <07:45:58>: UDP RTP Port 9029. Response received WITH TRANSLATION 47580::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/
    <07:45:58>: UDP RTP Port 9030. Response received WITH TRANSLATION 39885::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/
    <07:45:58>: UDP RTP Port 9031. Response received WITH TRANSLATION 40360::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/
    <07:45:58>: UDP RTP Port 9032. Response received WITH TRANSLATION 33601::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/
    <07:45:58>: UDP RTP Port 9033. Response received WITH TRANSLATION 35504::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/
    <07:45:58>: UDP RTP Port 9034. Response received WITH TRANSLATION 48763::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/
    <07:45:58>: UDP RTP Port 9035. Response received WITH TRANSLATION 46554::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/
    <07:45:58>: UDP RTP Port 9036. Response received WITH TRANSLATION 48607::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/
    <07:45:58>: UDP RTP Port 9037. Response received WITH TRANSLATION 39290::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/
    <07:45:58>: UDP RTP Port 9038. Response received WITH TRANSLATION 36503::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/
    <07:45:58>: UDP RTP Port 9039. Response received WITH TRANSLATION 49054::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/
    <07:45:58>: UDP RTP Port 9040. Response received WITH TRANSLATION 42274::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/
    <07:45:58>: UDP RTP Port 9041. Response received WITH TRANSLATION 41275::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/
    <07:45:58>: UDP RTP Port 9042. Response received WITH TRANSLATION 38613::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/
    <07:45:58>: UDP RTP Port 9043. Response received WITH TRANSLATION 43687::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/
    <07:45:58>: UDP RTP Port 9044. Response received WITH TRANSLATION 47210::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/
    <07:45:58>: UDP RTP Port 9045. Response received WITH TRANSLATION 42348::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/
    <07:45:58>: UDP RTP Port 9046. Response received WITH TRANSLATION 35024::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/
    <07:45:58>: UDP RTP Port 9047. Response received WITH TRANSLATION 34226::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/
    <07:45:58>: UDP RTP Port 9048. Response received WITH TRANSLATION 43340::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/
    <07:45:58>: UDP RTP Port 9049. Response received WITH TRANSLATION 34610::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 49
    
    I assume that the Apple Airport we are using for our router will not handle SIP properly for whatever reason. So I am looking at purchasing another router. I want to get the Cisco UC320W so that I can just replace this 3CX server and let that router handle it all, but my boss does not want to dump the server (since he has paid for the license already).

    I have read the manual from front to back numerous times, setup everything accordingly inside of 3CX, yet I still have a ton of issues with this system, and despite buying a license we get no tech support of any kind outside of an hourly rate of hundreds of dollars an hour? I just need this to work and not be so complicated and broken.

    Frustration abounds.
    Joe.
     
  5. lneblett

    lneblett Well-Known Member

    Joined:
    Sep 7, 2010
    Messages:
    2,083
    Likes Received:
    61
    Re: One-Way Audio with only one VOIP Provider - all others a

    OK, I have been using nexVortex succesfully for several years..since V9.

    In any event, is it safe to assume that you also did the appropriate firewall port forwarding configuration? You indicated in an earlier post that the exit code was 2a, but the latest post indicates code 49; so it seem that something has changed. I also did a web search and found a great deal of agnst in using the Airport, but not only on 3CX but with Cisco as well. It appears that the device is simply not very friendly to VoiP in general with SIP being a real issue. I will also assume that any SIP-ALG settings are disabled and I will further assume that you used the nexVortex template when establishing the service. You might also check in the nexVortex settings under VoIP provider to ensure that PBX delivers audio is checked. I wish I could help more here, but I do not have that router.

    While I might understand the frustration, it seems that the more cost effective solution considering the investment already made is to simply change out the airport for a router that works. I have systems using DLink, Netgear, MicroTik, linksys and a few others to include more robust enterprise types. If using an Airport currently, I suspect that using a Netgear, Dlink or Linksys will offer a competitive solution at a cost far below a system swap out and re-train period.

    If you have the upgrade insurance, I also encourage you to upgrade to V11; not that it has a solution for this issue, but you mention many other issues. As this is your first post, it could be that upgrading might provide some relief to whatever the other issues are.
     
Thread Status:
Not open for further replies.