thanks you. That's what I was thinking. Since SIP allows multi-part message we can use different charsets. I shall check on the RFC 2781 and the other thread that Bret provided. Thank you very much for the quick guidance
On Thu, Jun 20, 2013 at 6:19 PM, Joel Gerber <[email protected]>wrote: > One more note; you could have a multi-part message body with different > charsets. So 6556 and 78788 could be in one part as ASCII, while testname > would be in another part as UTF-16. > > Joel Gerber > Network Specialist > Network Operations > Eastlink > E: [email protected] T: 519.786.1241 > > -----Original Message----- > From: Brett Tate [mailto:[email protected]] > Sent: June-20-13 8:49 AM > To: tina raj; [email protected] > Subject: Re: [Sip-implementors] UTF-16 support in SIP > > Yes; you'd set the charset to be UTF-16 (although the "6556 78788" are > also UTF-16). However, you might be interested in RFC 2781 since it looks > like there may be some restrictions. > > Concerning the request-uri, my understanding is the answer is no. > > RFC 3986 section 2.5 does provide an escaping mechanism to allow full > UTF-8 for new URI schemes. However my understanding is that older schemes > (such as "sip"), don't expect the escaping concatenation. > > Since you are asking about UTF-16, you might be interested in the > following sipcore "SIP and Internationalisation" thread. Things are > potentially not as well standardized and interoperable as you might like it > to be. > > http://www.ietf.org/mail-archive/web/sipcore/current/msg05590.html > > > From: tina raj [mailto:[email protected]] > Sent: Thursday, June 20, 2013 7:25 AM > To: Brett Tate > Cc: [email protected] > Subject: Re: [Sip-implementors] UTF-16 support in SIP > > Thanks Bret. My question is more like I have couple of data in the body > of the SIP message like in SIP NOTIFY, the message body conatins data as > 6556 > 78788 > testname > > where in only the testname should be in UTF-16 and the rest of the data > remain as plain text In case we do this , do we have to set the charset in > the content-type to "UTF-16" > > Also can the request uri value have the data in UTF-16 ? > > > > > On Thu, Jun 20, 2013 at 4:54 PM, Brett Tate <[email protected]<mailto: > [email protected]>> wrote: > Yes; the body can contain UTF-16. > > RFC 3261 section 7.4.1: > > SIP messages MAY contain binary bodies or body parts. When no > explicit charset parameter is provided by the sender, media subtypes > of the "text" type are defined to have a default charset value of > "UTF-8". > > > -----Original Message----- > > From: tina raj [mailto:[email protected]<mailto:[email protected]>] > > Sent: Thursday, June 20, 2013 7:14 AM > > To: > > [email protected]<mailto:[email protected] > > s.columbia.edu> > > Subject: [Sip-implementors] UTF-16 support in SIP > > > > Is it possible that a part of the SIP message body can be in text and > > some in UTF-16 > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
