2011/12/29 Iñaki Baz Castillo ibc@aliax.net:
In the other side, please check this SIP request:
OPTIONS sip:bob@domain.com SIP/2.0 Via: SIP/2.0/UDP 1.1.1.1;branch=qweqweqwe From: "Alice" sip:alice@domain.com;tag=tag1234 To: "Bob" sip:bob@domain.com Bad-Header( lalala sip:lalala@1.2.3.4 Call-id: qweqweqweqwe Cseq: 1234 OPTIONS Content-Length: 0
This request is *invalid* since the "Bad-Header" header is fully malformed (it's not a header in fact), so it becomes an invalid whole SIP message. But send this request to Kamailio and Kamailio will happily forward it. And maybe the UAS receiving it will just *drop* the request rather than replying 400 (since it's not a valid SIP request).
The original "header" causing the problem in my system was the following (number and IP replaced):
P-Asserted-Identity(<sip: XXXXXXXX@XXX.XXX.XXX.XXX>)
Cheers.