IP Based SIP Trunk is not auto refreshing each time router reboot

[ECOM GROUP (Mauritius)]

Hello everyone,

I have a 3CX installed on OVH VPS, using a IP Based SIP Trunk via DDNS and it work well.
Each i restart my router in my local network, my ddns is up within second and no issue with this.
But i cannot make outdoing calls. But only when i click "Refresh Registration" in the management console" then i can start make call immediately.

This is very annoying for customer who have reboot their router. i noticed the re-register time out does not work for IP Based SIP Trunk. it only work for account based trunk.

Can someone help to find a solution.
Firewall check ok.

Port opened on local router is 5060, 5070, 5090, 5061, 9000-10999 and 80 as well for ddns.

Thanks.

 

[cobaltit]

IP authenticated trunks don't register. Your provider sends calls to an IP address and expects calls from an IP address. No registration attempt is made.

 

[ECOM GROUP (Mauritius)]

IP authenticated trunks don't register. Your provider sends calls to an IP address and expects calls from an IP address. No registration attempt is made.

Yes that is right. But the issue is each time i reboot my router, i cannot make calls, i have to manually refresh registration in 3cx so that it work.

 

[cobaltit]

So first perhaps you can clarify what role DynDNS plays in your SIP trunk configuration. I don't understand why this is needed.

 

[ECOM GROUP (Mauritius)]

So first perhaps you can clarify what role DynDNS plays in your SIP trunk configuration. I don't understand why this is needed.

My pbx is in the cloud. the IP my Telecom provided is a private/local ip on my network, the ONT SIP equipment is connected to my network switch and therefore i have forward it to a ddns so that my cloud 3cx can access it.

Why ddns, because my internet IP in my local network is dynamic

 

[cobaltit]

Ok, so I guess the question is why would you put your PBX in the cloud when your dialtone is local. That's just creating this problem. I have no idea if/when 3CX refreshes DNS lookup but the answer is to stop using a hosted 3CX.

 

[ECOM GROUP (Mauritius)]

Ok, so I guess the question is why would you put your PBX in the cloud when your dialtone is local. That's just creating this problem. I have no idea if/when 3CX refreshes DNS lookup but the answer is to stop using a hosted 3CX.

Cloud is more reliable from equipment, bandwidth etc.
Most system is coming to cloud nowadays. not all ISP provide SIP Line open to the internet.

I think there must be a solution before going for " setting up a vpn from cloud to local router"

 

[cobaltit]

You have several solutions:

• Get a static IP
• Setup a VPN

 

[ECOM GROUP (Mauritius)]

You have several solutions:

• Get a static IP
• Setup a VPN

I am aware of these solution, Since our major target is for SME/SME, i would prefer not to make the cost higher. Static IP is super expensive here.

 

[cobaltit]

Cloud is more reliable from equipment, bandwidth etc.

And while this is generally true, in your case it's not. For one, putting your PBX farther away from your dial tone is clearly causing reliability problems. And two, you are using MORE bandwidth this way, not less since you are carrying your PSTN traffic over the internet as well.

 

[3C Technology]

I have to agree with Cobaltit you are creating a lot of unnecessary points of failure/complexity.
So you have cloud PBX for reliability then you have sip trunk on premise? Kind of defeats the
objectives of a cloud based pbx. Where is you cloud PBX hosted ? And where is your SIP provider
based ?

 

[JohnS_3CX]

What ONT equipment? Is the provider giving you a GPON terminal that provides access to their SIP services?

Consider setting up a VPN so that there will be no IP changes or DDNS involved

You have to weigh that against the problems your current setup is causing your customer and decide what is best for them. You can make many things work, both in supported and unsupported 3CX scenarios, but ultimately if you want the service to be stable and not have to worry about power cycling or recovery from power outages and customer complaints then you will have to stick to a known-good tested and supported scenario.

 

[ECOM GROUP (Mauritius)]

What ONT equipment? Is the provider giving you a GPON terminal that provides access to their SIP services?

Consider setting up a VPN so that there will be no IP changes or DDNS involved

You have to weigh that against the problems your current setup is causing your customer and decide what is best for them. You can make many things work, both in supported and unsupported 3CX scenarios, but ultimately if you want the service to be stable and not have to worry about power cycling or recovery from power outages and customer complaints then you will have to stick to a known-good tested and supported scenario.

Hi John,
Thanks for your response, Telecom have installed a Huawei MA5675M where i can see an fiber optical cable is connected to it, then another device which is a Livebox Business LBB 240 where a cat 6 cable goes from the LBB240 wan port connect to the Huawei MA5675M. both device is without internet. they have provide only an IP for the SIP Line. the IP is only a private IP with same subnet of my local network.

I have then connect the LBB 240 to my network switch to be able to forward the IP via a DDNS.

it would be much better if 3cx could refresh the sip trunk automatically. for now, to set up a vpn,. the cheapest solution is having this https://www.tp-link.com/us/business-networking/vpn-router/tl-r600vpn/#specifications

 

[JohnS_3CX]

Hi,

Like the other members said, there are too many points of failure in this chain (even though when it works, it works).

I think what you, or the customer rather who pays the bill, should consider is whether they are willing to live with these restrictions or if they prefer a more stable service. Cloud is a very good solution but only when it makes sense to do so (ie. you are using an internet based trunk and an SBC at the phones site).

There is no way to prevent the specific issue because it relies on resolving a constantly changing IP in the current setup you have. After rebooting, things might not work as you expect especially if there are variables such as a changing IP. Hopefully your PBX is not also on a dynamic IP like the the office connection