osip-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [osip-dev] Parsing problem in case of Turkish characters in SDP


From: Aymeric Moizard
Subject: Re: [osip-dev] Parsing problem in case of Turkish characters in SDP
Date: Tue, 25 Sep 2012 20:48:25 +0200

Hi,

As defined in the SDP rfc: the attribute value is defined this way: (hexadecimal values for all letters)
and as explained in the rfc, the charset should be utf8

   byte-string =         1*(%x01-09/%x0B-0C/%x0E-FF)
                         ;any byte except NUL, CR, or LF


öçşğüİ.jpg should thus be added in utf8 and read in utf8.

osip has no knowledge of the charset and only write and read bytes, so unless
there is a real issue, I don't see any reason for the parser to fail!

Also, you haven't reported the reason why it fails? Have you tried a debugger? Any
usefull log or return code?

Regards
Aymeric

2012/9/24 Ceyda İdikurt <address@hidden>

Hi everyone,

This is Ceyda and i am beginner in C++.I have a problem with oSIP library.If anyone can help, thank you in advance.

I’m trying to parse that SDP by using oSIP SDP parser:

 

v=0

o=- 3556967126 3556967126 IN IP4 192.168.200.27

s=pjmsrp

c=IN IP4 192.168.200.27

t=0 0

m=message 52805 TCP/MSRP *

a=path:msrp://192.168.200.27:52805/0b9cdc925d9a42eab01c43f7d375575a;tcp

a=sendonly

a=setup:active

a=accept-types:*

a=file-selector:name:"öçşğüİ.jpg" type:application/octet-stream size:245418 hash:sha1:1b10ec8f9d3054a54341f9a721949886fcc1

 

 

But sdp_message_parse method fails if SDP has any Turkish characters.Then i tried to add “a:charset” parameter to SDP like that:

 

v=0

o=- 3556967126 3556967126 IN IP4 192.168.200.27

s=pjmsrp

c=IN IP4 192.168.200.27

t=0 0

a=charset:ISO-8859-9

m=message 52805 TCP/MSRP *

a=path:msrp://192.168.200.27:52805/0b9cdc925d9a42eab01c43f7d375575a;tcp

a=sendonly

a=setup:active

a=accept-types:*

a=file-selector:name:"öçşğüİ.jpg" type:application/octet-stream size:245418 hash:sha1:1b10ec8f9d3054a54341f9a721949886fcc1

 

But it still fails again.What should i do to make it parsed correctly?

 

Ceyda İdikurt


_______________________________________________
osip-dev mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/osip-dev




--
Antisip - http://www.antisip.com


reply via email to

[Prev in Thread] Current Thread [Next in Thread]