Discover Who Use Queue

[Hoygen83]

I have started managing a 3cx phone system already deployed.
I have a queue with extension 8000 that can't be edited since the system says that 8000 is an undesired number (I wonder how the people before achieved to create that queue).
So I made a new queue, 812.
If I call a number i see in event log only the event that my call enters the queue 8000
I desperatly need to find where is the setting that tells: if you call that number use queue 8000 and change it to 812.
Where do I find who is forwarding into a queue?

 

[JohnS_3CX]

On a 3-digit PBX you would not have a queue with 4 digits, any chance someone messed around and modified the system?

You can set logging to Verbose, restart the services and make a call to get it forwarded to 8000 (replicate the scenario).

Then download the Support Info file and open it using the 3CX Bin Log viewer if the normal Activity Log does not tell you what you need.
https://www.3cx.com/docs/3cx-log-viewer/

You can use the guide to isolate the call and only view what you want, or search for 8000 only (which may take longer).

I think you may need to consider deploying if this cannot be fixed, but lets see what you find first.

 

[Hoygen83]

Thank you very much.
I suspect that someone has done some trick with the digits when it was still possible.
I will normalize every queue.
Kindest Regards.

 

[JohnS_3CX]

You can contact 3CX Support directly if you wish to avoid risking any manual modifications. They may be able to remove the queue for you safely.

 

[Hoygen83]

Thank you,
I found out the desired settings.
I just switched queue and create a new one identical to the previous but with the correct digits.
But I haven't deleted the 8000 one.
I have another question.
If i update that 3cx system from 15.5 to 16 will there be problem caused by that extension (80009?

 

[JohnS_3CX]

For compatibility I would say you should make sure the system is not running in an unsupported case scenario (ie. with a 4 digit extension on a 3 digit PBX)

I can't say for sure because we don't test unsupported scenarios, but I do foresee it causing some trouble and would avoid it if possible.