Vectors are fun!! When they work..

[RedTech443]

I have a fun one with a customer.

We have a vdn going to a fairly standard vector that sometimes music on hold does not work and the vector processes differently. You can see in the "Not Working Trace" below that it skips the step for music for some reason, this is happening in multiple vectors and I am starting to wonder if the card in the TN2793B is on its way out..

CALL VECTOR

    Number: 14               Name: (Test Hunt)
Multimedia? y      Attendant Vectoring? y    Meet-me Conf? n           Lock? y
     Basic? y   EAS? n   G3V4 Enhanced? y   ANI/II-Digits? y   ASAI Routing? y
 Prompting? y   LAI? n  G3V4 Adv Route? y   CINFO? y   BSR? n   Holidays? y
 Variables? n   3.0 Enhanced? n
01 wait-time    0   secs hearing silence
02
03 announcement 1500
04 goto step    10            if staffed-agents   in split 14           =  0
05 queue-to     hunt-group 14   pri m
06
07 wait-time    10  secs hearing music
08
09 goto step    5             if unconditionally
10 announcement 1505
11 stop
12

[b]Working Vector Trace[/b]

list trace vector 14
time
vec st data

15:18:43 TRACE STARTED 07/19/2023 CM Release String cold-01.0.974.0-27607
 15:23:04 ▸▸ ENTERING TRACE cid 1043
 15:23:04 14 1 vdn e7889 bsr appl 0 strategy 1st-found override y
 15:23:04 14 1 AVON: 7889 AVRD:
15:23:04 14 1 wait @ secs hearing silent 
15:23:04 14 2 <blank>
15:23:04 14 3 announcement 1500
15:23:04 14 3 announcement: board 084V9 ann ext: 1500
15:23:07 14 4 goto step 10 if staffed in skill 14 = 0
15:23:07 14 5 queue-to
15:23:07 14 6 <blank>
15:23:07 14 7 wait 10 secs hearing music
15:23:07 14 8 hear moh port 01408022
15:23:14 14 8 LEAVING VECTOR PROCESSING cid 1043
15:23:14 14 8 TRACE COMPLETE cid 1043

[b]Not Working VECTOR TRACE[/b]

list trace vector 14
time
vec st data
LIST TRACE
15:17:52 TRACE STARTED 07/19/2023 CM Release String cold-01.8.974.0-27607
15:18:00 Ø Ø ENTERING TRACE cid 904
15:18:00 14 1 vdn e7889 bsr appl 0 strategy 1st-found override y
15:18:00 14 1 VDN: 7889 AVRD:
15:18:00 14 1 wait @ secs hearing silent
15:18:00 14 2 <blank>
15:18:00 14 3 announcement 1500
15:18:00 14 3 announcement: board 004V9 ann ext: 1500
15:18:03 14 4 goto step 10 if staffed in skill 14 = 0
15:18:03 14 5 queue-to
15:18:03 14 5 Local Agent Preference=n
15:18:03 14 5 Agent Login ID: Logged in at station: 7492
15:18:03 14 5 LEAVING VECTOR PROCESSING cid 904
15:18:03 14 5 TRACE COMPLETE cid 904

 

[ZeroZeroOne]

In your Not Working Trace, the call is immediately sent to an agent as part of the Queue-to in step 5. The call never gets to steps 6 and beyond.

That's expected behavior for when an agent is available.

Edit: You also don't have to circle back to the Queue-to step. Once the call is "in queue" then it remains waiting for an available agent even if other steps are executed (Route-to will stop the queue, however).

If you re-queue then that call could potentially be placed at the BACK of the line if there are multiple callers waiting. Just go back to the wait-time step.