At 04:58 PM 7/31/2007, Francois Audet wrote:
Hi all,
It seems from the mailing list discussion that the preferred approach is
to
use the 480 (Temporarily Unavailable) response code, with a Warning
header field.
The Warning header could use one of the following 2 newly defined
warn-codes:
380 SIPS Not Allowed: The UAS or proxy can
s/can/cannot
process the request
because the SIPS scheme is not allowed (e.g., because there are
currently no registered SIPS Contacts).
381 SIPS Required: The UAS or proxy cannot process the request
because the SIPS scheme is required.
If you cannot live with this approach, please voice your opinion.
Thanks.
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
_______________________________________________
Sip mailing list https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [EMAIL PROTECTED] for questions on current sip
Use [EMAIL PROTECTED] for new developments on the application of sip
