After Upgrading to V16 showing several duplicate extensions under "Phones"

[Erik Nathe]

Hoping someone has a quick fix for me here. After updating to V16 we have several Yealink phones that are duplicated under "Phones" of the 3cx console. Also each of the ones that has a duplicate is unable to make or receive phone calls... Our 3cx instance is hosted on Google Cloud.

I have tried rebooting, re-provisioning and even deleted the whole extension and then imported it back in. As soon as I set it up with the phone it duplicates again. Any help would be greatly appreciated!

 

[JohnS_3CX]

Hi Erik,

How are the phones connected to the PBX? Are they on STUN ?

 

[Erik Nathe]

Very sorry, forgot to include that. They are connected via STUN.

 

[JohnS_3CX]

Ok please check your extensions one by one, and ensure there are no overlapping ports between them:



These must be different for each deskphone

 

[Erik Nathe]

Just the local SIP Port of Phone or all three?

 

[Saqqara]

Info on setting up stun phone - https://www.3cx.com/community/threa...etgear-nighthawk-x4s-d7800.54620/#post-225296

 

[Erik Nathe]

It looks like the users are able to make and receive phone calls now, though the console is still showing duplicates. I am also unable to send commands to the phones from the console, like "Reboot" or "reprovision" I have to have someone onsite physically unplug the phone... seems to only be an issue with the yealinks.

 

[JohnS_3CX]

All 3 actually. The local SIP port, if the same across many devices, will cause duplicates.

The RTP ports (20 ports per phone as you see in the screenshot) must also be different so that one phone does not end up with the audio from another phone.

 

[JohnS_3CX]

In addition, at the phones site, the firewall must be configured to forward the ports on each phones in order to avoid audio and registration issues.

If you more than a couple of phones, you will greatly benefit by installing an SBC. That should make port management unnecessary (SBC uses a tunnel for traffic), and also make provisioning and management a bit easier.

 

[AWS2P]

Are your phones with LAN STATIC IP ?

 

[Erik Nathe]

I was interested in SBC as I saw it in a few other posts. Though I did not understand how to install it for our needs... We do not have a server onsite at that location as they are a small remote site.. They come in over a Site to Site VPN. So do we install SBC on our local server, one the 3cx cloud server, or does it need to be installed at their local site?

 

[JohnS_3CX]

If you have site to site VPN then the phones will appear as local phones and should be set up as "Local".

In your scenario, neither STUN nor SBC is necessary then.

Are the phones on the same IP network effectively as the PBX?

 

[Erik Nathe]

No the PBX is hosted on a Google Cloud server

 

[AWS2P]

So where is VPN ?

 

[Erik Nathe]

The VPN is from our remote site to our main site... to be able to access our network. Google Cloud hosted 3CX does not require a VPN to access.

 

[AWS2P]

For now on main and remote site all your phones are STUN mode ?
Globally how many phones do you have connected to PBX ?

As you surely have more than 2 or 3 phones you should add an SBC on main site, remote site is VPN so phones are seen in same LAN as main site.

 

[Erik Nathe]

We have about 40 phones between the two sites.

Understood. I will look into installing SBC at our main site.

Thank you!

 

[AWS2P]

You can use one or 2 SBC's , one on each site and connect phones from site to each.
it can be a hardware redondancy, if one dies other can handle phones

 

[JohnS_3CX]

You also have the option of installing a Raspberry Pi 3B+ as an SBC for a more cost effective solution
https://www.3cx.com/docs/3cx-tunnel-session-border-controller/

• Raspbian Linux on the latest Raspberry Pi (3B+ model), for up to 30 phones and a maximum of 10 BLF keys per device.
• Windows and Debian Linux on x64 hardware, supporting more than 30 phones.