Absence management not working with external identity provider

Status
Not open for further replies.

kusig

Customer
Joined
May 18, 2015
Messages
24
Reaction score
1
We have integrated our self hosted 3CX sucessfuly with Google IdentityProvider to have a secure managed system.

What we observed now is, that users do not become unavailable anymore if they close their Webbrowser/PWA application. The user just stays "Available" within all busy fields of all other users.

The unavailability does only work if the "Logout" is manually invoked before closing the application. But of course nobody does this for sure, this would be a not helpful advice at all :)

The expectation is that the users with no connected phone (browser/pwa ..) are shown as unavailable at least (even better would be absent state but this is another story).
 
Hi there.
So in your case, the user is in the queue (it is logged in), and it will ring too even if the Web client/PWA is closed?
Did you by any chance register the 3CX mobile application on this extension too?
Or maybe you have a mobile number saved, and the option Ring my mobile at the same time is on too?
 
The user doesn't even need to be logged in to a Queue, just login to the system is enough and close the browser. It stays now forever Available for all other users and it could be even be called although it rings nowhere.

There is no mobile parallel ringing configured and no mobile client installed.
 
I can only think of the above and why it shows registered and green.
But if that is not the case, then I guess logs can show where it is registered, when you place the call.
 
Status
Not open for further replies.

Forum statistics

Threads
112,328
Messages
591,905
Members
165,483
Latest member
AshleyStokes