google cloud hosted 3cx with yealinks over wan w/ STUN?

[dandenson]

Anyone running a number of yealinks like this? No SBC, just STUN?

Do you have to do anything special? ie, set allow udp rules for the rtp ports?

 

[Marari]

If you're running 1 phone per location, it's no big deal. Other than manually setting the provisioning address, it should be fairly straight forward.

If you are using multiple phones at a single location, I strongly recommend using an SBC. A raspberry pi is plenty for up to 20 phones using 10 BLF's or less each.

If you're hell-bent and determined to use multiple phones at a single location via STUN, read this:

https://www.3cx.com/docs/manual/configuring-ip-phones/#h.ul2fzupi6t22/#h.9k3bh09gpbh3

Yes, you'll need to configure multiple ports for each remote extension.

I'm going to say "I told you so" now...

 

[cobaltit]

No, I don't have any installs using more than one phone using STUN. It's not worth the headache.

 

[dandenson]

I've been using yealinks remotely with asterisk for quite a while. They all share the same rtp range and have had no issues once sip alg has been disabled.

I see that when setting a phone to stun mode, it selects a small set of ports, usually 14000-14019 and identical for each phone. This isn't enough ports for more than one phone so I'd basically just set different ports for each phone. I really shouldn't need to port forward these to the phones just have the firewall allow related.

The first site I setup was with an SBC and I was having some trouble with calls ringing through. Right now I'm doing a VPN and running things as local and the phones just route to the pbx.

I don't have any single phone sites, usually 4-12 phones. The SBC adds a point of failure, as does the VPN really.

 

[Marari]

I don't have any single phone sites, usually 4-12 phones. The SBC adds a point of failure, as does the VPN really.

Best of luck,

Your answer can be found in here:

https://www.3cx.com/docs/manual/configuring-ip-phones/#h.ul2fzupi6t22

and here:

https://www.3cx.com/docs/manual/configuring-ip-phones/#h.ul2fzupi6t22/#h.9k3bh09gpbh3

 

[dandenson]

Link #2 seems to make it clear.

 

[vectra]

SBC can be point of failure and I'm not using it. I have many customers with up to 50-60 phones in stun mode under one location. You have to setup unique SIP port for each phone (Ext 101=5101, ext 102=5102, etc...) and unique range of rtp ports (ext 101=14000-14019, ext102=14020-14039, etc...). Also, you have to check "PBX delivery audio" under each extension, otherwise you will not have audio when extension calling another extension under same LAN.I have 25 BLF on each phone and if you have good internet connection and good firewall with SIP alg disabled. I'm using ZYXEL USG series firewalls and those routers are capable to do NAT conning properly. Other possibilities to create VPN tunnel between PBX hosted on google (IPSEC tunnel) and your firewall then you not going to have any issues with phones.

 

[leejor]

SBC can be point of failure and I'm not using it.

Well...anything can be a point of failure. Modem, router (both ends), 3CX server, plug in power supply, Hard drive, your ISP, the list goes on and on. The brakes on your car might fail today too, does that mean you'll take the bus? It is all a mater of risk, and the odds of failure.

If the way you have it set up , works for you, and the extra bandwidth back through the PBX for every call, isn't an issue, then carry on. But please don't justify not using an SBC simply because it may fail at some point. So can any other link in the chain.