[SR-Users] libosip2 parse body error

2010-10-26 Thread t
Hi, Not sure how to provide this info (or even if anybody cares), but libosip2 parser objects to incorrect (short) Content-Length from iptel.org. Regards, Tony. 20:15:21 sock.c:434 send UDP packet to 213.192.59.75: 5060 ---BUFFER DUMP follows--- 53 49 50 2f 32 2e 30 20 32 30 30 20 4f 4b 0d 0a S

Re: [SR-Users] libosip2 parse body error

2010-10-27 Thread Daniel-Constantin Mierla
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

Re: [SR-Users] libosip2 parse body error

2010-10-27 Thread Daniel-Constantin Mierla
Never ever send private emails - they will be discarded, keep the mailing list cc-ed. Iptel org is running SIP Express Router 3.1. Take a ngrep of the traffic and send it here, the hexa codes you send are not for humans to read, like we are here on mailing lists. Otherwise make a tar.gz of pca

Re: [SR-Users] libosip2 parse body error

2010-10-27 Thread Klaus Darilion
On 10/27/2010 12:43 PM, Daniel-Constantin Mierla wrote: Now, if it is easier for you to count hex codes by hart in a combined content, then it is fine. For me is easier to get the body in text format and use wc tool to count. Except it is hard to say if there is CR, CRLF, LF (whatever) at the en

Re: [SR-Users] libosip2 parse body error

2010-10-27 Thread Daniel-Constantin Mierla
On 10/27/10 9:54 PM, Klaus Darilion wrote: On 10/27/2010 12:43 PM, Daniel-Constantin Mierla wrote: Now, if it is easier for you to count hex codes by hart in a combined content, then it is fine. For me is easier to get the body in text format and use wc tool to count. Except it is hard to say

Re: [SR-Users] libosip2 parse body error

2010-10-27 Thread Stefan Sayer
Ovidiu Sas wrote: What is interesting in this particular 200ok, is the fact that only the IP was fixed: - the private IP was substituted with the public IP: - 192.168.254.1 -> 66.49.235.129 - the length of both IPs is the same - the port was _not_ touched - 5022 was provided and 5022 was

Re: [SR-Users] libosip2 parse body error

2010-10-27 Thread Ovidiu Sas
Well, then somebody at iptel.org should take a look at this ... because there's something wrong there ... Regards, Ovidiu Sas On Wed, Oct 27, 2010 at 4:14 PM, Stefan Sayer wrote: > Ovidiu Sas wrote: >> >> What is interesting in this particular 200ok, is the fact that only >> the IP was fixed: >>