Re: [Sip-implementors] is Contact Header Mandatory and could be anonymous in the INVITE

[Dale R. Worley]

> On Sat, Mar 3, 2018 at 7:33 PM, Dale R. Worley  wrote:
>
>> Zuniga, Guillermo  writes:
>> > I Access enviroment not PEER to PEER connection, CONTACT could be
>> > anonymous or always should be any valid uri-user?
>>
>> The Contact always has to be a valid URI.  However, that URI does not
>> have to be the AOR (address-of-record) of a customer; it just has to be
>> able to reach the UA (when used by the next proxy in the signaling
>> path).

There are a lot of complexities.  Certainly, the Contact has to be a
syntactically correct URI.  But there are various ways to avoid
divulging user-sensitive information.  See

3323 A Privacy Mechanism for the Session Initiation Protocol (SIP). J.
 Peterson. November 2002. (Format: TXT=54116 bytes) (Status: PROPOSED
 STANDARD) (DOI: 10.17487/RFC3323) 

5379 Guidelines for Using the Privacy Mechanism for SIP. M. Munakata, S.
 Schubert, T. Ohba. February 2010. (Format: TXT=52595 bytes) (Status:
 INFORMATIONAL) (DOI: 10.17487/RFC5379) 

5767 User-Agent-Driven Privacy Mechanism for SIP. M. Munakata, S.
 Schubert, T. Ohba. April 2010. (Format: TXT=23270 bytes) (Status:
 INFORMATIONAL) (DOI: 10.17487/RFC5767) 

Dale
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Re: [Sip-implementors] is Contact Header Mandatory and could be anonymous in the INVITE

[Arun Tagare]

 Hi  Zuniga, Guillermo

The below abstract clearly states that CONTACT header *MUST* contain a
valid URI.

RFC 3261


>>>
That is, the Contact header field value contains
 the URI at which the UA would like to receive requests, and this URI
 MUST be valid even if used in subsequent requests outside of any
 dialogs.
<<<

Hope that could help you

Thanks & Regards
Arun A. Tagare




On Sat, Mar 3, 2018 at 7:33 PM, Dale R. Worley  wrote:

> Zuniga, Guillermo  writes:
> > I Access enviroment not PEER to PEER connection, CONTACT could be
> > anonymous or always should be any valid uri-user?
>
> The Contact always has to be a valid URI.  However, that URI does not
> have to be the AOR (address-of-record) of a customer; it just has to be
> able to reach the UA (when used by the next proxy in the signaling
> path).
>
> Dale
> ___
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>



-- 

With Regards

Arun A. Tagare
+91 9449 029729
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Re: [Sip-implementors] is Contact Header Mandatory and could be anonymous in the INVITE

[Dale R. Worley]

Zuniga, Guillermo  writes:
> I Access enviroment not PEER to PEER connection, CONTACT could be
> anonymous or always should be any valid uri-user?

The Contact always has to be a valid URI.  However, that URI does not
have to be the AOR (address-of-record) of a customer; it just has to be
able to reach the UA (when used by the next proxy in the signaling
path).

Dale
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Re: [Sip-implementors] is Contact Header Mandatory and could be anonymous in the INVITE

[anhright]

Hi Guillermo, 
Contact header could be anonymous in some cases. An example is when you hide 
your Caller ID.
A.C
Sent from my Samsung Galaxy smartphone.
 Original message From: "Zuñiga, Guillermo" 
 Date: 3/2/18  05:07  (GMT+07:00) To: Aman 
 Cc: discuss...@sipforum.org, 
sip-implementors@lists.cs.columbia.edu Subject: Re: [Sip-implementors] is 
Contact Header Mandatory and could be anonymous in the INVITE 
Thanks for that,

I Access enviroment not PEER to PEER connection, CONTACT could be anonymous or 
always should be any valid uri-user?

Regards,
Thanks
Guillermo

De: Aman [mailto:amanpreeet.si...@gmail.com]
Enviado el: Monday, February 26, 2018 3:11 AM
Para: Zuñiga, Guillermo
CC: discuss...@sipforum.org; sip-implementors@lists.cs.columbia.edu
Asunto: Re: [Sip-implementors] is Contact Header Mandatory and could be 
anonymous in the INVITE

Yes, CONTACT header field is mandatory for the SIP INVITE request.

Cheers,
Aman
​preet Singh​


On Thu, Feb 22, 2018 at 12:57 AM, Zuñiga, Guillermo 
mailto:guillermo.zun...@cwpanama.com>> wrote:
Hi fellows,

I would you can help me to know and be clear about the following questions:

Is the CONTACT header mandatory that always have to be present in the INVITE?
I am asking that for the case that imagine that Endpoint after is Registered in 
a Registrar Server, send me the following header info.

FROM uri-user =anonymous@domain/ip
TO uri-user=called(uri-user)@domain/ip

CONTACT = could be anonymous@domain/ip or should be original uri-user@domain/ip 
?? if you can help me to identify this in the RFC or give some tips more where 
I can search more information, will be great.


According with the RFC 3261,
8.1.1.8 Contact


The Contact header field provides a SIP or SIPS URI that can be used
 to contact that specific instance of the UA for subsequent requests.
 The Contact header field MUST be present and contain exactly one SIP
 or SIPS URI in any request that can result in the establishment of a
 dialog. For the methods defined in this specification, that includes
 only the INVITE request. For these requests, the scope of the
 Contact is global. That is, the Contact header field value contains
 the URI at which the UA would like to receive requests, and this URI
 MUST be valid even if used in subsequent requests outside of any
 dialogs.

If the Request-URI or top Route header field value contains a SIPS
 URI, the Contact header field MUST contain a SIPS URI as well.

For further information on the Contact header field, see Section
 20.10.


Regards and thanks for all your time.
I really appreciate a lot your time.

Thanks,
Guillermo



Guillermo Zuniga
Especialista de Soporte Técnico
Gerencia de Soporte Técnico

Tel:    +507 263-6671
Cel:    +507 6670-0481
Fax:    +507 265-3295
Email:  guillermo.zun...@cwpanama.com<mailto:guillermo.zun...@cwpanama.com>

[cid:image3f4341.JPG@d191b510.4e907fe0]

<http://www.cwpanama.com>

<http://www.cwpanama.com>

<http://play.google.com/store/apps/details?id=com.croem.web.cwp>

<http://www.facebook.com/masmovilpanama>

<http://www.cwpanama.com>

<http://bit.ly/MasMovil>

<http://www.facebook.com/masmovilpanama>

<http://www.facebook.com/masmovilpanama>

[cid:image447e4b.JPG@010140db.4385dd6c]



El contenido de este correo es confidencial y puede ser objeto de acciones 
legales.  Es dirigido solo para el o los destinatarios(s) nombrados 
anteriormente. Si no es mencionado como destinatario, no debe leer, copiar, 
revelar, reenviar o utilizar el contenido de este mensaje. Si ha recibido este 
correo por error, por favor notifique al remitente y proceda a borrar el 
mensaje y archivos adjuntos sin conservar copias.

The information contained in this e-mail is confidential and may also be 
subject to legal privilege.  It is intended only for the recipient(s) named 
above.  If you are not named as a recipient, you must not read, copy, disclose, 
forward or otherwise use the information contained in this email.  If you have 
received this e-mail in error, please notify the sender immediately by reply 
e-mail and delete the message and any attachments without retaining any copies.




Guillermo Zuniga
Especialista de Soporte Técnico
Gerencia de Soporte Técnico

Tel:    +507 263-6671
Cel:    +507 6670-0481
Email:  guillermo.zun...@cwpanama.com

[cid:image2de857.JPG@a646cd6c.458f29e7]

<http://www.cwpanama.com>

<http://www.cwpanama.com>

<http://play.google.com/store/apps/details?id=com.croem.web.cwp>

<http://www.facebook.com/masmovilpanama>

<http://www.cwpanama.com>

<http://bit.ly/MasMovil>

<http://www.facebook.com/masmovilpanama>

<http://www.facebook.com/masmovilpanama>



<https://play.google.com/store/apps/details?id=com.croem.web.cwp>

<http://www.cwpanama.com>

[cid:image4e1677.JPG@f5733792.48a6d594]


___
Sip-implementors mailing list
Sip-im

Re: [Sip-implementors] is Contact Header Mandatory and could be anonymous in the INVITE

[Zuñiga , Guillermo]

Thanks for that,

I Access enviroment not PEER to PEER connection, CONTACT could be anonymous or 
always should be any valid uri-user?

Regards,
Thanks
Guillermo

De: Aman [mailto:amanpreeet.si...@gmail.com]
Enviado el: Monday, February 26, 2018 3:11 AM
Para: Zuñiga, Guillermo
CC: discuss...@sipforum.org; sip-implementors@lists.cs.columbia.edu
Asunto: Re: [Sip-implementors] is Contact Header Mandatory and could be 
anonymous in the INVITE

Yes, CONTACT header field is mandatory for the SIP INVITE request.

Cheers,
Aman
​preet Singh​


On Thu, Feb 22, 2018 at 12:57 AM, Zuñiga, Guillermo 
mailto:guillermo.zun...@cwpanama.com>> wrote:
Hi fellows,

I would you can help me to know and be clear about the following questions:

Is the CONTACT header mandatory that always have to be present in the INVITE?
I am asking that for the case that imagine that Endpoint after is Registered in 
a Registrar Server, send me the following header info.

FROM uri-user =anonymous@domain/ip
TO uri-user=called(uri-user)@domain/ip

CONTACT = could be anonymous@domain/ip or should be original uri-user@domain/ip 
?? if you can help me to identify this in the RFC or give some tips more where 
I can search more information, will be great.


According with the RFC 3261,
8.1.1.8 Contact


The Contact header field provides a SIP or SIPS URI that can be used
 to contact that specific instance of the UA for subsequent requests.
 The Contact header field MUST be present and contain exactly one SIP
 or SIPS URI in any request that can result in the establishment of a
 dialog. For the methods defined in this specification, that includes
 only the INVITE request. For these requests, the scope of the
 Contact is global. That is, the Contact header field value contains
 the URI at which the UA would like to receive requests, and this URI
 MUST be valid even if used in subsequent requests outside of any
 dialogs.

If the Request-URI or top Route header field value contains a SIPS
 URI, the Contact header field MUST contain a SIPS URI as well.

For further information on the Contact header field, see Section
 20.10.


Regards and thanks for all your time.
I really appreciate a lot your time.

Thanks,
Guillermo



Guillermo Zuniga
Especialista de Soporte Técnico
Gerencia de Soporte Técnico

Tel:+507 263-6671
Cel:+507 6670-0481
Fax:+507 265-3295
Email:  guillermo.zun...@cwpanama.com<mailto:guillermo.zun...@cwpanama.com>

[cid:image3f4341.JPG@d191b510.4e907fe0]

<http://www.cwpanama.com>

<http://www.cwpanama.com>

<http://play.google.com/store/apps/details?id=com.croem.web.cwp>

<http://www.facebook.com/masmovilpanama>

<http://www.cwpanama.com>

<http://bit.ly/MasMovil>

<http://www.facebook.com/masmovilpanama>

<http://www.facebook.com/masmovilpanama>

[cid:image447e4b.JPG@010140db.4385dd6c]



El contenido de este correo es confidencial y puede ser objeto de acciones 
legales.  Es dirigido solo para el o los destinatarios(s) nombrados 
anteriormente. Si no es mencionado como destinatario, no debe leer, copiar, 
revelar, reenviar o utilizar el contenido de este mensaje. Si ha recibido este 
correo por error, por favor notifique al remitente y proceda a borrar el 
mensaje y archivos adjuntos sin conservar copias.

The information contained in this e-mail is confidential and may also be 
subject to legal privilege.  It is intended only for the recipient(s) named 
above.  If you are not named as a recipient, you must not read, copy, disclose, 
forward or otherwise use the information contained in this email.  If you have 
received this e-mail in error, please notify the sender immediately by reply 
e-mail and delete the message and any attachments without retaining any copies.




Guillermo Zuniga
Especialista de Soporte Técnico
Gerencia de Soporte Técnico

Tel:+507 263-6671
Cel:+507 6670-0481
Email:  guillermo.zun...@cwpanama.com

[cid:image2de857.JPG@a646cd6c.458f29e7]

<http://www.cwpanama.com>

<http://www.cwpanama.com>

<http://play.google.com/store/apps/details?id=com.croem.web.cwp>

<http://www.facebook.com/masmovilpanama>

<http://www.cwpanama.com>

<http://bit.ly/MasMovil>

<http://www.facebook.com/masmovilpanama>

<http://www.facebook.com/masmovilpanama>



<https://play.google.com/store/apps/details?id=com.croem.web.cwp>

<http://www.cwpanama.com>

[cid:image4e1677.JPG@f5733792.48a6d594]


___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu<mailto:Sip-implementors@lists.cs.columbia.edu>
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors

Re: [Sip-implementors] is Contact Header Mandatory and could be anonymous in the INVITE

[Aman]

Yes, CONTACT header field is mandatory for the SIP INVITE request.

Cheers,
Aman
​preet Singh​


On Thu, Feb 22, 2018 at 12:57 AM, Zuñiga, Guillermo <
guillermo.zun...@cwpanama.com> wrote:

> Hi fellows,
>
> I would you can help me to know and be clear about the following questions:
>
> Is the CONTACT header mandatory that always have to be present in the
> INVITE?
> I am asking that for the case that imagine that Endpoint after is
> Registered in a Registrar Server, send me the following header info.
>
> FROM uri-user =anonymous@domain/ip
> TO uri-user=called(uri-user)@domain/ip
>
> CONTACT = could be anonymous@domain/ip or should be original
> uri-user@domain/ip ?? if you can help me to identify this in the RFC or
> give some tips more where I can search more information, will be great.
>
>
> According with the RFC 3261,
> 8.1.1.8 Contact
>
>
> The Contact header field provides a SIP or SIPS URI that can be used
>  to contact that specific instance of the UA for subsequent requests.
>  The Contact header field MUST be present and contain exactly one SIP
>  or SIPS URI in any request that can result in the establishment of a
>  dialog. For the methods defined in this specification, that includes
>  only the INVITE request. For these requests, the scope of the
>  Contact is global. That is, the Contact header field value contains
>  the URI at which the UA would like to receive requests, and this URI
>  MUST be valid even if used in subsequent requests outside of any
>  dialogs.
>
> If the Request-URI or top Route header field value contains a SIPS
>  URI, the Contact header field MUST contain a SIPS URI as well.
>
> For further information on the Contact header field, see Section
>  20.10.
>
>
> Regards and thanks for all your time.
> I really appreciate a lot your time.
>
> Thanks,
> Guillermo
>
>
>
> Guillermo Zuniga
> Especialista de Soporte Técnico
> Gerencia de Soporte Técnico
>
> Tel:+507 263-6671
> Cel:+507 6670-0481
> Fax:+507 265-3295
> Email:  guillermo.zun...@cwpanama.com
>
> [cid:image3f4341.JPG@d191b510.4e907fe0]
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> [cid:image447e4b.JPG@010140db.4385dd6c]
>
>
>
> El contenido de este correo es confidencial y puede ser objeto de acciones
> legales.  Es dirigido solo para el o los destinatarios(s) nombrados
> anteriormente. Si no es mencionado como destinatario, no debe leer, copiar,
> revelar, reenviar o utilizar el contenido de este mensaje. Si ha recibido
> este correo por error, por favor notifique al remitente y proceda a borrar
> el mensaje y archivos adjuntos sin conservar copias.
>
> The information contained in this e-mail is confidential and may also be
> subject to legal privilege.  It is intended only for the recipient(s) named
> above.  If you are not named as a recipient, you must not read, copy,
> disclose, forward or otherwise use the information contained in this
> email.  If you have received this e-mail in error, please notify the sender
> immediately by reply e-mail and delete the message and any attachments
> without retaining any copies.
>
> ___
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>
>
___
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors