05-03-2016 05:10 AM - edited 03-17-2019 06:04 PM
Solved! Go to Solution.
05-03-2016 05:13 AM
You should be getting a message saying the session is expired and do you wish to renew .Aren't you getting this ?
05-03-2016 05:13 AM
You should be getting a message saying the session is expired and do you wish to renew .Aren't you getting this ?
05-03-2016 05:16 AM
I only get message that session is expired - Jabber is still connected, it seems but is not registered anymore. You have to shutdown and start jabber again.
When does this timeout occur ? is there a time to check Setting ? We have SSO - when a session is timeing out - customer assumes that it should reconnect automatically.
any idea ?
Kind regards
05-03-2016 12:03 PM
05-03-2016 12:08 PM
I have the same issue...I am hoping there is. I just opened a ticket with Cisco asking about the "Token Session Timeout". I found that you can change this in the documentation but they do not mention where to do so. I will keep you posted once I hear back.
12-04-2017 11:00 PM
Hi!
I hope you are doing well.
Have you found a solution for this issue ?
05-03-2016 11:38 PM
12-05-2017 01:25 AM
Hi
I couldn't find number 3. Application session timeout Where to set : CUCM Recommended Value - 30 Minutes ( default) from CLI set webapp session timeout 30.
Please ket me know where is it in CUCM 11.5.
Thanks!
Shachar
12-05-2017 01:57 AM
12-05-2017 04:51 AM
12-05-2017 08:53 AM
Hi,
Jabber login has nothing to do with this command.
what do u mean by OAuth Token?
regds,
aman
12-05-2017 11:14 PM
Hi Aman,
This discussion is regarding Jabber in SSO deployment and we have the same problem as reindl_mc had.
We have deployed Jabber with SSO at one of our customers (CUCM 10.5 / ADFS).
After approximately 6 days from each login that a user is made the Jabber or the ADFS ends the session.
In the Jabber's Error Notifications we can see the "session has timed out"error.
A.M.Mahesh Babu mention couple of things that can be relevant:
We should be getting a message saying the session is expired and do you wish to renew - We don't get that message
He also mention the 4 timers that can be relevant:
ADFS
- IDP Idle Timeout
- IDP Absolute Timeout
CUCM
- OAuth Token
- Application session timeout
Regarding the ADFS - I found the IDP Idle Timeout that was configured to 8 Hours
But not the IDP Absolute Timeout (Which could defanatliy could be the reason for this problem)
regarding the CUCM i couldn't understand how is the Application session timeout configuration is related to the SSO at the Jabber
Best regards,
Shachar
12-06-2017 01:40 AM
Hi ,
I won't be able to help u on the same.
I suppose u are already in touch with Cisco TAC Engr. So, u can take assistance from him.
regds,
aman
02-09-2018 05:17 AM
Did you find the answer to this? I keep getting error CJ:1000:606 Session Timeout as well. I need to manually reextend my session every 60 minutes, which I figure should be done automatically in the background.
10-10-2023 01:37 AM
Hi, we are getting same error code CJ:1000:606 and CJ:2100:2. In our Environment, we have the Jabber 12.9 and 14.2 versions. The error report is emananting from Clients with Version 14.2.0.58008. Please, let me know how you were able resolved the issue
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide