Non-interruptable announcement as busy treatments in routing objects

[smile]

Hi All

Business unit want's to play some announcement (ads) for the calling party while they stay in queue and wait for the agent (music/ads/music again) . The main feature is that this announcement (only ads) should not be interrupted event if agent in target group becomes available.

I suppose about 3 different methods to solve this task, but can't chose more "reliable" and "accurate":
The first way is to use common objects, like "play announcement" and "selection". First we use "selection" with minimum 2-seconds timeout and then if there is no free agents, go through the red port to "play announcement" block. So, calling user will listen total duration of prompt and after the prompt will end, the next block will be "selection" again with usual "music/in_queue" treatment and long timeout.
The second way is to use  selectdn[] function to check the availability of target and if not - play prompt on the same manner. Then route interaction to target via "selection" or route/deliver function.
The 3rd way is in using GVP IVR - i hope that after URS send call to GVP port and lost the control on the call and can't interrupt treatment before GVP ends to pay it.

Did someone the same thing and which approach is more suitable? Thanks.

ps
environment: sip server+stream manager+gvp 7.6

[Timur Karimov]

Hi 
we use selection and play announcement in busy options.

WBR Thaler

[smile]

but this treatments will be interrupted if the agent becomes ready, isn't it?

[cavagnaro]

So everyone MUST listen those VG even when there are free agents or only if there are no free agents? If ALL then try to use the PlayMusic (trumpet). If second option well...have to smoke my brain a little bit more...

[smile]

Cavagnaro, if there is no free agents at the beginning of course. i've made this strategy already and tests were fine. I've used selectdn[] function to check the agent's availability and then (if nobody is free) - PlayMusic. Just wanted to know - may be someone done the same thing already, prons and cons for the different approaches

[kubikle]

All tree options will work. With third one (using GVP IVR) it should be taken into account that if URS lost control over interaction for long time (more then minute) there is possibility it will drop processing of such calls.  If so then playing with URS option call_tracking will be needed.

[smile]

Thank you, Kubikle!

[Fra]

[quote author=kubikle link=topic=6025.msg26194#msg26194 date=1290537300]
All tree options will work. With third one (using GVP IVR) it should be taken into account that if URS lost control over interaction for long time (more then minute) there is possibility it will drop processing of such calls.  If so then playing with URS option call_tracking will be needed.
[/quote]
It depends on which deployment you have - with GVP behind (URS centric), URS would be controlling the call.

Fra

[Timur Karimov]

[quote author=smile link=topic=6025.msg26185#msg26185 date=1290525183]
but this treatments will be interrupted if the agent becomes ready, isn't it?
[/quote]
of course =)

[cavagnaro]

Maybe what I'd try to do is:

1. Call Enters
2. Play announcement
3. Function catches SDATA about agents on ready
4. If 3 > 0 then go to a target object
5. else return to 2

and the Play Announcement maybe can use variables to play different musics.

[smile]

yeah, cavagnaro, this is the 4th method