Hi Chaim,
In this case, Server should handle same REGISTER as this REGISTER
will be received on same transaction and Server will easily know that its a
retransmission rather then fresh REGISTER.
Thanks and Regards,
Vivek Takwar
On Thu, Sep 4, 2014 at 7:55 PM, Chaim Geretz <[email protected]> wrote:
> Greetings,
>
> Consider a case where the response to a REGISTER gets lost, UA resends the
> identical request.
>
> This means the callid and cseq remain the same.
>
> RFC 3261 10.3 (step 7) states that if callid is identical:
>
> ... the registrar compares the CSeq value. If the value
> is higher than that of the existing binding, it MUST update or
> remove the binding as above. If not, the update MUST be
> aborted and the request fails.
>
> This algorithm ensures that out-of-order requests from the same
> UA are ignored.
>
> ​Since CSeq is not higher than that of the existing binding, this also
> results in the retries to get ignored as well.
>
> Is the the client expected to increment CSeq if a response is not received,
> or is the server expected to detect re-transmissions and resend the
> previously sent response prior to applying the algorithm described in 10.3.
>
> Thank You
> Chaim Geretz
> _______________________________________________
> Sip-implementors mailing list
> [email protected]
> https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
>
--
Name | Title
GlobalLogic
P +x.xxx.xxx.xxxx M +x.xxx.xxx.xxxx S skype
www.globallogic.com
<http://www.globallogic.com/>
http://www.globallogic.com/email_disclaimer.txt
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
