On Tue, 2006-04-25 at 12:18 -0400, Uttam Kumar Sarkar wrote:
> According to that we are expecting that Allow-Events header in the
> following format:
>
> Allow-Events: message-summary, refer, dialog, line-seize.
>
> Any suggestion on this is appreciated.
RFC 3261, section 6:
Header Field: A header field is a component of the SIP message
header. A header field can appear as one or more header field
rows. Header field rows consist of a header field name and zero
or more header field values. Multiple header field values on a
given header field row are separated by commas. Some header
fields can only have a single header field value, and as a
result, always appear as a single header field row.
Section 7.3:
[H4.2] also specifies that multiple header fields of the same field
name whose value is a comma-separated list can be combined into one
header field. That applies to SIP as well, but the specific rule is
different because of the different grammars. Specifically, any SIP
header whose grammar is of the form
header = "header-name" HCOLON header-value *(COMMA header-value)
allows for combining header fields of the same name into a comma-
separated list.
So
Allow-Events: message-summary, refer, dialog, line-seize.
can always be written as:
Allow-Events: message-summary
Allow-Events: dialog
Allow-Events: line-seize
Dale
---
interop.pingtel.com -- the public SIP phone interoperability test server
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
