[reSIProcate] Incorrect pre-parsing SIP-ETag header

[Volodymyr Tarasenko]

Hi,

As I see resiprocate does not parse SIP-ETag correctly
(BTW it was generated by itself). For example attached
200 OK was generated by resiprocate's DUM but cannot
be processed by resiprocate when it was received via
UDP, error is: 
Scanner rejecting datagram as unparsable / fragmented 

As I see it happens when 0x0a symbol exists in this
header because resiprocate correctly parses all other
messages where SIP-ETag exists without this symbol...

Any idea how to fix it? ;) 


      ____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OK.sip
Type: application/octet-stream
Size: 474 bytes
Desc: 795631201-OK.sip
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20080326/5e74e504/attachment.obj>