Warning calls being recorded on DDI 1

[sakom26]

Hi,
I have an issue to resolve for a client and can't think of how to do it.

They have calls coming into DDI's that go direct to users extensions and need to warn the caller before the user picks up the call that calls may be recorded for training and monitoring purposes.

The client has an Avaya IP office 500 V2 with a mixture of analogue, digital and IP phones
They have VM Pro in IP office mode (Not Intuity).
They use CCR to record the calls.

Standard Avaya call being recorded message is turned off as the client hates it.

I have tried using announcements on the user, but this also plays the message on internal calls and if they pick the phone up stops the message.

Does anyone have any ideas on how I can sort this for the client?

Many thanks in advance.

SAKOM26

 

[AACon]

let me ask you, does the users DDI end in the last 3 or 4 digits of the users extension, or is it random? If it does, there is a way to do it, pretty easily.

-Austin
ACE: Implement IP Office

 

[amriddle01]

Just replace the standard Avaya message with your own with the same file name



"No problem monkey socks

 

[AACon]

I don't think that is what he's looking for. He wants to warn the caller that the call is being recorded BEFORE it gets to the user. That standard message only comes up when the call is *currently* being recorded. I have a module built that will do exactly this, as long as the DDI/DID matches the users extension.

-Austin
ACE: Implement IP Office

 

[amriddle01]

I get you, it's an easy build in VM Pro using the $TARGET variable or if it rings a group put a queue message on 0 secs



"No problem monkey socks

 

[AACon]

How would the $TARGET variable know where to go? It's a DDI, it does not have a target, other than a vm module.
I just have a generic action stripping the $DDI to the last 4 digits to $CP0, then transferring to $CP0. Problem with this is that outbound CID is now broken unless you have a nice NS303555E (or simliar) ARS for the users.

-Austin
ACE: Implement IP Office

 

[amriddle01]

I meant $DDI, I built a module earlier with $TARGET in a few places, it's on the brain



"No problem monkey socks

 

[sakom26]

Sorry for the time in getting back to you.

Sadly the DDI is completely random to the extensions.
There are 60+ DDIs coming in over ISDN30 and SIP

The client only wants to warn on DDI calls as the calls to the main number go to Auto Attendant.

Many thanks in advance,
SAKOM26

 

[AACon]

If they really are random (who does that anymore?), then you'll have quite a bit of work ahead of you. You'll have to build a variable routing table...well quite a few actually. They only allow up to 15 variables per table. Put each DDI in the table, and route each to a generic call recorded message, and then to the proper extension. You'll have to link quite a few tables up to do the matching Have fun!

-Austin
ACE: Implement IP Office

 

[mforrence]

I just have a generic action stripping the $DDI to the last 4 digits to $CP0,

@AACcon - can you describe how you do this stripping? I have a need for this exact function. Thanks. Mike

 

[AACon]

Here you go!

-Austin
ACE: Implement IP Office

 

[mforrence]

PERFECT! Pink thanks coming your way.