[ZenMasta]

Having trouble connecting remotely using 3cx phone.
In 3cx Console: listening port 5090
password is set.

I have created one extension
Extension: 120, under phone provisioning tab I have check the box marked to enable 3cx Tunnel

Firewall: PFSense
NAT TCP/UDP Port 5090
External: my wan ip
points to 192.168.13.144

RULE: allow tcp/udp 5090 to 192.168.13.144

When I try to connect with the 3cxphone it just says Not Connected. And I don't know if there is a log or anything to check.

I was able to connect previously before I upgraded to v10 and changed hardware. Besides the version change the only thing that changed was my internal ip which I have already accounted for.

I have even disabled windows firewall even though I don't believe I should have to. What am I missing?

[Vali_3CX]

Hi
In the main menu, click the Debug option to open the debug window - there is not any useful hint? Which 3CXphone version do you have (as shown in About) ?

[leejor]

And check the 3CX server log to see if the registration attempt is even reaching 3CX through your router.
You changed the local IP of 3CX in the 3CX phone too?

[ZenMasta]

Phone version 5.0.14900.0

I don't really remember doing anything since my last post to this topic. However as restarted the phone it actually connected. So yaay I guess.

[ghassan]

hello guys ,
i have same problem too . im using dyndns.org , i've tired from it and forward ports from 1~50000 and always its gives me authentication failed ,
i've think about another idea i've make my 3CX server as DMZ and its still have same problem ,, is there anybody can support us

[daver56]

I am having the same problem. I cannot connect from outside my local LAN. I have verified my DYNDNS address point to my home DSL IP address, I have used a remote port status checker and verified that 5060 and 5090 are both open. I have tried connecting using 3CX for IPhone and with 3CX VOIP Phone. Both work fine locally but both fail remote. I am testing this to be able to recomend it to a friend to purchase for his business. At this point I cannot recomend anything. HELP!

[eagle2]

Are you allowing connections outside the LAN to you 3CX server ? In version 10 you should allow them explicitly for each remote extension.

The problem with dyndns.org could be the amount of inquiries for resolving IP address. I would rather suggest using a router (at remote site), which could establish a VPN tunnel using dyndns to the main site with 3cx server.

regards

[willow]

I would try it without dyndns and see it it registers. I do beleive that in the 3cx you also need to have have the sip domain as the dyn dns as well. I have always learned that dyn dns and the 3cx sometimes do not play well together.