On 04/09/2013 11:59 AM, Juha Heinanen wrote:
because path-value starts with name-addr and my interpretation is that since there are <>s around this path header body:
Path: sip:192.98.102.10;transport=tcp;lr;received='sip:192.98.102.10:58156%3Btransport%3Dtcp'
solely consists of name-addr and does not include any rr-params. sip uri included in name-addr in turn cannot have ; and = in its param values.
I see, probably you are right. We've had base64 encode/decode on our todo list for some time already (for broken UAs, e.g. some of them cut everything after "'"), so maybe we should offer user a choice of proper escaping and base64 encoding here.
it turned out that save error had nothing to do with syntax of path header, but was due to a bug that i fixed.
-- juha