Provide Recording to D.I.D. #'s

[bdaphoneguy]

Got a weird one here. Customer just rolled out Call Recording and wants to ensure all callers are aware thier calls are being recorded. Basic users in ACD Path which is easy with RAD's, however users have D.I.D.#'s that they also want to recieve a notification. I have used Path's for direct numbers with a common RAD Greeting and Interflow to users.
Heres where the problems start.
1. Using Routing, callers internally do not get greeting calling extensions which is Great. Calls being transferred however do which is not Great.
2. Interflowing calls to second extension on sets is Great and using Name Tag Hunt Groups, messages can be taken in correct mailboxes, however using Exchange this does not work.
Maybe I'm over thinking it, any suggestions?
3300ICP Rls. 9.0 platform.

 

[DoubleUT]

This can't be done with the 3300, you might want to look at Nupoints Call Director or IQ.

 

[boycey9]

I would stay away from IQ if possible as the programming to get this to work is massive, You have to program each DDI up as a condition on the 6160 each linking to the next one. If one is accidently changed then all the ddi's after this condition will fail.
It does work but I wont go in to it in great detail as Its an expensive option and you probably wont go for it just based on your requirement.
Im no expert on Nupoint so will leave for others to comment on this.

 

[dryaquaman]

How about this:
In the trunk service form insert a digit on the DID's (i.e. 7)
The DID then becomes 7+DID.
Now, create a phantom ACD group as 7+DID.
Play the "your call is being recorded" message after 1 second.
Then interflow to the actual number after the message plays. (this is a timer).
Be sure to have enough RAD ports to play multiple messages at same time or the caller may only hear "Your call...." or no message at all.

For any number that you don't want to play the message for, set up a system speed dial to route the the actual number.

The big down side of this is that you have to do this for every DID.
That's a lot of work.

Dry Aquaman.

http://www.university-music-on-hold.com

 

[bdaphoneguy]

Thanks for the thoughts. At present I have a Path created for the DID (simple 4 digit number)users. By Reroute Always (DID Originating Device) I am able to send the external calls to the Path's with the common RAD with "Your being Recoded" greeting and interflowing to a Phantom DN labeled "External Call" on the 5340IP sets.Client loves the second line indicator for external calls. Works great withe the Phantom being a member of the Primary DN's Personal Ring Group. Call goes to EMEM voicemail and recieves correct greeting to leave message.
The problem now is that the users are "Exchange" members and not EMEM.
I have replaced the Personal Ring Group with Name Tag Hunt groups to force the call into the Primary DN's voicemail box without success.
Any-one use the Name Tag trick for callers to forward in an Exchange users mailbox?