28 Dec
2011
28 Dec
'11
1:33 p.m.
Iñaki Baz Castillo writes:
Juha, the wrong header I meant is not a wrong
P-Asserted-Identity, but
a malformed text that makes *all* the SIP message invalid. So a proxy
or server receiving it can just *drop* the request (the same Kamailio
does if the Request URI contains a falmormed URI).
So there is nothing to fix in the GW. It's behaving 100% correctly.
i'm lost. why is your sip proxy forwarding a sip request that is
totally (not just one header) malformed? and why is your sip proxy able
to forward such a request when your uas is not able to respond to it?
any how is this all correct based on rfc3261?
-- juha