Solved 408 Request Timeout/REGISTER from local

[Nils]

Hi,

since yesterday one of our SIP-Trunks cannot register.
I don't understand, why the 3CX is getting Timeouts, because the provider send a response to our register request.

I tried the following steps to resolve this issue:
- DNS works
- Provider said everything on there side is normal
- Restart the whole Server
- Set the credentials again
- Recreate the SIP Trunk in console
- Checked firewall logs if something is blocked

Maybe someone have another tip to lock at?

(It's a generic trunk)

Message in 3CX Console:
[CM504005]: Registration failed for: Lc:10002(@(Villach) Generic SIP Trunk[<sip:u+************@trunk.innofon.at:5160>]); Cause: Cause: 408 Request Timeout/REGISTER from local

Trace:
REGISTER sip:trunk.innofon.at:5160 SIP/2.0
Via: SIP/2.0/UDP ************:5060;branch=z9hG4bK-524287-1---117cdf38bb2e796e;rport
Max-Forwards: 70
Contact: <sip:u+************@************:5060;rinstance=d569dc1a4242a0d6>
To: "+************"<sip:u+************@trunk.innofon.at:5160>
From: "+************"<sip:u+************@trunk.innofon.at:5160>;tag=9d341b7d
Call-ID: KevN9MnhVtT4qo89mkfPqw..
CSeq: 1 REGISTER
Expires: 290
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE
Supported: replaces, timer
User-Agent: 3CXPhoneSystem 15.5.13103.5 (11793)
Content-Length: 0

SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP ************:5060;branch=z9hG4bK-524287-1---117cdf38bb2e796e;received=80.228.9.44;rport=5060
From: "+************"<sip:u+************@trunk.innofon.at:5160>;tag=9d341b7d
To: "+************"<sip:u+************@trunk.innofon.at:5160>;tag=as0b3a9a12
Call-ID: KevN9MnhVtT4qo89mkfPqw..
CSeq: 1 REGISTER
Server: InnoSIP-trunk
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="app.innofon.at", nonce="3c59c4ca"
Content-Length: 0

REGISTER sip:trunk.innofon.at:5160 SIP/2.0
Via: SIP/2.0/UDP ************:5060;branch=z9hG4bK-524287-1---117cdf38bb2e796e;rport
Max-Forwards: 70
Contact: <sip:u+************@************:5060;rinstance=d569dc1a4242a0d6>
To: "+************"<sip:u+************@trunk.innofon.at:5160>
From: "+************"<sip:u+************@trunk.innofon.at:5160>;tag=9d341b7d
Call-ID: KevN9MnhVtT4qo89mkfPqw..
CSeq: 1 REGISTER
Expires: 290
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REGISTER, SUBSCRIBE, NOTIFY, REFER, INFO, MESSAGE, UPDATE
Supported: replaces, timer
User-Agent: 3CXPhoneSystem 15.5.13103.5 (11793)
Content-Length: 0

SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP ************:5060;branch=z9hG4bK-524287-1---117cdf38bb2e796e;received=************;rport=5060
From: "+************"<sip:u+************@trunk.innofon.at:5160>;tag=9d341b7d
To: "+************"<sip:u+************@trunk.innofon.at:5160>;tag=as0b3a9a12
Call-ID: KevN9MnhVtT4qo89mkfPqw..
CSeq: 1 REGISTER
Server: InnoSIP-trunk
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH
Supported: replaces, timer
WWW-Authenticate: Digest algorithm=MD5, realm="app.innofon.at", nonce="3c59c4ca"
Content-Length: 0


Thanks in advanced
Regards
Nils

 

[eddv123]

FYI in a standard SIP situation a 401 Unauthorized message is a normal response when registering.

You will get a response back stating 401 Unauthorized as this is the registrar requesting authorization credentials from the device registering. The registration information is then resent back in another register message which will then receive a 200 OK back.

You do not seem to be getting this 200 OK so I would check the credentials you are sending. Also where this does seem to be a Registration based SIP trunk please confirm this.

 

[YiannisH_3CX]

Hello @Nils

As eddv123 mentioned the 401 response from the provider is normal, what is not normal in the above log is that the PBX does not send the Authorisation details in the response.
This can happen for a few reasons. The first is that the providers IP is blacklisted in the IP blacklist of the PBX found on the dashboard. The other reason could be the 401 message from the provider is malformed so the PBX ignores it but we cannot see this through the logs.
Is the providers port 5160?

 

[Nils]

Wow, that was a easy one. Thanks for the tip with the ip blacklist.
For some reason it got blocked automatically because of to many failed authentifications.

Thanks a lot!

 

[YiannisH_3CX]

Glad to see the issue has been resolved. You could add the providers IP to the whitelist to prevent this from happening again.