GOOD NEWS iPBX 2026 Queue Callback beta2

[wardmundy]

I still need to figure out how to add them to System Recordings during module installation as the configuration section has a drop down menu to add any available recordings

Gemini to the rescue. See the bottom option... https://share.gemini.google/jOzc5IMzZHwY

 

[wardmundy]

well, that didn't work but I think this will but I can't test it at the moment:

cd /var/lib/asterisk/sounds/en/custom
wget https://filedn.com/lBgbGypMOdDm8PWOoOiBR7j/IncrediblePBX2026/CONTRIBUTORS/queue-press*-to-request-callback.wav
wget https://filedn.com/lBgbGypMOdDm8PWOoOiBR7j/IncrediblePBX2026/CONTRIBUTORS/queue-returning-your-call.wav
chown asterisk:asterisk *
cd ..
mysql -u root -ppassw0rd asterisk -e "INSERT INTO recordings (displayname, filename, description) VALUES ('Queue Returning Your Call', 'custom/queue-returning-your-call.wav', 'Added via CLI');"
mysql -u root -ppassw0rd asterisk -e "INSERT INTO recordings (displayname, filename, description) VALUES ('Queue Press Star to request Callback', 'custom/queue-press*-to-request-callback.wav', 'Added via CLI');"
fwconsole reload

 

[KNERD]

Yes, that is a start, The script will have to do all at as user asterisk.

 

[wardmundy]

@KNERD: I ran into a few problems. First, many Incredible PBX systems have a skyetel trunk enabled by default even though it's not registered. Disabling it and choosing another default outbound trunk never gets reset for the qcallbacks. So I guess the moral of the story for now is to make sure your Outbound Routes are properly configured and working BEFORE installing qcallback.

Another gotcha was attempting to set the qcallback options. When it attempted to write the settings to /etc/asterisk/queues_post_custom.conf, I got a message that the system was read-only even though it wasn't. The only way around this was to edit /usr/lib/systemd/system/php8.2-fpm.service, change ProtectSystem=full to false, then issue systemctl daemon-reload followed by systemctl restart php8.2-fpm.service.

Finally, when I called in with the queue answering calls, all I got was music on hold. Pressing * initiated the qcallback setup but the initial prompt message never played even though it played my calling phone number and then hung up. Then the return calls failed because they were sent to the disabled skyetel trunk rather than the default outbound route.

As for the recordings, I don't see a way to programmatically add them. I think users are going to have to download them to their desktop and then add them in the GUI using the Custom Recordings option. Otherwise, they never played even after manually re-enabling them in the GUI following the setup I listed above.

Hope this helps.

 

[KNERD]

@KNERD: I ran into a few problems. First, many Incredible PBX systems have a skyetel trunk enabled by default even though it's not registered. Disabling it and choosing another default outbound trunk never gets reset for the qcallbacks. So I guess the moral of the story for now is to make sure your Outbound Routes are properly configured and working BEFORE installing qcallback.

Another gotcha was attempting to set the qcallback options. When it attempted to write the settings to /etc/asterisk/queues_post_custom.conf, I got a message that the system was read-only even though it wasn't. The only way around this was to edit /usr/lib/systemd/system/php8.2-fpm.service, change ProtectSystem=full to false, then issue systemctl daemon-reload followed by systemctl restart php8.2-fpm.service.

Finally, when I called in with the queue answering calls, all I got was music on hold. Pressing * initiated the qcallback setup but the initial prompt message never played even though it played my calling phone number and then hung up. Then the return calls failed because they were sent to the disabled skyetel trunk rather than the default outbound route.

As for the recordings, I don't see a way to programmatically add them. I think users are going to have to download them to their desktop and then add them in the GUI using the Custom Recordings option. Otherwise, they never played even after manually re-enabling them in the GUI following the setup I listed above.

Hope this helps.

The for queue answering the calls and playing any announcement entering the queue, that is that is handled by the Queues module. This one does not have an intro announcement. Only an announcement for letting the caller know there is an option to have a callback instead of waiting. That starts playing after 1 minute of waiting at default. Once you press the callback key (default '*') it will play the number you are calling from. Since there is not enough words from Asterisk/FreePBX to tell the user what to do like press 1 if the number is good, or press 2 to call back to another number. Is there something wrong with that?

For the actual call back, I guess I could put a setting for which outbound route for each callback to use. Can you provide a call log for that event so I can look it over?


Also for the read-only error, can you give me the exact message? I have never seen this before.

I Will eventually get around to adding the recordings.

Thanks.

 

[KNERD]

/usr/lib/systemd/system/php8.2-fpm.service

I see the issue. I am using Debian 13 on this version which has PHP 8.4. I will see about making it compatible with Debian 12 also, but EOL is already getting close as it is two years away.

This is why we did not see a complaint from CPA Joe about this. He is also using Debian 13.