Re: [SR-Users] libosip2 parse body error

Thanks Daniel, fyi, the Content-Length doesn't match the actual length in the invite ok returned from iptel.org <http://iptel.org> (213.192.59.75), and the same situation also occurs from ekiga.net <http://ekiga.net>. libosip2 interprets the rfc as saying that this 'should' be correct. (and I buy this!). it looks like an openser (opensips?) quirk. anyway, I have put in code locally to fixup the Content-Length. Thanks, Tony. 73 75 62 0d 0a 43 6f 6e 74 65 6e 74 2d 4c 65 6e sub..Content-Len 67 74 68 3a 20 20 20 32 30 31 0d 0a 0d 0a 76 3d gth: 201....v= 30 0d 0a 6f 3d 74 77 69 6e 6b 6c 65 20 31 33 33 0..o=twinkle 133 33 37 30 37 32 38 39 20 38 30 39 37 35 37 36 37 3707289 80975767 33 20 49 4e 20 49 50 34 20 31 39 32 2e 31 36 38 3 IN IP4 192.168 2e 32 35 34 2e 31 0d 0a 73 3d 2d 0d 0a 63 3d 49 .254.1..s=-..c=I 4e 20 49 50 34 20 31 39 32 2e 31 36 38 2e 32 35 N IP4 192.168.25 34 2e 31 0d 0a 74 3d 30 20 30 0d 0a 6d 3d 61 75 4.1..t=0 0..m=au 64 69 6f 20 35 30 32 32 20 52 54 50 2f 41 56 50 dio 5022 RTP/AVP 20 39 38 20 31 30 31 0d 0a 61 3d 72 74 70 6d 61 98 101..a=rtpma 70 3a 39 38 20 73 70 65 65 78 2f 31 36 30 30 30 p:98 speex/16000 0d 0a 61 3d 72 74 70 6d 61 70 3a 31 30 31 20 74 ..a=rtpmap:101 t 65 6c 65 70 68 6f 6e 65 2d 65 76 65 6e 74 2f 38 elephone-event/8 30 30 30 0d 0a 61 3d 66 6d 74 70 3a 31 30 31 20 000..a=fmtp:101 30 2d 31 35 0d 0a 0-15.. On Wed, Oct 27, 2010 at 5:40 AM, Daniel-Constantin Mierla &lt;miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote: Hello, you claim that contact header is malformed or libosip2 has issues in parsing a good content header? In case of first option, can you tell what it believes is wrong. Your message is hard to follow since is not clear text, next time send only the text part. For the second option, you have to approach libosip2 support forums. Cheers, Daniel On 10/25/10 10:44 PM, t wrote: -- Daniel-Constantin Mierla http://www.asipto.com