3cx Cloud - Fanvil X4 - "Waiting for STUN"

[Syssa]

Hello

I have running a 3cx instance on Azure and I am experiencing following problem:

When deploying remote STUN phones (Fanvil X4's). The phones get all the correct info/properties from the 3cx but they are stuck on "Waiting for remote STUN". When I logon to the web portal of the phone and click "Submit" within the "Line" Tab the phone magicly registers.

The default firmware running on the Fanvil X4 phones is rc2.3.2.4600.
I am facing the same issue when using following firmware:

• 2.4.0.5572
  
• 2.7.0.6130

How is this possible and how can I solve this?

Thanks in advance

Greetings

 

[phonemaster]

Hello

I have running a 3cx instance on Azure and I am experiencing following problem:

When deploying remote STUN phones (Fanvil X4's). The phones get all the correct info/properties from the 3cx but they are stuck on "Waiting for remote STUN". When I logon to the web portal of the phone and click "Submit" within the "Line" Tab the phone magicly registers.

The default firmware running on the Fanvil X4 phones is rc2.3.2.4600.
I am facing the same issue when using following firmware:

• 2.4.0.5572
  
• 2.7.0.6130

How is this possible and how can I solve this?

Thanks in advance

Greetings

Hi Syssa,
Never saw this type of issue during my installations (and believe me I did a lot ).
It sounds like some network issue. Probably, the connection between the phone and 3cx PBX is very slow.
The phone can't resolve the 3cx FQDN and get the STUN replies before and during the registration and stops there. After some time, it gets it and when you press Submit it registers.
Do you have a local DNS server? If so, try to add a record there (3cx FQDN to-> 3cx Public IP). This can decrease the timeout and solve your problem.

 

[Syssa]

Update:

When I test this with an Fanvil X3 the phone registers flawlessly. So there is definitely something with the phone/firmware versions.

 

[YiannisH_3CX]

Hello @Syssa

I tried to replicate your issue with a Fanvil X4 running firmware 2.4.0.5572 and i do not get this issue. I am also running the latest PBX version (15.5.15502.6) and the default template. Although i am not running a Azure instance i am running a Google instance.