Yealink T43U will not register via STUN when 3CX Windows app is registered, provisions just fine

[rely1]

Hi,

I have been struggling with provisioning BOTH 3cx APP, 3cx Android APP, and a T43U Yealink phone via STUN all on the same remote network.

The configuration for the extension Options I have unchecked "Block Remote phones using Stun", so that this is turned off for this extension.

My 3cx Server is self-hosted at Google Cloud Platform. The firewall test check passes on all expected ports. I have additonally opened UDP 5062 as a test for SIP. My understanding is that remote STUN phones must be registered on unique SIP/RTP ports?

The phone provisions after factory resetting the Yealink T43U and it asks for the username and password and provisions the extension properly. BUT it will not register if the Windows app is active on the same network.

I have the phone provisioning ports as follows on this extension:
Local SIP Port: 5060 (also tried 5062 UDP and opened this port on GCP firewall inbound)
Local RTP Port Start 14020
Local RTP Port End 14039

The RTP ports start and end on this extension is unique to my 3cx system and no other extension is configured with these RTP ports.

When the user launches the desktop 3CX windows APP then the phone registration fails after some time.
When we stop the 3cx Windows App at this remote user's location, the phone after reboot will register properly.
Once the user starts the 3cx Windows APP the phone will lose it's registration.

How should I set the Local SIP Port to avoid conflict?
When I tried to set it to 5062, still the Yealink phone would not register as long as the Windows 3cx app is registered.

When the user has the Windows 3cx app registered he can also use his Android 3cx app at the same time.

Please let me know how we can successfully register the Yealink T43U via STUN and use the Windows 3cx app and Android APP all registered at the remote location.

Thanks

 

[N_G]

Follow the guides and recommendations:

1. Switch to 3CX Hosted. From your post it seems you are still new to voip and why self host and make your life difficult.
2. Use the SBC to connect the Yealink. Remote STUN is not supported and error prone.

 

[rely1]

Follow the guides and recommendations:

1. Switch to 3CX Hosted. From your post it seems you are still new to voip and why self host and make your life difficult.
2. Use the SBC to connect the Yealink. Remote STUN is not supported and error prone.

We have other extension successfully running Stun. Have about 10 years of VoIP experience. Surprised to hear you say that Stun doesn’t work. We were considering a router phone running SBC.

 

[JohnS_3CX]

@rely1 We don't support STUN in 3CX hosted solutions because of its unreliable nature, something you are also experiencing right now.

This is why we created the 3CX SBC, and made great efforts to have some popular phones now work with the SBC embedded into their firmware, no extra hardware needed.

There is no guaranteed successful way for getting STUN to work - ever.

 

[Colorado VoIP]

Hi,

I have been struggling with provisioning BOTH 3cx APP, 3cx Android APP, and a T43U Yealink phone via STUN all on the same remote network.

The configuration for the extension Options I have unchecked "Block Remote phones using Stun", so that this is turned off for this extension.

My 3cx Server is self-hosted at Google Cloud Platform. The firewall test check passes on all expected ports. I have additonally opened UDP 5062 as a test for SIP. My understanding is that remote STUN phones must be registered on unique SIP/RTP ports?

The phone provisions after factory resetting the Yealink T43U and it asks for the username and password and provisions the extension properly. BUT it will not register if the Windows app is active on the same network.

I have the phone provisioning ports as follows on this extension:
Local SIP Port: 5060 (also tried 5062 UDP and opened this port on GCP firewall inbound)
Local RTP Port Start 14020
Local RTP Port End 14039

The RTP ports start and end on this extension is unique to my 3cx system and no other extension is configured with these RTP ports.

When the user launches the desktop 3CX windows APP then the phone registration fails after some time.
When we stop the 3cx Windows App at this remote user's location, the phone after reboot will register properly.
Once the user starts the 3cx Windows APP the phone will lose it's registration.

How should I set the Local SIP Port to avoid conflict?
When I tried to set it to 5062, still the Yealink phone would not register as long as the Windows 3cx app is registered.

When the user has the Windows 3cx app registered he can also use his Android 3cx app at the same time.

Please let me know how we can successfully register the Yealink T43U via STUN and use the Windows 3cx app and Android APP all registered at the remote location.

Thanks

you only need to open the standard 3cx ports. when you provision a STUN phone you just set a random port on the phones provisioning tab (don't have to open it up on the firewall). we start at 5070 for the clients that only have a couple phones. make sure your phone firmware is up to date and it should just link up. what we have found on the STUN clients, is they often have SIP ALG enabled on their network, once we can get them to take the time to shut that off, the phones will link up. if you've tried everything you can think of, check for SIP ALG on their network.