I was pretty sure this was fixed. Can you send a simple set of XML scenarios (UAC and UAS) that replicate this bug?
Any bug of this nature is most likely in get_last_header, but CreateSendingMessage could be at fault as well. Charles [EMAIL PROTECTED] wrote on 03/05/2008 09:10:50 AM: > Hey list, > > I think this has been raised before and fixed, but it is back again. > > For example when the below scenario is used: > > <scenario name="MS Basic Responder"> > > <recv request="REGISTER" rrs="true" crlf="true" /> > > <send> > <![CDATA[ > > SIP/2.0 200 OK > [last_From:] > [last_CSeq:] > [last_To:] > [last_Call-ID:] > [last_Via:] <--------------------- ERROR > Content-Length: 0 > > ]]> > </send> > ... > > The [last_Via:] chops off the last character!!! Thus it is an invalid > SIP signal!!! > > I'm using the official SIPp 3.0. Is there a patch? Is this fixed in > the latest unofficial build? If not, where should I look in the source > code??? > > Simon > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Sipp-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/sipp-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
