SIP trunk registration problem

@vmiro wrote:

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 06d11b204b8b2b3f06daa01d1beb6a63@[::1]

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

Then, SBC sends challenge, but with the wrong Call ID:
Call-ID: 06d11b204b8b2b3f06daa01d1beb6a63-acess2pbxt-mih67c0fe2iggbdf50i9spostnu5us55@2.2.2.2

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)
10.0.0.5.sip > 10.0.0.60.sip: SIP, length: 473
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.0.0.60:5060;branch=z9hG4bK5118cdda;rport=5060
From: ;tag=as5589aadc
To: ;tag=SDsuur399-5ryxhwictm
Call-ID: 06d11b204b8b2b3f06daa01d1beb6a63-acess2pbxt-mih67c0fe2iggbdf50i9spostnu5us55@2.2.2.2
CSeq: 217 REGISTER
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: 218282ef1c4cf59b50e404d47ab07c26-acess2pbxt-mih67c0fe2iggbdf50i9spostnu5us55@2.2.2.2 (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 218282ef1c4cf59b50e404d47ab07c26-acess2pbxt-mih67c0fe2iggbdf50i9spostnu5us55@2.2.2.2
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.
Thanks

Posts: 3

Participants: 2

Read full topic