It seems that little to no devices our there support the lr tag as it applies to record-route and route. What I have seen are two things: lack of proper parsing support of a single value token in the record-route/route headers, and lack of support of lr as a function. I'm not that concerned w/ little to no support for lr just yet, proxies/ua(s) don't have to understand lr, just parse it properly. However, I have seen many bugs w/ just proper parsing. It also seems that a syntax of lr=true has been implemented to get around these problems. Should this parameter string (lr=true) be recognized as needing lr route handling? Will this parameter string get added to the sip spec?
I would like to follow the general convention, but I cannot find much information on the matter. Thanks, -jasson _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
