Queue Pro (VQ Plus) Troubleshooting
- Nathaniel Halbrooks
Intention of this page to capture the troubleshooting steps to debug VQ Plus module issue.
Supported Module Versions
Troubleshooting information as mentioned in this page is applicable to below mentioned module versions or higher.
Vqplus v14.0.4.22 and v15.0.7.20
Sysadmin v14.0.38.23 and v15.0.16.16
Fwconsole Commands 14+
List Queue callbacks calls
"fwconsole vqplus list --queue=xxxx"
List the active queue callback requests in the queue callback --queue is an optional parameter to list from particular queue
fwconsole vqplus list --queue=2006
|ID |Queue |UniqueID |CBID |Position|Callback Num |QueueJoinTime |
|1 |2006 |1600939721.2445 |4 |1 |2222 |2020-09-25 10:10:23|
|2 |2006 |1600939725.2449 |4 |2 |2702 |2020-09-25 10:11:20| |
Trace the queue callback"fwconsole vqplus trace --uniqueid=xxxx"
List the callback daemon activity for the queue callback calls --uniqueid=xxxxxxxxx is an optional parameter to list for a particular callback
fwconsole vqplus trace --uniqueid=1600939721.2445
|DBID |Queue |UniqueID |CBID |Pos|Callback Num|QueueJoinTime |Channel |Event |Reason |Event linkedID |Event time|Event Result |
|2 |2006 |1600939721.2445 |0 |2 |2222 |1600939721 |SIP/2222-000000|Qjoin | | |2020-09-24 14:58:41| |
|5 |2006 |1600939721.2445 |0 |0 | | | |QLEAVE | |1600939721.2445|2020-09-24 14:58:59|Call having uniqueid 1600939721.2445 Remoed from 2006|
|9 |2006 |1600939721.2445 |4 |2 |2222 |1600939721 | |CBRequest | |1600939721.2445|2020-09-24 14:59:05|Queue posistion was =2 and we added to Virtual position 2|
|10 |2006 |1600939721.2445 |4 |2 |2222 | | |CBADD | |1600939721.2445|2020-09-24 14:59:05|CB added 1600939721.2445 from 2006|
|13 |2006 |1600939721.2445 |4 |1 |2222 | | |POSISTION | |1600939721.2445|2020-09-24 14:59:10|POSISTION 1600939721.2445(2222) changed from 2 to =1|
|15 |2006 |1600939721.2445 |4 |1 |2222 | | |CBDIAL | |1600939721.2445|2020-09-24 14:59:10|Dialing uniqueid 1600939721.2445 from 2006|
|16 |2006 |1600939721.2445 |4 |1 |2222 | | |CB-DIAL-SUCCESS| |1600939721.2445|2020-09-24 14:59:10|CBDIALSUCCESS 1600939721.2445 from 2006 Try num=1|
|18 | |1600939721.2445 |0 |0 | | | |CB-DIAL-ATTEMPT| |1600939750.2479|2020-09-24 14:59:10|Dial Attempt ID 1600939750.2479|
|21 |2006 |1600939721.2445 |4 |2 |2222 | | |POSISTION | |1600939721.2445|2020-09-24 14:59:20|POSISTION 1600939721.2445(2222) changed from 1 to =2|
|30 |2006 |1600939721.2445 |4 |1 |2222 | | |POSISTION | |1600939721.2445|2020-09-24 15:00:31|POSISTION 1600939721.2445(2222) changed from 2 to =1|
|35 |2006 |1600939721.2445 |4 |1 |2222 | | |CBDIAL | |1600939721.2445|2020-09-24 15:01:50|Dialing uniqueid 1600939721.2445 from 2006|
|36 |2006 |1600939721.2445 |4 |1 |2222 | | |CB-DIAL-SUCCESS| |1600939721.2445|2020-09-24 15:01:50|CBDIALSUCCESS 1600939721.2445 from 2006 Try num=2|
|37 | |1600939721.2445 |0 |0 | | | |CB-DIAL-ATTEMPT| |1600939910.2641|2020-09-24 15:01:50|Dial Attempt ID 1600939910.2641|
|45 |2006 |1600939721.2445 |4 |1 |2222 | | |CBDIAL | |1600939721.2445|2020-09-24 15:04:20|Dialing uniqueid 1600939721.2445 from 2006|
|46 |2006 |1600939721.2445 |4 |1 |2222 | | |CB-DIAL-SUCCESS| |1600939721.2445|2020-09-24 15:04:20|CBDIALSUCCESS 1600939721.2445 from 2006 Try num=3|
|47 | |1600939721.2445 |0 |0 | | | |CB-DIAL-ATTEMPT| |1600940060.2772|2020-09-24 15:04:20|Dial Attempt ID 1600940060.2772|
|50 | |1600939721.2445 |0 |0 | | | |CBDEL | |1600939721.2445|2020-09-24 15:06:10|Removed uniqueid 1600939721.2445 from CBtable|
|51 |2006 |1600939721.2445 |4 |0 |2222 | | |CB-REMOVED |MAX Retries |1600939721.2445|2020-09-24 15:06:10|CB removed for uniquied1600939721.2445| |
Field | description |
|---|---|
DBID | The table id of that particular callback daemon log entry DB table. If we need to see more details, then we can login to database and fetch the respective DBID row.
|
Queue | Queue number |
uniqueid | Unique id of that particular call |
CBID | callback id |
Pos | Position of that particular call during the callback process |
Callback Num | Callback Requested number |
Channel | Channel name of the call |
Event | Call back related event information. CBADD → callback called added CBDIAL → Callback Call Dial CB POSITION -> Position of the call that particular event time CB CBDEL -> Deleted from callback requests CB QRejoin → Callback call is successful and rejoined in the queue QLEAVE -> call left from the queue Qjoin → call joined the queue CBRequest → callback requested |
Reason | The reason for that particular event ( if any) |
Event linkedID | The unique id of the call occurred with the event eg: CB |
Event time | Time of that particular Event occurred |
Event Result | This some explanation of that particular event |
|
|
Callback Daemon log Retention policy
In advanced settings we have the below settings for log retention. Value can be configured between 5(min) to 30 days(max).
VQ Plus Support Logging
While reporting an issue to Sangoma Support team or Engineers, Please do ensure to capture the below logs under "Sysadmin → Support → Queue call back logs".
This option will be visible only if "licensed" VQ Plus module is installed in the system.
You might want to enable other logs depends on issue.
