SIP trunk registration problem

Hi, I’m having a problem registering my trunks to the providers SBC. I got everything working several months, and this morning trunks are refusing to register. Investigating a little bit further I have found out that my FreePBX box doesn’t get valid SIP challenge from SIP trunk provider:

My FreePBX sends REGISTER SIP message to provider SBC.
Here, you can see that session Call-ID is [email protected][::1]

13:54:25.598086 IP (tos 0x60, ttl 64, id 22878, offset 0, flags [none], proto UDP (17), length 401) > SIP, length: 373
Via: SIP/2.0/UDP;branch=z9hG4bK5118cdda;rport
Max-Forwards: 70
From: sip:[email protected];tag=as5589aadc
To: sip:[email protected]
Call-ID: [email protected][::1]
User-Agent: FPBX-
Expires: 3600
Contact: sip:[email protected]:5060
Content-Length: 0

Then, SBC sends challenge, but with the wrong Call ID:
Call-ID: 06d11b204b8b2[email protected]

Here you can see postix acess2pbxt… added to original Call-ID:

13:54:25.606114 IP (tos 0x0, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 501) > SIP, length: 473
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP;branch=z9hG4bK5118cdda;rport=5060
From: sip:[email protected];tag=as5589aadc
To: sip:[email protected];tag=SDsuur399-5ryxhwictm
Call-ID: 06d11b204b8b2[email protected]
WWW-Authenticate: Digest realm=“1000”,nonce=“570b9071b2d5f63d6828c9ef73885934694d4074”,opaque=“5ab8b14f2208db1c06b89e49dd862508”,qop="auth"
Content-Length: 0

So, FreePBX gets SIP message with unknown Call ID and rejects the message:

chan_sip.c:9056 find_call: = Looking for Call ID: 218282ef1c4cf[email protected] (Checking To) --From tag as251ac89d --To-tag SDt04i799-fwhxhn6mk8
chan_sip.c:9224 find_call: That’s odd… Got a response on a call we don’t know about. Callid 218282ef1c4cf[email protected]
chan_sip.c:28779 handle_request_do: Invalid SIP message - rejected , no callid, len 463

My SIP provider claims that their configuration is intact, they have several other clients with the same configuration as mine, and everything works with no problems, and the problem is on my side.

Trunks doesn’t work whole day, I need to solve this as quickly as possible, but I’m missing ideas.
Call-ID should match, RFC says, I’m quite sure the problem is on their side but…

Any suggestion would be appreciated.


They are turning down your request. This usually means you’ve messed up the password or some other parameter in the connect or registration string.

It should be SUPER easy to call them and say “Hey, I’m get a 401 back from you guys on my SIP registration. Can you get me some more details.”

Did you notice that your Caller ID is using IPv6 when everything else in your transcript is using IPv4?

1 Like

I’m calling them whole day yesterday, and they just telling me that my asterisk doesn’t send reply to their challenge…

But, I didn’t noticed IPv6 address in Call ID. I disabled IPv6 in Linux and rebooted the machine, and the trunks are REGISTERED.

What can I say but, thank you cynjut, I appreciate your advice and help :wink: