[SIPForum-discussion] Difference between Update and Re-Invite

[balajivenkat subramanian]

Hi Deepak ,

To add more  ,

Use of UPDATE
-----------------------
It allows a client to update parameters of a session (such as the set of
media streams and their codecs) but has no impact on the state of a dialog .

How different from Reinvite
--------------------------------------
it is like a re-INVITE, but unlike re-INVITE, it can be sent before the
initial INVITE has been completed.  This makes it very useful for updating
session parameters within early dialogs.

Regards,
Venkat

On Tue, Aug 10, 2010 at 2:10 AM, Nitin Kapoor <nitinkapoorr at gmail.com>wrote:

> Deepak,
>
> Both re-Invite and UPDATE are similar but the actual difference lies where
> UPDATE is always one way whereas in re-invite the negotiation happens like
> initial invite request.
>
> In UPDATE, either offer is accepted or ignored but the entity which
> receives UPDATE can't send it's allowed media parameters in the response,
> like what happens in 200OK for INVITE or re-INVITE.
>
> Thanks,
> Nitin Kapoor
>
>   On 9 August 2010 12:07, Deepak raj Siddharthan <
> deepakraj.siddhu at gmail.com> wrote:
>
>>   Hello all,
>>
>> Can any one tell me the difference betweent the "Update" method and
>> "Re-Invite" ?
>>
>> Thanks in advance
>>
>> Best Regards,
>> Deepak
>>
>> _______________________________________________
>> This is the SIP Forum discussion mailing list
>> TO UNSUBSCRIBE, or edit your delivery options, please visit
>> http://sipforum.org/mailman/listinfo/discussion
>> Post to the list at discussion at sipforum.org
>>
>>
>
> _______________________________________________
> This is the SIP Forum discussion mailing list
> TO UNSUBSCRIBE, or edit your delivery options, please visit
> http://sipforum.org/mailman/listinfo/discussion
> Post to the list at discussion at sipforum.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20100810/d003848c/attachment-0002.html>