17 Mar
2009
17 Mar
'09
6:15 p.m.
Nils Ohlmeier wrote:
Record-Route headers are inserted into the request, the INVITE in this
case, and the UAS is suppose to copy the Record-Route header from the
INVITE into the reply. Which it obviously fails to do.
In general a proxy like SER is not suppose to change/touch the reply ;-)
I seem to remember that there were quite legal cases where a proxy
messes with the Record-Route it added itself in the reply. Just can't
remember quite what it was.
If one doesn't need the ability of the rr module to store attributes in
the Record-Route header, one should get away with something like
append_to_reply("Record-Route: <XXX.XXX.XXX.XXX:5060;nat=yes>\r\n");
in this case.
Regards,
Martin