Forum Discussion

Aspirant

May 09, 2016

3CX Phone Server, Secondary Addresses and PortForwarding

Hi, all- a small quandry. I am attempting to set up a 3CX phone server for a customer. The WAN's primary IP is already established at xx0.xx0.xx0.241 255.255.255.248. The client has a few more IPs at...

Security

bearbeatz

Aspirant

May 10, 2016

No apologies necessary. Am grateful for the sounding board, Dane.

So, I'll try to submit a bit more info:

Firmware Version: 4.3.1-22

So, I have LAN WAN rules shaped for both outbound and inbound traffic.

A sample Inbound and Outbound row using one Service. In this case, TCP port 5090 for the 3CX Tunnel-->

Inbound configuration:

1. Service Name: 3cxtunnelT

2. Filter: ALLOW always

3. LAN Users: 192.168.4.13 (Phone Server)

4. LAN Users: [empty]

5. WAN Users: Any

6. QOS Profile: NONE

7. Destination: xxx.xxx.xxx.242 (Secondary IP assigned to WAN1 [with assigned primary xxx.xxx.xxx.241])

8. Bandwidth Profile: NONE

9. Log: Never

Outbound configuration:

1. Service Name: 3cxtunnelT

2. Filter: ALLOW always

3. LAN Users: 192.168.4.13

4. WAN Users: xxx.xxx.xxx.241-xxx.xxx.xxx.242

5. QOS Profile: NONE

6. Bandwidth Profile: NONE

7. Log: Never

*8. NAT IP: xxx.xxx.xxx.242 (WAN1)

I run the 3CX Phone Server FW Checker and this is what transpires...

Testing SIP Port 5060 using STUN server: stun.3cx.com:3478
Resolving STUN server stun.3cx.com ... Resolved to: [198.50.247.220]
[Test1] Reachability test ... Resolved Public IP: 96.95.157.241:5060
STUN server stun.3cx.com has second address 198.50.247.219:3479
[Test2] One on One Port Forwarding ... FAILED.
No response received or port mapping is closed. Firewall check failed. This configuration is not supported.

Note: The 3CX Phone Server is pretty simple with the networking options. configured for the .242 as the Static Public IP and the 192.168.4.13 as the selected NIC. DNS yields correct name server lookup and address, too...

Regards,

bearbeatz

Aspirant

May 10, 2016

oops. #3 in Inbound should be titled "LAN Server IP Address"...

DaneA
NETGEAR Employee Retired
May 11, 2016
Hi bearbeatz,

For us to check if the secondary WAN IP Address works, why not try to swap the primary WAN IP Address and secondary WAN IP Address. Make the .242 as the primary WAN IP Address then make the .241 as the secondary WAN IP Address on the SRX5308. As well as edit the Inbound and Outbound rules in the SRX5308 and the settings on the 3CX phone server to use the .241 as the WAN IP Address for the meantime.

If ever still won't work, kindly try to update the firmware of the SRX5308 to the latest version 4.3.3-6. Make sure to perform a factory reset on the SRX5308 after a successful firmware update then reconfigure the setting from scratch. Then, check if same problem occurs. Here is the link where to download the latest firmware v4.3.3-6.

Regards,

DaneA
NETGEAR Community Team
DaneA
NETGEAR Employee Retired
May 15, 2016
Hi bearbeatz,

Were you able to swap the WAN IP Addresses?

Did you update the firmware to the latest version then did a factory reset and reconfigured from scratch?

Regards,

DaneA

NETGEAR Community Team
JohnRo
NETGEAR Employee Retired
May 18, 2016
Hello bearbeatz,

We’d greatly appreciate hearing your feedback letting us know if the information we provided has helped resolve your issue or if you need further assistance.
If your issue is now resolved we encourage you to mark the appropriate reply as the “Accepted Solution” so others can be confident in benefiting from the solution. The Netgear community looks forward to hearing from you and being a helpful resource in the future!

Thanks,