Hi Benny, I'm trying to meet a 3rd party equipment spec which is prescriptive as to the boundary string. To be honest, I haven't connected to the equipment yet (I'm just running unit tests against the spec). When I get a chance to connect to the equipment, ill get back to you to see if the escaped version is acceptable. Thanks again, Steve -----Original Message----- From: pjsip-bounces@xxxxxxxxxxxxxxx [mailto:pjsip-bounces at lists.pjsip.org] On Behalf Of Benny Prijono Sent: Thursday, 6 October 2011 12:45 PM To: pjsip list Subject: Re: Bug: Quoted boundary string in outgoing multipartmessage On Thu, Oct 6, 2011 at 5:15 AM, Steve King <sking at zetron.com> wrote: > Hi Benny, > > Thanks for the response, > > The only issue is when a 3rd party manufacturer *needs* the form: > ;param="the value" > > This form is currently not possible in PJSIP without setting value to "\"the value\"", and then in this case the boundary string is incorrect. > > Setting to "the value", will as you rightly and as PJSIP rightly does, create an escaped version ;param=the%20value. > Right. But aren't you in control of what the delimiter value is? I mean, can't you control the value such that escaping and quoting the parameter will not be necessary? Benny _______________________________________________ Visit our blog: http://blog.pjsip.org pjsip mailing list pjsip at lists.pjsip.org http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
