Hi Hanifa,
As refer *section 12.2.2 UAS Behavior of Rfc 3261*
" Requests sent within a dialog, as any other requests, are atomic. *If*
* a particular request is accepted by the UAS, all the state changes*
* associated with it are performed. If the request is rejected, none*
* of the state changes are performed.*
Note that some requests, such as INVITEs, affect several pieces of
state.
---------------
--------
-------
When a UAS receives a target refresh request, it MUST replace the
dialog's remote target URI with the URI from the Contact header field
in that request, if present.
"
And as per *section 12 Dialogs of rfc 3261,* A Dialog state consist of the
dialog
ID, a local sequence number , a remote sequence number , a local URI, a
remote URI, remote target, a boolean flag called "secure", and a route
set.
Please also refer *section 5.4. Target Refresh Requests of rfc 5057* which
says
"Target refresh requests *update the remote target of a dialog when*
* they are successfully processed*. The currently defined target
refresh requests are INVITE, UPDATE, SUBSCRIBE, NOTIFY, and REFER
[7])."
So your assumption is correct as per my understanding of above rfcs
that remote
target set should be updated only when 2xx is sent, whether the request
is reINVITE or UPDATE.
Best Regards,
Sachin Rastogi
On Sat, Jan 9, 2010 at 12:45 PM, hanifa.mohammed <
[email protected]> wrote:
> Hi,
> To update the remote target set, UPDATE/reInvite shall be used.
> Assume, reInvite is used.
> So, shall UAS update the remote target set, immediately after receiving
> the re-INVITE?
> Or only if 200 Ok is sent for this reInvite ?
>
> Assume, the sip stack receives the reInvite and intimates the
> application. Now, the
> application returns 4xx for some reason. So, in this case, will the remote
> target set be updated
> in the dialog?
>
> Here is a snippet from RFC3261 Section 12.1.1, for ur immed observation,
> that explains the initial INVITE,
> but for req within a dialog, it is not clear.
> The remote target MUST be set to the URI
> from the Contact header field of the request I assume that remote
> target set should be updated only when 2xx is sent, whether the request
> is reINVITE or UPDATE. Otherwise, the UAC may not be able to confirm that
> the
> target set is updated. And UAC should try modifying the remote target set,
> until 2xx is received.
>
> Thanks in adv.
>
> Best Regards,
> Mohammed Hanifa
>
> _______________________________________________
> 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
