> 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
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
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 r
.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
...@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
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 CONT
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 i
