According to RFC 3261 you can generate 405 if you cannot support the method.

8.2.1 Method Inspection

   Once a request is authenticated (or authentication is skipped), the
   UAS MUST inspect the method of the request.  If the UAS recognizes
   but does not support the method of a request, it MUST generate a 405
   (Method Not Allowed) response.


Somesh

* Please do not take print out of this e-mail unless  its absolutely necessary *



-----Original Message-----
From: [email protected] on behalf of NarayanaSwamy
Sent: Tue 3/3/2009 9:38 AM
To: 'Dale Worley'
Cc: [email protected]; [email protected]; [email protected]; 
[email protected]
Subject: Re: [Sip-implementors] Regarding custom messages
 
I understand that this is a guideline/practice we could follow to support a
custom-message. 
How about handling an unknown message (say XYZ)?

In the TCK (for JSR289) one of the test is sending an unknown message. Is it
okay to expect the SIP element handle this unknown message? 

NarayanaSwamy A.



EMAIL DISCLAIMER : This email and any files transmitted with it are 
confidential and intended solely for the use of the individual or entity to 
whom they are addressed. Any unauthorised distribution or copying is strictly 
prohibited. If you receive this transmission in error, please notify the sender 
by reply email and then destroy the message. Opinions, conclusions and other 
information in this message that do not relate to official business of Mascon 
shall be understood to be neither given nor endorsed by Mascon. Any information 
contained in this email, when addressed to Mascon clients is subject to the 
terms and conditions in governing client contract.

Whilst Mascon takes steps to prevent the transmission of viruses via e-mail, we 
can not guarantee that any email or attachment is free from computer viruses 
and you are strongly advised to undertake your own anti-virus precautions. 
Mascon grants no warranties regarding performance, use or quality of any e-mail 
or attachment and undertakes no liability for loss or damage, howsoever caused. 


_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

Reply via email to