Ports / Trunk Status Registered (idle) no calls possible

[beuvema]

Ports / Trunk Status Registered (idle) no calls possible


Hi forum,

being new to the 3CX Phone System I hope of some support through the forum. I did some research on this forum but only found identical issues with no awnsers.

Here is my case:

about a day after the 3CX Phone System installation no calls from outside to inside and from the inside to the outside of the PBX can be made. Internal calls still work. During the first hours of installation I experienced no problems.

The 3CX Phone System v8.0.10824.716 is installed on a Windows 2003 SBS R2 SP2 Server without any issues.
In 3CX I created a VOIP Provider "VoipBuster" with these settings:

Provider Details
- SIP server hostname or IP - sip.voipbuster.com
- SIP server port - 5060
- Outbound proxy hostname or IP - sip.voipbuster.com
- Outbound proxy port (default is 5060) - 5060

Account Details
- External number - 3185xxxxxxx
- Authentication ID - VoipBuster accountname
- Authentication Password - VoipBuster Password

Simultaneous Calls
- Maximum Simultaneous Calls - 1

This configuration worked for about 24 hours then stopped. Stange thing is that the "Ports / Trunk Status" remains "Registered (idle)". It seems this status is not updated periodically.

I tested the installation on our own local server and on a remote server with different VoipBuster accounts. both dropped the lines after about a day,

Restarting the services or even the complete server does not solve the issue.

In one of the topics in this forum I read about similar problems that were solved by going to:

- VOIP Providers -> VoipBuster -> tab "Advanced"
- Registration Settings
- Which IP to use in 'Contact' field for registration: Specified IP -> Changed to my Static WAN IP

this did not solve the issue

Anyone with a clue how to solve this issue?

 

[beuvema]

Maybe the logging helps

10:52:42.565 [CM503020]: Normal call termination. Reason: Not available
10:52:42.565 [CM503016]: Call(1): Attempt to reach <sip:[email protected]> failed. Reason: Not Registered
10:52:42.565 [CM503016]: Call(1): Attempt to reach <sip:[email protected]> failed. Reason: Not Registered
10:52:42.565 [CM503017]: Call(1): Target is not registered: Out.069999999{rule=interlokaal}
10:52:42.503 [CM503010]: Making route(s) to <sip:[email protected]>
10:52:42.472 [CM505001]: Ext.10: Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:[email protected]:5060]
10:52:42.472 [CM503001]: Call(1): Incoming call from Ext.10 to <sip:[email protected]>
10:52:28.284 [EC200002]: Media server is connected: applicationt2k3001:0/MediaServer local:127.0.0.1:5482 remote:127.0.0.1:17537
10:52:23.612 [CM504001]: Ext.MakeCall: new contact is registered. Contact(s): [sip:[email protected]:40600;rinstance=f0ff83068d3f8dd0/MakeCall]
10:52:23.550 [CM504001]: Ext.IVRForward: new contact is registered. Contact(s): [sip:[email protected]:40600;rinstance=ce4451bd43ac524f/IVRForward]
10:52:23.503 [CM504001]: Ext.EndCall: new contact is registered. Contact(s): [sip:[email protected]:40600;rinstance=001d619c2bdcdce9/EndCall]
10:52:23.409 [CM504001]: Ext.99: new contact is registered. Contact(s): [sip:[email protected]:40600;rinstance=0d1314d4ddd24a11/99]
10:52:22.409 [CM504004]: Registration succeeded for: 10001@VoipBuster
10:52:21.909 [CM504003]: Sent registration request for 10001@VoipBuster
10:52:21.831 IP(s) added:[192.168.254.50]

 

[beuvema]

Firewall Checker results

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

<11:46:34>: Phase 1, checking servers connection, please wait...
<11:46:34>: Stun Checker service is reachable. Phase 1 check passed.
<11:46:34>: Phase 2a, Check Port Forwarding to UDP SIP port, please wait...
<11:46:39>: UDP SIP Port is set to 5060. Response received correctly with no translation. Phase 2a check passed.

<11:46:39>: Phase 2b. Check Port Forwarding to TCP SIP port, please wait...
<11:46:44>: TCP SIP Port is set to 5060. Response received correctly with no translation. Phase 2b check passed.

<11:46:44>: Phase 3. Check Port Forwarding to TCP Tunnel port, please wait...
<11:46:48>: TCP TUNNEL Port is set to 5090. Response received correctly with no translation. Phase 3 check passed.

<11:46:48>: Phase 4. Check Port Forwarding to RTP external port range, please wait...
<11:46:54>: UDP RTP Port 9000. Response received correctly with no translation. Phase 4-01 check passed.
<11:46:59>: UDP RTP Port 9001. Response received correctly with no translation. Phase 4-02 check passed.
<11:47:03>: UDP RTP Port 9002. Response received correctly with no translation. Phase 4-03 check passed.
<11:47:08>: UDP RTP Port 9003. Response received correctly with no translation. Phase 4-04 check passed.
<11:47:12>: UDP RTP Port 9004. Response received correctly with no translation. Phase 4-05 check passed.
<11:47:17>: UDP RTP Port 9005. Response received correctly with no translation. Phase 4-06 check passed.
<11:47:21>: UDP RTP Port 9006. Response received correctly with no translation. Phase 4-07 check passed.
<11:47:26>: UDP RTP Port 9007. Response received correctly with no translation. Phase 4-08 check passed.
<11:47:30>: UDP RTP Port 9008. Response received correctly with no translation. Phase 4-09 check passed.
<11:47:35>: UDP RTP Port 9009. Response received correctly with no translation. Phase 4-10 check passed.
<11:47:39>: UDP RTP Port 9010. Response received correctly with no translation. Phase 4-11 check passed.
<11:47:44>: UDP RTP Port 9011. Response received correctly with no translation. Phase 4-12 check passed.
<11:47:48>: UDP RTP Port 9012. Response received correctly with no translation. Phase 4-13 check passed.
<11:47:53>: UDP RTP Port 9013. Response received correctly with no translation. Phase 4-14 check passed.
<11:47:57>: UDP RTP Port 9014. Response received correctly with no translation. Phase 4-15 check passed.
<11:48:02>: UDP RTP Port 9015. Response received correctly with no translation. Phase 4-16 check passed.
<11:48:06>: UDP RTP Port 9016. Response received correctly with no translation. Phase 4-17 check passed.
<11:48:11>: UDP RTP Port 9017. Response received correctly with no translation. Phase 4-18 check passed.
<11:48:15>: UDP RTP Port 9018. Response received correctly with no translation. Phase 4-19 check passed.
<11:48:20>: UDP RTP Port 9019. Response received correctly with no translation. Phase 4-20 check passed.
<11:48:24>: UDP RTP Port 9020. Response received correctly with no translation. Phase 4-21 check passed.
<11:48:24>: UDP RTP Port 9021. NO RESPONSE received. Phase 4-22 check failed with ERRORS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
<11:48:29>: UDP RTP Port 9022. Response received correctly with no translation. Phase 4-23 check passed.
<11:48:33>: UDP RTP Port 9023. Response received correctly with no translation. Phase 4-24 check passed.
<11:48:38>: UDP RTP Port 9024. Response received correctly with no translation. Phase 4-25 check passed.
<11:48:42>: UDP RTP Port 9025. Response received correctly with no translation. Phase 4-26 check passed.
<11:48:47>: UDP RTP Port 9026. Response received correctly with no translation. Phase 4-27 check passed.
<11:48:51>: UDP RTP Port 9027. Response received correctly with no translation. Phase 4-28 check passed.
<11:48:56>: UDP RTP Port 9028. Response received correctly with no translation. Phase 4-29 check passed.
<11:49:00>: UDP RTP Port 9029. Response received correctly with no translation. Phase 4-30 check passed.
<11:49:05>: UDP RTP Port 9030. Response received correctly with no translation. Phase 4-31 check passed.
<11:49:09>: UDP RTP Port 9031. Response received correctly with no translation. Phase 4-32 check passed.
<11:49:09>: UDP RTP Port 9032. NO RESPONSE received. Phase 4-33 check failed with ERRORS. Some functionality will be LIMITED. For more information, please visit http://www.3cx.com/support/firewall-checker.html
<11:49:14>: UDP RTP Port 9033. Response received correctly with no translation. Phase 4-34 check passed.
<11:49:18>: UDP RTP Port 9034. Response received correctly with no translation. Phase 4-35 check passed.
<11:49:23>: UDP RTP Port 9035. Response received correctly with no translation. Phase 4-36 check passed.
<11:49:27>: UDP RTP Port 9036. Response received correctly with no translation. Phase 4-37 check passed.
<11:49:32>: UDP RTP Port 9037. Response received correctly with no translation. Phase 4-38 check passed.
<11:49:36>: UDP RTP Port 9038. Response received correctly with no translation. Phase 4-39 check passed.
<11:49:41>: UDP RTP Port 9039. Response received correctly with no translation. Phase 4-40 check passed.
<11:49:45>: UDP RTP Port 9040. Response received correctly with no translation. Phase 4-41 check passed.
<11:49:50>: UDP RTP Port 9041. Response received correctly with no translation. Phase 4-42 check passed.
<11:49:54>: UDP RTP Port 9042. Response received correctly with no translation. Phase 4-43 check passed.
<11:49:59>: UDP RTP Port 9043. Response received correctly with no translation. Phase 4-44 check passed.
<11:50:03>: UDP RTP Port 9044. Response received correctly with no translation. Phase 4-45 check passed.
<11:50:08>: UDP RTP Port 9045. Response received correctly with no translation. Phase 4-46 check passed.
<11:50:12>: UDP RTP Port 9046. Response received correctly with no translation. Phase 4-47 check passed.
<11:50:17>: UDP RTP Port 9047. Response received correctly with no translation. Phase 4-48 check passed.
<11:50:21>: UDP RTP Port 9048. Response received correctly with no translation. Phase 4-49 check passed.
<11:50:26>: UDP RTP Port 9049. Response received correctly with no translation. Phase 4-50 check passed.


Application exit code is 2

 

[mfm]

You should try and take your PBX stunless, according to the logs, there seems to be a registration process, and since you havent pasted in the registration retry details, its hard to say exactly why its faling.

Guide to turn off stun resolution:

http://www.3cx.com/blog/voip-howto/stun-resolution/