[reSIProcate] Request with non unique tid

["Alexander Altshuler" <alt@xxxxxxxxx>]

Hi All

I have SIP client which generate (sometimes) non unique transaction id
(branch parameter within Via header).
I know it is wrong behavior.
My resip based proxy respond for this request with previously sent response
of first transaction.
Nothing extremely bad, but I think if stack will respond with 400 Bad
Request it will better.

What do you think?

Best regards,
Alex

1. SIP client ->proxy
REGISTER sip:silicatvalley.home SIP/2.0
Via: SIP/2.0/UDP 192.168.0.2:24594;rport=24594;branch=z9hG4bK29002348
Max-Forwards: 70
Contact: <sip:539606@xxxxxxxxxxx:24594>
To: "alt" <sip:539606@xxxxxxxxxxxxxxxxxx>
From: "alt" <sip:539606@xxxxxxxxxxxxxxxxxx>;tag=5e29db05
Call-ID: 60091a0f1f4d615bd775353c8c37286b@xxxxxxxxxxx
CSeq: 2 REGISTER
Expires: 3600
Proxy-Authorization: Digest username="539606", realm="silicatvalley.home",
nonce="4180625810:6cf32021c97deb68fd41142b2f92bd32",
response="2e65d830ec0c57f14bcd618dad8aaee6", uri="sip:silicatvalley.home",
algorithm=MD5
User-Agent: SIP eyeP Phone (Build: EMPhoneSIP W32 5.05.25 EM)
Allow-Events: presence
Content-Length: 0

2. Proxy -> client
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.2:24594;rport=24594;branch=z9hG4bK29002348
Contact: <sip:539606@xxxxxxxxxxx:24594>;expires=3600
To: "alt"<sip:539606@xxxxxxxxxxxxxxxxxx>;tag=7248df0f
From: "alt"<sip:539606@xxxxxxxxxxxxxxxxxx>;tag=5e29db05
Call-ID: 60091a0f1f4d615bd775353c8c37286b@xxxxxxxxxxx
CSeq: 2 REGISTER
Content-Length: 0

3. Client -> proxy
SUBSCRIBE sip:520410@xxxxxxxxxxxxxxxxxx;user=phone SIP/2.0
Via: SIP/2.0/UDP 192.168.0.2:24594;rport=24594;branch=z9hG4bK29002348
Max-Forwards: 70
Contact: <sip:520410@xxxxxxxxxxx:24594>
To: <sip:520410@xxxxxxxxxxxxxxxxxx;user=phone>
From: "alt" <sip:539606@xxxxxxxxxxxxxxxxxx>;tag=7d7b5114
Call-ID: 335c613e4a1e2648f916bd096a066779@xxxxxxxxxxx
CSeq: 3 SUBSCRIBE
Accept: application/xpidf+xml
Proxy-Authorization: Digest username="539606", realm="silicatvalley.home",
nonce="4180625810:6cf32021c97deb68fd41142b2f92bd32",
response="beed24dcfedd006c1df9108d9df2b6c5", qop=auth,
uri="sip:520410@xxxxxxxxxxxxxxxxxx;user=phone",
cnonce="be188467e14a6c3dd62cae725269905f", nc=00000001, algorithm=MD5
User-Agent: SIP eyeP Phone (Build: EMPhoneSIP W32 5.05.25 EM)
Event: presence
Content-Length: 0

4. Proxy -> client
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.0.2:24594;rport=24594;branch=z9hG4bK29002348
Contact: <sip:539606@xxxxxxxxxxx:24594>;expires=3600 
To: "alt"<sip:539606@xxxxxxxxxxxxxxxxxx>;tag=7248df0f 
From: "alt"<sip:539606@xxxxxxxxxxxxxxxxxx>;tag=5e29db05 
Call-ID: 60091a0f1f4d615bd775353c8c37286b@xxxxxxxxxxx 
CSeq: 2 REGISTER Content-Length: 0