You have to let SIPp generate the Call-ID: --------------------------------------- [call_id] A call_id identifies a call and is generated by SIPp for each new call. In client mode, it is mandatory to use the value generated by SIPp in the "Call-ID" header. Otherwise, SIPp will not recognise the answer to the message sent as being part of an existing call. --------------------------------------- (<http://sipp.sourceforge.net/doc2.0/reference.html#Structure+of+client+%28UAC+like%29+XML+scenarios>)
BR Michael Santosh Reddy wrote: > > Hi, > > I am doing a basic registration scenario where SIPp sends REGISTER and > receives 200 OK with some additional headers. I have attached the error > and message logs. please look into it. Can SIPp ignore or receive some > custom header received in responses > > -- > Thanks & Regards, > Santosh Reddy. > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > 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 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
