Vectoring Question 1

[rgass01]

Came across a vector that had a go to step written that sends you to the same q-to step over and over in a loop:

Step 1 q-to skill 1
Step 2 wait 30 sec music
Step 3 go to step 1

does the switch realize that the call is already q'd to skill 1 and just treat it as a failed step or does it re-q the call and thus lose the person's place in Q? any other implications?

 

[berniebrown432]

Since it's reusing the same q-to step, nothing wrong happens. Once the call is queued it maintains its queue position and works its way to the top as calls ahead of it are answered or abandoned.

The only purpose that I could think of for this: on releases prior to CM 2.1, if the queue for the split/skill is full on the first pass, the call will not be queued (queue step fails), and you want to keep trying to get the call queued when a queue slot becomes available. The bad part is: if the unqueued call is in the 30 second wait cycle when a queue slot becomes available, new calls hitting the first step during that time period will be queued ahead of the waiting call.

Normally, just increase the queue size on the hunt group form. However, if there is a large quantity of splits/skills, the system's total available queue slots would have to be spread across all of them, so they may have relatively small queue sizes.

With CM 2.1 and later, split/skill queue sizes do not exist. However there still is a system limit of total queued call across all groups: 1,000 on CSI/S8300 platforms and 12,000 for S8500/S8700/S8710 platforms.

Bernie