I am testing a SIP UAS, and I am using the PROTO Test-Suite: c07-sip to test the robustness this UAS.
Since my UAS create SIP dialogs when receiving PROTO INVITE PDUs,
I use the "Connection Teardown mechanism" proposed by c07-sip java client.
see http://www.ee.oulu.fi/research/ouspg/protos/testing/c07/sip/index.html#appendix-a
This mechanism allows to send CANCEL, then ACK PDUs after receiving 1xx or 2xx response(s)
from my UAS. Indeed, receiving CANCEL and ACK in my UAS, should free the dialog. However,
as stated in section 12.2.1.1 of RFC 3261, a SIP UAC MUST send a CANCEL/ACK using the To Tag given
in the 1xx or 2xx response.
My UAS, and any other 3261-compliant UAS I tested actually respond 1xx, or 2xx (OK) with a To Tag, but the teardown mechanism
of Test-Suite: c07-sip Java client does NOT use this To Tag to send subsequent requests (CANCEL and ACK).
Thus, the UAS is unable to match the dialog ID of the INVITE (since dialogID = fromTag + callId +toTag), and is unable
to release any dialog. It means the teardown mechanism is completely unuseful to actually teardown sessions in a UAS,...
unless I misunderstood something.
I would be very interested to know how implementors have used Test-Suite: c07-sip, and especially, how they succeeded in
using the teardown mechanism to release sessions in a UAS. (This test was used at last SIP Interoperability event in International
SIP 2004, If some people present at this event could explain me...)
Thanks for advance
Thomas
_______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
