New install, having audio/call issues

Discussion in '3CX Phone System - General' started by zzyzxx71, Feb 17, 2012.

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

    Joined:
    Feb 17, 2012
    Messages:
    13
    Likes Received:
    0
    Greetings,

    I've recently setup a demo 3CX server as part of a beta test towards converting our phone system over to VOIP.

    I currently have it configured with multiple extensions, internally things are working as expected - both the PC versions of the softphone and mobile platforms are working via the LAN and WiFi on the inside.

    Externally we're having odd issues though - I've disabled STUN, the firewall checker response favorably.

    Firewall Checker log:
    ----

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

    I've opened up the following ports (I know this is overkill, but it is beta testing)
    9000-9100 udp
    5090 UDP/TCP
    5060-5061 UDP/TCP
    10000-20000 UDP

    I also have 3478 opened both ways (this was when I was troubleshooting STUN as the possible cause of the issue)

    I've also configured a SIP ALG that came with our firewall (It's a Watchguard X750e that I can't wait to Office Space when the current license period expires)

    Even with all that, we're experiencing 1 way/no audio, calls that immediatenly answer, but the recipient gets a brief ring and then nothing, etc.

    Below is an example of the Server Activity Log from a failed call:

    Code:
    14:41:10.058  [CM503008]: Call(1): Call is terminated
    14:41:05.322  [CM503007]: Call(1): Device joined: sip:9999@127.0.0.1:40600;rinstance=e03af19728fd9507
    14:41:05.318  [CM503007]: Call(1): Device joined: sip:6125@172.16.0.1:32994
    14:41:05.303  [CM505001]: Ext.9999: Device info: Device Identified: [Man: 3CX Ltd.;Mod: Voice Mail Menu;Rev: General] Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CX Voice Mail Menu] PBX contact: [sip:9999@127.0.0.1:5060]
    14:41:05.303  [CM503002]: Call(1): Alerting sip:9999@127.0.0.1:40600;rinstance=e03af19728fd9507
    14:41:05.110  [CM503025]: Call(1): Calling Ext:Ext.9999@[Dev:sip:9999@127.0.0.1:40600;rinstance=e03af19728fd9507]
    14:41:05.062  [CM503005]: Call(1): Forwarding: Ext:Ext.9999@[Dev:sip:9999@127.0.0.1:40600;rinstance=e03af19728fd9507]
    14:41:05.059  [CM503016]: Call(1): Attempt to reach <sip:6128@12.191.106.100:5060> failed. Reason: Not Registered
    14:41:05.058  [CM503017]: Call(1): Target is not registered: Ext.6128
    14:41:05.048  [CM503010]: Making route(s) to <sip:6128@12.191.106.100:5060>
    14:41:05.043  [CM505001]: Ext.6125: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [3CXPhone for Android 1.3.4] PBX contact: [sip:6125@172.16.0.25:5060]
    14:41:05.039  [CM503001]: Call(1): Incoming call from Ext.6125 to <sip:6128@12.191.106.100:5060>
    
    the firewall is 172.16.0.1
    the server is 172.16.0.25
    the external IP of the box is 12.34.56.78 (for security purposes).

    My extension is 6125, I'm attempting to call 6128. The call is cut short, but still indicates connected on my handset.

    We have multiple teleworkers in the field, so this must work before we move forward.

    Thanks in advance.
     
  2. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,868
    Likes Received:
    304
    Well, this call went off to voicemail because the extension you were calling was not registered. 3CX sent a message and port listed, but got no reply. So it either can't get through, or, the IP/port is incorrect.

     
  3. SY

    SY Well-Known Member
    3CX Support

    Joined:
    Jan 26, 2007
    Messages:
    1,825
    Likes Received:
    2
    You need find a way to disable SIP ALG.
    PBX does not need to use STUN in the environment where static public IP is available on the border device(NAT/Firewall) and external ports are statictly forwarded to PBX host.You can disable usage of stun and specify which external IP should be used by PBX on the local network interface. You can find additional hints in the article
    http://www.3cx.com/blog/voip-howto/troubleshooting-direct-remote-extension/

    Thanks
    P.S. Please use code tag when post logs. Simply select text of the log in your message and press "Code" button at the top of the editing window
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. zzyzxx71

    Joined:
    Feb 17, 2012
    Messages:
    13
    Likes Received:
    0
    12.191.106.100 is the external IP which is NAT'd to the internal IP. I'm fairly confident this user (iPhone client) was indicating that it was "on hook" at the time.

    I've disabled the ALG, and verified that the STUN server option is disabled with the external IP entered as required.
     
  5. leejor

    leejor Well-Known Member

    Joined:
    Jan 22, 2008
    Messages:
    10,868
    Likes Received:
    304
    All 3CX "knows" is that it didn't get a reply. If you don't come up with anything else, (perhaps trying a different router?) You may want to make use of Wireshark, at various points along the way to figure out if the message is getting through to the set, or, if the set is not responding, or, if the response isn't getting back to 3CX
     
Thread Status:
Not open for further replies.