Hi, I found that there was indeed a bug in opensips. The body extracted from received Notify contained '\n' at the end so before the boundary string there was a sequence of \n and 2 CRLF(\r\n). I have fixed this and now there are always 2 CRLF. However I see that my wireshark still shows \r\n at the beginning of the boundary string... With the starting string not ending right - I did not observe this in my tests so far. Please update with the fix and le me know if you still see problems.
Regards, -- Anca Vamanu www.voice-system.ro Juha Heinanen wrote: > Ovidiu Sas writes: > > >> I don't think that the second boundary looks ok: >> Boundary: \r\n--1fZ25o5K6UJOKcK25Mw2VZNJ\r\n >> >> See the \r\n in the middle of the string. >> > > yes, and also start param value looks wrong on this line: > > Content-Type: multipart/related;type="application/rlmi+xml";start= > "<127532956\r\n\r\n > > -- juha > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
