Solved Windows Users planning to Upgrade to 16.0.6.641 beware

[RichB]

I have only upgraded one instance from 16.0.5... to 16.0.6.641 but it appears to have re-introduced the DNS issue that was found in the initial release of 16.0.5. It causes issues creating outbound calls and it was only a problem for Windows users, Linux wasn't a problem.

 

[AWS2P]

can you give some details, what you found exactly?
have done update on all my pbxs including on premise windows one and not seen any problem

 

[RichB]

https://www.3cx.com/community/threa...nd-calls-since-16-5-update.72723/#post-326323

can you give some details, what you found exactly?
have done update on all my pbxs including on premise windows one and not seen any problem

https://www.3cx.com/community/threa...nd-calls-since-16-5-update.72723/#post-326323

 

[AWS2P]

haven't got this until now since pbxs are in.641

 

[RichB]

The excellent NickD_3CX suggested going into the SIP Trunk settings, Options tab and to change IP Mode to IPV4 which has fixed the issue for me.