Solved 3 ext can't login to call queues v 18 / v18 sp 1

Status
Not open for further replies.

Clint Reed

Silver Partner
Advanced Certified
Joined
Oct 26, 2017
Messages
60
Reaction score
13
Hello All,

Running 3cx v18 sp 1 on debian 10 hosted in AWS. We have 3 extensions that can not login to the call queues. One being mine own ext. I have tried the following
1. Updating to SP 1 last night, still fails.
2. Logged off any applications I was logged on with my extension number , removed myself from all the call queues, Add myself back to 1 queue. Restarted and update to the new windows app and test, still fails to login.
3. Closed the Windows app and tested from the webclient and test in the android app. Still fails to login to the queue.

For the option of logging in to the queue, tested using the Q button in the cell app, In the webclient>top left click person icon and select login to queue. and it switches to log out of queue - but fails. This option will toggle from login to log out but has no affect
Next option was open the Panel click on the Queue and click Login OUT OF QUEUE - has no effect - it DOES NOT switch to Login to queue like other extensions - stuck on Logged in. I can change the status of other extensions, but not mine or the other 2 ext that are stuck.

Thanks
Clint
EasyIT
 
Hi @Clint Reed,

Can you try to dial *62 and see if the extension logs into the queue? The three extensions may have been globally logged out using the Dial Code (default: *63 - log out of queues, and you can use *62 - log in to queues).

You can check the defaults from the Dial Codes panel in the Management Console under >> Settings >> Dial Codes.
 
I added myself back to a few queues, dialed the code to log out, and then the code to log in. It says if logged in but is not and can't answer calls.

I also created a test extension it appears to work correctly and can login and out of queues OK.
 
I added myself back to a few queues, dialed the code to log out, and then the code to log in. It says if logged in but is not and can't answer calls.

I also created a test extension it appears to work correctly and can login and out of queues OK.
Check for explicit logout
 
  • Like
Reactions: VasilisV_3CX
So from a new extension, you can answer. That's good.

I was about to write what @ConceptsWeb beat me to it (Cheers!), check that you're not explicitly logged out (individually logged out of a queue rather than globally). Open the Panel, select the queue and make sure you're logged in. You can do this as shown in the picture below:

1640009369445.png
 
  • Like
Reactions: Evolute IT
I ended up deleting my extension as it was the oldest and recreated it, Now all 3 extensions can login and out of queues. Now sure why it was hung and why it effected to other ext but happy it's fixed.

Thanks
Clint
 
  • Like
Reactions: Evolute IT
Glad to hear that you got it working @Clint Reed, remember that for quick testing, you can always copy the extension (eg create extension 205 off of 101), delete the old extension (101) and then copy 205 and create a new 101 with the same options as it previously had. Delete 205 and you're good to go.

If you encounter the same problem, you know the error is related to the extension's options / rights.
 
  • Like
Reactions: Clint Reed
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet