Hi
The RFC 4028 allows 2 simultaneous session timer
negotiations i.e with Re-Invite and Update. So the following combinations
are possible for session refresh request.
|<----Re-Inv------
|
|<----Update----
|<----Re-Inv------
|
|----Update---->
|----Re-Inv------>
|
|<----Update----
|----Re-Inv------>
|
|----Update--->
The session timers (session interval and session expires) will be started
based on the session expires header values in the 2xx response of refresh
request.
The cross over of the response messages is also possible(Response for the
first refresh request received after the response for the second refresh
request).
The session expires in the 2xx response must be validated by the stack as
per the rules defied in RFC4028.
What would be the most elegant way of handling such scenarios:
1. In these scenarios the stack must maintain the state for both the
refresh requests so that it can validate the session expires value in the
response
2. Do not allow a second session timer negotiation while one
negotiation is in progress.
Regards
Vinay
****************************************************************************
*************************************************
This e-mail and attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed
above. Any use of the information contained herein in any way (including,
but not limited to, total or partial disclosure, reproduction, or
dissemination) by persons other than the intended recipient's) is
prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!
****************************************************************************
*************************************************
_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
