1 Jun
2004
1 Jun
'04
1:48 p.m.
Hi,
It seems SER doesn't parse a route header like this:
Route: sip:5555@10.2.2.2;lr=on;ftag=10af7dc2db05
because it isn't enclosed with < >. Is this behavior correct, according the
RFC3261?
Debug output:
15(6201) parse_nameaddr(): No < found
15(6201) parse_rr(): Error while parsing name-addr
15(6201) find_first_route(): Error while parsing Route HF
15(6201) loose_route(): There is no Route HF
Best regards