Re: [Sip-implementors] Is it acceptable to have "methods=" param in the Contact header for a REGISTER message

2007-12-20 Thread Paul Kyzivat
[EMAIL PROTECTED] wrote: > Searching for "methods" in RFC 3840 turns up an oddity: Section 5 > says: > >When using the "sip.methods" feature tag, a UA MUST NOT include >values that correspond to methods not standardized in IETF standards >track RFCs. > > but two paragraphs later i

Re: [Sip-implementors] Is it acceptable to have "methods=" param in the Contact header for a REGISTER message

2007-12-20 Thread Dale . Worley
From: "Amit P. Ahuja" <[EMAIL PROTECTED]> One of the SIP hardphones that I use sends out a REGISTER message with the Contact header that looks like: Contact: sip:[EMAIL PROTECTED]:5060;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, RE

[Sip-implementors] Is it acceptable to have "methods=" param in the Contact header for a REGISTER message

2007-12-19 Thread Amit P. Ahuja
One of the SIP hardphones that I use sends out a REGISTER message with the Contact header that looks like: Contact: sip:[EMAIL PROTECTED]:5060;methods="INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER" I could not find whether the "methods=" param in the