Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Client does not send session refresh if it is the UAS session refresher #246

Open
GoogleCodeExporter opened this issue Jun 30, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1.Establish a chat or file session with the terminating client as session 
refresher, i.e. Session-Expires: <timeout_value>;refresher=uas
2.When sip session timeout expires, the terminating client does not send SIP 
refresh request

What is the expected output? What do you see instead?
The expected result is it should send a refresh request to refresh the session. 
 Currently, the client does not send session refresh request when it is the 
refresher.

What version of the product are you using? On what operating system?
2.5.11

Please provide any additional information below.
The UAS can have 2 roles, non-refresher or refresher.
However, seems it assumes UAS is always not the refresher.
In SessionTimerManager.sessionRefreshForUAS(), it only checks the timeout and 
terminate the session as a non-refresher, it doesn't not send session refresh 
if it's the refresher.

Original issue reported on code.google.com by mcd...@mcdull.us on 13 Mar 2014 at 8:30

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant