Trunk OpenIP impossible to register V16.5

[AWS2P]

Hi,
using supported sip provider Openip, randomly I get on different W10 pbxs on premise, trunk become in unregistred state alone.
For now my pbx has lost his registration at 4.49:33 AM and PBX never sent any new attempt to sip provider since this time.
Got a mail notification from PBX



Trunk sip is from 3CX template, and pbx is latest version 16 SP5 but this random behavior was existing before.

So in trunk sip template , registration is set from DNS name (voip.myopenip.fr) . When this failure occurs , it's impossible to refresh registration, a click on refresh registration seems to do absolutely nothing. Date and time doesn't refresh on time you click on it. SIP provider side receive nothing.

In same time, have a beronet analog gateway used as trunk and even gateway is registred green, it's impossible to dial out. Got a 503 error from 3CX each try to dial out, message like , you need to ask to admin......
Of course rules are done properly to be used by gateway and port on gateway was free.


The only way to register SIP trunk is to edit settings and change domain name and replace with IP 94.143.87.216. SIP registration instantly reach sip provider and trunk passes green.
A nslookup on sip provider domain name is resolved on PBX (this to exclude a DNS resolution problem)

This behavior is not new but never been fixed since a while between 3CX and OpenIp, it looks like a bug on 3cx side IMO, do you have any infos for this behavior?
is there any investigations on this ?

 

[ESP_Paul]

Looks like a few other people are having this issue with the latest 3cx build..
https://www.3cx.com/community/threa...lving-since-updating-to-16-5-yesterday.72721/

 

[AWS2P]

Yes seems similar problem , but this behavior is not new between 3CX and french sip trunk provider OpenIp

 

[dmayer]

It's more than likely not a specific provider issue but some sort of DNS bug inside of 3CX itself.

 

[YiannisH_3CX]

Hi @aws2p

Can you please send me a p.m. so we can look into the issue by gathering some data?

 

[AWS2P]

On my side this problem is occuring only on windows PBXs on premise. Others using Cloud Debian are not impacted.

 

[AWS2P]

Perhaps my thread could be merged with https://www.3cx.com/community/threa...lving-since-updating-to-16-5-yesterday.72721/
it seems to be same problem

 

[StefanW]

@aws2p

did you speak with @YiannisH_3CX via Private Message?

 

[NickD_3CX]

Perhaps my thread could be merged with https://www.3cx.com/community/threa...lving-since-updating-to-16-5-yesterday.72721/
it seems to be same problem

Yes, I think that is best.

For this reason I'll be locking this thread and you can continue on the other post.

Also as Stefan suggested, please send a PM to @YiannisH_3CX and myself to see what more we can do and find out.