VQPlus Queue Callback generating multiple callbacks

I purchased the VQPlus commercial module and I’m trying to setup Queue Callback. I’m running FPBX 17 with Asterisk 21.4.3 and VQPlus 17.0.1.17.
I am able to make a call to the queue and request a callback. I am able to see the callback listed in the callback queue. Once a queue agent becomes available the callback is started and my phone is called. I press 1 to accept the call and I am delivered to the queue and then to the available agent. Before I am able to answer the initial callback call, I start receiving more callbacks to my phone. It appears there are 2 additional callbacks generated.

I have timeout set to 300s, retries to 0 and retry delay set to 300.

I have been looking in the /var/log/asterisk/qcallback_out.log trying to follow the events and trying to see if there are any hints. I can see where the call is added to the callback and then when it finds and available agent. Thoughout the logs I see a repeating series of messages:

2024-10-18 11:33 -05:00: We are updating the position of 1729268813.0 in the Q:604 To new position1
2024-10-18 11:33 -05:00: 1 We have free SlOTS in the queue 604
2024-10-18 11:33 -05:00: Last check time 1729269201 + 30 and current time1729269201
2024-10-18 11:33 -05:00: Found an Active(non paused) agent: Cloud Test 2 (Local/900@from-queue/n from hint:900@ext-local) (ringinuse enabled) (dynamic) (In use) has taken no calls yet (login was 0 secs ago)
2024-10-18 11:33 -05:00: Found an Active(non paused) agent: Cloud Test 2 (Local/900@from-queue/n from hint:900@ext-local) (ringinuse enabled) (dynamic) (In use) has taken no calls yet (login was 0 secs ago)
2024-10-18 11:33 -05:00: Calling back ‘xxxxxxxx60’ for queue 604
2024-10-18 11:33 -05:00: We have successfully placed a callback call 1729268813.0 and callback number is xxxxxxxx60 for the queue604
2024-10-18 11:33 -05:00: Last check time 1729269201 + 30 and current time1729269202
2024-10-18 11:33 -05:00: Last check time 1729269201 + 30 and current time1729269206
2024-10-18 11:33 -05:00: TypeError: Symfony\Component\Process\Process::__construct(): Argument #1 ($command) must be of type array, string given, called in /var/www/html/admin/modules/vqplus/Modules/Crud.php on line 680 in file /var/www/html/admin/libraries/Composer/vendor/symfony/process/Process.php on line 143
2024-10-18 11:33 -05:00: Stack trace:
2024-10-18 11:33 -05:00: 1. TypeError->() /var/www/html/admin/libraries/Composer/vendor/symfony/process/Process.php:143
2024-10-18 11:33 -05:00: 2. Symfony\Component\Process\Process->__construct() /var/www/html/admin/modules/vqplus/Modules/Crud.php:680
2024-10-18 11:33 -05:00: 3. FreePBX\modules\Vqplus\Modules\Crud->queueSettings() /var/www/html/admin/modules/vqplus/functions.inc/geters_seters.php:260
2024-10-18 11:33 -05:00: 4. vqplus_queue_settings() /var/www/html/admin/modules/vqplus/functions.inc/callback-daemon.php:19
2024-10-18 11:33 -05:00: 5. {closure}() /var/www/html/admin/libraries/php-asmanager.php:1615
2024-10-18 11:33 -05:00: 6. AGI_AsteriskManager->process_event() /var/www/html/admin/libraries/php-asmanager.php:349
2024-10-18 11:33 -05:00: 7. AGI_AsteriskManager->wait_response() /var/www/html/admin/modules/vqplus/functions.inc/callback-daemon.php:164
2024-10-18 11:33 -05:00: 8. unknown() /var/www/html/admin/modules/vqplus/queue-callback.php:25
2024-10-18 11:33 -05:00: Queue callback daemon started
2024-10-18 11:33 -05:00: Checking callbacks on queue 604
2024-10-18 11:33 -05:00: Queue =604 The entry details Array
2024-10-18 11:33 -05:00: (
2024-10-18 11:33 -05:00: [uniqueid] => 1729268813.0
2024-10-18 11:33 -05:00: [cbid] => 1
2024-10-18 11:33 -05:00: [callbacknum] => xxxxxxxx60
2024-10-18 11:33 -05:00: [tries] => 0
2024-10-18 11:33 -05:00: [queue_entry_time] => 1729268827
2024-10-18 11:33 -05:00: [linkedids] => Array
2024-10-18 11:33 -05:00: (
2024-10-18 11:33 -05:00: [0] => 1729268813.0
2024-10-18 11:33 -05:00: )
2024-10-18 11:33 -05:00:
2024-10-18 11:33 -05:00: )

I’m not sure if the “TypeError” is actually causing the additional calls.

Anyone else finding similar issues.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.