Hello George,

I think the Contact is an exception which doesn't
fit to the rule you mention

Looking at section 7.3 of RFC 3261:

   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.  The Contact header field allows a comma-separated
   list unless the header field value is "*".

Note that the last part allows contact header fields to have
comma-separated lists.

Also note that the grammar directly implies that
this can be a comma separate list:
Contact        =  ("Contact" / "m" ) HCOLON
                  ( STAR / (contact-param *(COMMA contact-param)))
contact-param  =  (name-addr / addr-spec) *(SEMI contact-params)


Regards,

Attila

Attila Sipos
Software Engineer
www.vegastream.com


> -----Original Message-----
> From: George Petrov Georgiev-Rusiichev [mailto:[EMAIL PROTECTED]
> Sent: 30 October 2003 08:55
> To: [EMAIL PROTECTED]
> Subject: [Sip-implementors] question about Contact header
> 
> 
> 
> Hi all
> 
>   Is there anybody who can give me an idea whether Contact: header
>   could exist as a multiple header field rows. In RFC3261 is
>   written :
> 
> Multiple header field rows with the same field-name MAY be present in
>    a message if and only if the entire field-value for that 
> header field
>    is defined as a comma-separated list (that is, if follows 
> the grammar
>    defined in Section 7.3).  
> 
>  And the grammar for Contact: is
> 
> Contact        =  ("Contact" / "m" ) HCOLON
>                   ( STAR / (contact-param *(COMMA contact-param)))
> 
>  which doesn't match
>                   
> header  =  "header-name" HCOLON header-value *(COMMA header-value)
> 
> 
> The problem is that there are many servers that puts Contact: 
> in multiple header
> field rows e.g. SIP Express router (SER)
> 
> 
> Thanks in advance
> 
> 
> --
>  George                            mailto:[EMAIL PROTECTED]
> 
> _______________________________________________
> Sip-implementors mailing list
> [EMAIL PROTECTED]
> http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
> 
_______________________________________________
Sip-implementors mailing list
[EMAIL PROTECTED]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Reply via email to