Snom D715 : stunserver fqdn:5060 is not answering

[Arnaud PENSU]

bonjour,
En 2 mois voici 2 D715 qui me posent problème.
j'ai résolu le premier cas après 2 reset usine.
Mais sur ce nouveau cas, j'ai besoin de comprendre pour être sûr de ne pas passer les prochains mois à reseter tous les D715 dans la nature...

La topologie :
Serveur 3CX v16.0.7.1078 PRO sur cloud - 2 IP Phone en Stun Snom D715 Fw 10.1.54.16 (pas de maj à priori)
Réseau du client : routeur et switch Ubiquiti Unifi - Vlan voix (utilisé par lldp-med)

Les deux extensions et téléphones sont configurés de de façon rigoureusement identique, ainsi que le port du switch sur lequel ils sont connecté.
et vous me voyez venir, un téléphone fonctionne parfaitement, l'autre fait des siennes depuis ce week-end.

j'ai appliqué un factory reset sur le téléphone, je vois bien passer la phase de provisionning, le téléphone applique tous les paramètres mais à la fin, dans le Syslog du téléphone j'ai ca :

[WARN ] SIP: stunserver fqdn.du3cx.fr:5060 is not answering, will try again in 300 seconds (see setting stun_binding_interval)

j'ai comparé les paramètres des deux téléphones, la seule différence visible est l'heure système, alors que les deux semblent quand même à l'heure... ?

system_time=1612361535 pour celui qui fonctionne
system_time=1613989157 pour le récalcitrant.

j'en perds mon latin.
j'ai rebooté le serveur - idem

je viens de faire la MAJ : 16.0.8.9 => idem.

j'ai désactivé LLDP-MED sur le switch, et donc forcé les paramètres VLAN dans le provisionning des téléphones => idem.

si quelqu'un a déjà vu ca, une piste, une iée, une corde....

 

[JohnS_3CX]

Hi Arnaud,

We kindly ask that you post in English on the international forum.

Alternatively, you can also try our French forum
https://www.3cx.fr/forum/

 

[Arnaud PENSU]

yes, sorry it s a mistake, i thought it was the french forum.
i'll try to translate because my problem persist.

 

[Arne Larsen]

why dont you use stun.3cx.com or stun1.3cx.com
Port is 3478

 

[Arnaud PENSU]

don t know this method, STUN Server url is provided to the phone directly by 3CX PBX Server.
the other phone on same site same switch have no problem.
the customer use 3VC since September without any issue.

 

[JohnS_3CX]

HI Arnaud,

STUN needs a lot of things to go right before it works as intended.

You could also consider SBC, this removes the need to deal with STUN issues altogether, and makes life much easier. This is our recommended solution for remote phones.

 

[Arnaud PENSU]

hi.
i've switch the phone by a new One, exact same config and it s ok !!!!!!!

i've connected the 'strange' one into my Lan .. and it's connected !!!!!.

So, so there seems to be a problem with the network. what i don't explain is this site is in service since many months...

i'll take another look at your Stun documents, maybe i ve missed something ... all my customers uses my Cloud standards, so they are all in STUN with SNOMs...

 

[Arnaud PENSU]

HI Arnaud,

STUN needs a lot of things to go right before it works as intended.

You could also consider SBC, this removes the need to deal with STUN issues altogether, and makes life much easier. This is our recommended solution for remote phones.

i'm agree witth SBC for more users but for two, i'm not. the SBC represents an on-site SPOF, and it doesn't really save deployment time for 2 users in my opinion.

 

[Arnaud PENSU]

Well ... unfortunatly, everthing is configured exactly has it should be :
- PBX firewall check is ok, it has a fixed public ip, fqdn is well resolved.
- "Disallow use of extension..." is obviously disabled, and "Pbx deliver Audio" is checked.
- IP Phone have Fixed ip by DHCP reservation
- SIP and RTP ports are uniques for both ip phones, and correctly forwarded from the firewall (at least, correctly configured)
- IP Phone are provisionned by the automatic method, wich work very well, the phone downloads its configuration well as we can see in the phone logs.
- SIP Alg is disabled on the firewall
....

so, at this time, no progress, I still haven't been able to validate the problem part.

i have at least 2-3 other customers with exact same configuration : PBX, Network infrastructure, IP Phones ....

 

[JohnS_3CX]

[WARN ] SIP: stunserver fqdn.du3cx.fr:5060 is not answering, will try again in 300 seconds (see setting stun_binding_interval)

You said you get this warning, but Just to be clear, what is the real issue the phone facing?

- No Registration?
- Registration but no calls?

Or does it work OK and you are just curious why the message appears?

 

[Arnaud PENSU]

You said you get this warning, but Just to be clear, what is the real issue the phone facing?

- No Registration?
- Registration but no calls?

Or does it work OK and you are just curious why the message appears?

No registration.
another ip phone with same config is ok.
This ip phone on another site is ok ......

 

[JohnS_3CX]

If we assume that the phone is ok, and it did work fine from another network, then the most likely thing that remains is the network at the problematic site.

Make sure that the firewall settings are indeed correct, and that each phone has its own unique sip port forwarded. Don't use 5060 just in case something blocks it.

Maybe restart the firewall too, because sometimes you might enter the correct details but they will not be applied while the firewall is still running.