MOH not heard in between 1st and 2nd queue announcements 1

[damascus9]

I'm on 8.1 (69) and MOH is no longer heard in between queue announcements after I made a subtle programming change in VMPro.
MOH was heard originally, when I programmed my Specific Start Points/Groups/Queued and Still Queued with Generic actions. Then my customer asked me to modify the queue announcements by giving them an option to opt out of the queue and leave a message. So I replaced the generic action with a menu action using the same entry prompt, and added a touch tone pointing to a leave mail action. That works, except now there is no MOH or ringback in between announcements, just silence. This is the ONLY change I made and this killed the MOH.

Does anyone know if it's possible to accomplish what my customer wants, using hunt group announcements and queue/still queued start points while preserving MOH between announcements?

As always, appreciate any input. Thanks guys.

 

[Westi]

dial *34 and listen if your MoH is playing at all

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[derfloh]

Sounds like the call never leaves the announcement start point and Voicemail pro is waiting for the caller to enter a menu option. Did you check what timeout you defined in the menu?

 

[damascus9]

Thanks for your replies, guys. Yes, MOH is definitely on. If I program the queue and still queued start points as generic actions, everything works and sounds as it should. But if I add a menu action and then connect the generic action to it, no MOH is heard, but the touch tone programmed in the menu action works, and the voicemail time is correct.

 

[Gunnaro]

Could it be that you have "syncronized calls" ticked?
That could make funny things happen when a Queued/still Queued contains an individual option or feature (like a Menu, ETA and POS).


Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[damascus9]

Hey guys, thanks for your input. I figured it out by moving around the order of the generic and menu actions. I took the entry prompt out of the generic action and inserted it in the menu action and added a timeout option to the generic action.

Half the problem is being able to test this without bothering staff during working hours!

 

[Gunnaro]

That's interesting; how did the call make the jump from Qeued to Still Queued if stuck in an endless timeout on a Menu in Queued.

The timer for second announcement should not start before the call is leaving the first.

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

 

[damascus9]

Sorry for the confusion, the jpg I uploaded is actually the "still queued" start point. The "queued" start point is just a generic action using the silent mc_01.wav file, then after xx seconds it goes to the still queued start point that does all the work. It repeats once then goes to voicemail. MOH is heard before and after the announcements.

You stop doing this for a few years and you forget everything!!

 

[derfloh]

One bad and good today ;-) That's what I thought... There is no way to leave the queued start point...

 

[Gunnaro]

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam