@comtech wrote:
Asterisk/FreePBX 13
We have a pretty diverse environment with a few phone systems. We want to offer queue service via Asterisk/FreePBX without having to redeploy/reprogram the user's already working phones. I created a virtual extension in FreePBX (1111111111) there is no external routing to this extension and our SIP trunk routes 1111111111 to the Non-Asterisk phone system.
The FreePBX endpoint has a findme/followme setup for 1111111111#
This works and as long as the virtual extension is signed into the queue, queued calls will come to the phone on the other Non-Asterisk phone system.
The reason I made the FreePBX extension identical to the Non-Asterisk phone system, was to simplify queue call control. I was thinking that on an inbound route to FreePBX (2222222222) from the Non-Asterisk 1111111111, FreePBX would see the caller ID match with the virtual extension and when I input a feature code, it would apply it to the matching FreePBX virtual extension (1111111111).
When creating the 2222222222 inbound route to FreePBX, I noticed that the destination could be set to Feature Code Admin, but the sub options don't allow for *45, which will log the virtual extension (1111111111) in and out of the FreePBX queue.
Is there a way to work around this from within the GUI? Does this even seem like a viable approach to do what I want (1. answer FreePBX queues on external phones, and 2. giving those external phones a way to start and stop the queue calls)?
Thanks in advance for any insight or ideas!
Posts: 1
Participants: 1