Solved 400 Missing Authorization header field after update to 18.0 Update 3 (Build 450)

[hakimy]

Hi!

After the update to 18.0 Update 3 (Build 450) both Trunks for the same provider get changed to unregistered with the following message:
Call or Registration to wilhelm.tel 1 has failed. sip:[email protected] replied: 400 Missing Authorization header field; from IP:213.209.115.117:5060

How can I fix this?
Edit: they stay registered for ~35 minutes, then go down with the message above and change to registered again after ~4 minutes

 

[YiannisH_3CX]

Hi @hakimy

Do you have the PBX set up to use a Dynamic IP address? If so please change it to static if possible and see if that resolves your issue.

 

[hakimy]

Okay. I will try this. Just saw the other thread with the same problem.

 

[YiannisH_3CX]

Let us know of the results

 

[hakimy]

Yes, this seems to fix the issue for now

 

[cedric79]

Hello,
We have the same issue since this morning (auto update @ 2AM).
We have switched the setup from Dynamic to static IP (we have a dynamic wan IP) but the issue is still the same.

 

[cedric79]

Hello,
We have the same issue since this morning (auto update @ 2AM).
We have switched the setup from Dynamic to static IP (we have a dynamic wan IP) but the issue is still the same.

It is ok since we have switched to static IP address.
What happens if our WAN ip address change?

Regards,

 

[YiannisH_3CX]

It is ok since we have switched to static IP address.
What happens if our WAN ip address change?

You will need to keep an eye our for that for now until we release the fix for this. Or if your IP changes frequently we can patch your system manually. We will need access to the OS though so if you want please send me a p.m.

 

[cedric79]

You will need to keep an eye our for that for now until we release the fix for this. Or if your IP changes frequently we can patch your system manually. We will need access to the OS though so if you want please send me a p.m.

Thanks for the reply.
Our IP should not change before some days.

 

[NickD_3CX]

Small update, we should be releasing a V18 U3 patch for this in a few days from now.
Until then if anyone else has the issue, please set your 3CX Servers to "Static" in Settings --> Network.

I will mark this as 'Solved'.