Hi guys, Current docs says: "When a SIP message that can be correlated to an existing call (with the Call-ID: header) but is not expected in the scenario is received, SIPp will send a CANCEL message if no 200 OK message has been received or a BYE message if a 200 OK message has been received. The call will be marked as failed. If the unexpected message is a 4XX or 5XX, SIPp will send an ACK to this message, close the call and mark the call as failed."
What about this scenario ? Sipp UAC --INVITE--> Sipp UAC <--403 Forbidden-- *1 Sipp UAC --ACK--> Sipp UAC pausing for a while Sipp UAC <--100 Trying-- *2 *1 and *2 are due to packet reordering (it seems at least). In this case, sipp marks the call as failed saying: "Aborting call on unexpected message for Call-Id '[email protected]': while pausing (index 9), received 'SIP/2.0 100 Trying" Which I think is not really a correct behaviour, but not 100% sure about that :-) Has someone seen similar before ? Thanks, Endre ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
