Also to substantiate that Contact header is optional for 200 OK for REGISTER,
here is one more context in RFC.

See Table 2: Summary of header fields, A--O of RFC 3261, just after section 
20.1.

Header field          where   proxy ACK BYE CAN INV OPT REG
Contact                2xx           -   -   -   m   o   o


This says that Contcat in 2XX for INVITE is mandatory while for REGISTER is 
optional.

Somesh S Shanbhag
M G L Bangalore



-----Original Message-----
From: [EMAIL PROTECTED] on behalf of Jesus Rodriguez
Sent: Thu 9/11/2008 3:28 PM
To: Iñaki Baz Castillo
Cc: [email protected]
Subject: Re: [Sip-implementors] Fetching Bindings
 
Hello,


> El Jueves, 11 de Septiembre de 2008, Victor Pascual Ávila escribió:
>> Scenario: a SIP UA is not registered and it sends a REGISTER request
>> without Contact header.
>>
>> A success response to any REGISTER request contains the complete list
>> of existing bindings, regardless of whether the request contained a
>> Contact header field.
>>
>> Contact cannot be empty:
>> Contact  =   ( "Contact" / "m" ) HCOLON
>> ( STAR / (contact-param *(COMMA contact-param)))
>> contact-param  =  (name-addr / addr-spec) *( SEMI contact-params)
>>
>>
>> RFC3261, Section 10.3- Step 8 says:
>>
>> "The registrar returns a 200 (OK) response.  The response MUST  
>> contain
>> Contact header field values enumerating all current bindings."
>>
>> It should say:
>>
>> "The registrar returns a 200 (OK) response. If there exist any
>> bindings for that AOR, the response MUST contain Contact header field
>> values enumerating all current bindings."
>>
>> Am I right?
>
>
> I 100% agree. This seems a bug since a Contact cannont be empty (BNF  
> syntax)
> but there is a "MUST contain Contact".


I also agree with Victor. If no bindings exist, the 200OK should not  
have a Contact header.

Saludos
JesusR.

------------------------------------
Jesus Rodriguez
VozTelecom Sistemas, S.L.
[EMAIL PROTECTED]
http://www.voztele.com
Tel. 902360305
-------------------------------------





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

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

Reply via email to