Trey,
As I mentioned in an earlier post, we don’t use an internal Asterix box with SIP trunking. We use independent IP phone handsets connected directly to the trunking provider.
I must not understand the difference between our scenarios.
Any news on this voip issue?
We also suffer from long delays before the sip phones reauthenticate and we need to power them off and on after a disconnect
+1 - this would be a big help.
has anything been added to this topic? any feature set to Peplink that helps solve this issue with registration?
I personally don’t have this problem even with multiple WANs, apparently because we operate an Asterisk server on our LAN. For those of you who operate SIP handsets connected to an in-the-cloud server, this sounds like an ideal application for a remote Fusion Hub. You could go Fusion VPN to Fusion Hub provider, and then go from there on a reliable single IP to the SIP provider. That would likely add a bit to latency which is not a good thing for VoIP but would be worth a try if your local WANs go down frequently.
The ultimate configuration would be a SIP provider who maintains Fusion Hub at its data center. Are there any? SIP providers are an extremely competitive business. I bet if Peplink’s sales department made the case and some customers raised their hand, you would get a few providers to implement it. In particular I expect that Vitelity could be talked into it.
1 Like
That’s exactly what we are doing right now in our office. We have a Balance 305 with 2 WAN connections, then in our ISP data centre on vSphere we have FusionHub with our 3CX PBX. The latency from us to FusionHub is 1-2ms on the fibre and about 8-12 on average on the cable. I didn’t want to have our PBX in the cloud as I don’t like adding an extra hop, but since traffic routes through SpeedFusion for hot failover anyway I figure it adds nothing really by having the phone system in the DC with FusionHub. It works great, as then if a WAN link fails there’s no interruption on the calls at all. I’m also able to authenticate via Static IP even though our office has only dynamic IP addresses, since all voice traffic comes through FusionHub’s public IP.
Our SIP provider isn’t the same as our ISP but their equipment is in the same datacentre, so pinging our SIP provider from FusionHub is around 2-3ms.
3 Likes
+1 This would be a huge help for us!
We operate Fusion Hub in all 3 of our geo-redundant data centers for VoIP run off of FreeSwitch and it runs flawlessly. Just got done testing a few months back. Really cool stuff and no insane costs or not truly direct shots to data centers like most other SD-WAN providers. Thought I would share just to show that it is successfully spun up in live production environment.
1 Like