bsavery

Since your doing a route to number to reach the hunt groups, once it hits that line, vector processing is complete and anything after that point will never be reached.

This is good though (for your situation)... on your hunt group form, add a cover path to voicemail. If it's not an option, you might have to set Vector? to No.

When Vector is set to Y, the vector controls the hunt group and then you'd use Queue To (hunt) instead of Route To (hunt extension) followed by the wait and messaging statements you discovered. You'd have to split the lines up though... something like this...

1 Wait 0 hearing silence (personally, I like to use 2 secs of ring)
2 Collect 1 digit after announcement xyz
3 goto step 7 if digit = 1
4 goto step 12 if digit = 2
5 wait 4 seconds hearing silence
6 goto step 2 if unconditionally (or other no button push option)
7 queue to skill xx (Hunt Group 1)
8 announcement abc (I like to have a sorry for the wait message)
9 wait 30 seconds hearing music
10 messaging split 99 for extension xx
11 stop
12 queue to skill yy
13 announcement abc
14 wait 30 seconds hearing music
15 messaging skill 99 for extension yy
16 stop

The only downside to this... the phone MUST be manned or off-hook when not manned. The switch doesn't know when there's no one there and will route a call to the phone anyway, where it will ring forever.

Good Luck!
Bob

will

Cool. Good info Bob! Unfortunately, the person responsible for this site previously is no longer with my company and never connected the vm system to a modem or the network. I can only remotely hit the G3. I'll have to engage our support vendor to enable remote vm access.


thanks,
Will