The extra parameters added in via-header in [1] like "oc", '=' sign was used. It seems '=' is correct way to go ahead instead of ':'.
[1] http://tools.ietf.org/html/draft-ietf-soc-overload-control-15 On Fri, Mar 21, 2014 at 5:39 PM, Olle E. Johansson <[email protected]> wrote: > > On 21 Mar 2014, at 11:47, Brett Tate <[email protected]> wrote: > > > The Contact's ABNF is within RFC 3261 section 25.1. > He asked for a header parameter, not the contact parameter. Where's that > documented? > > /O > > Your new contact > > parameter must conform to contact-extension. You'd use an equals instead > > of colon. > > > > Contact = ("Contact" / "m" ) HCOLON > > ( STAR / (contact-param *(COMMA contact-param))) > > contact-param = (name-addr / addr-spec) *(SEMI contact-params) > > contact-params = c-p-q / c-p-expires > > / contact-extension > > contact-extension = generic-param > > generic-param = token [ EQUAL gen-value ] > > gen-value = token / host / quoted-string > > token = 1*(alphanum / "-" / "." / "!" / "%" / "*" > > / "_" / "+" / "`" / "'" / "~" ) > > > >> -----Original Message----- > >> From: [email protected] [mailto:sip- > >> [email protected]] On Behalf Of J C Sunil > >> Kumar Reddy > >> Sent: Friday, March 21, 2014 6:33 AM > >> To: [email protected] > >> Subject: [Sip-implementors] Query on Contact header parameter > >> > >> Hi All, > >> > >> I need to send a proprietary parameter in contact header in an INVITE > >> message to other end. > >> Something like this: > >> > >> Contact: "Sunil" > >> <sip:[email protected];transport=tcp>;category:strvalue > >> > >> Here "category:strvalue" is my proprietary parameter. Where "category" > >> is a > >> param name and "strvalue" is the value. > >> > >> What does the SIP standard specify? whether it should be colon(:) or > >> Equals(=)? > >> I mean according to SIP standards, which is the correct one? > >> > >> category:strvalue > >> or > >> category=strvalue > >> or something else? > > > > -- > > > > > > This email is intended solely for the person or entity to which it is > > addressed and may contain confidential and/or privileged information. If > > you are not the intended recipient and have received this email in error, > > please notify BroadSoft, Inc. immediately by replying to this message, > and > > destroy all copies of this message, along with any attachment, prior to > > reading, distributing or copying it. > > > > _______________________________________________ > > Sip-implementors mailing list > > [email protected] > > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
