VM Pro DDI to message to user 7

[Mr Lee]

Hi All,

I have an IPO500 and VM Pro. The customer would like any user DDI's to play a message before routing to off to the user, the same message is to be played for each DDI /user.
Is this possible ? I was told we could send all calls to a module then play a message but how do I then get to the users?

Any advice is appreciated.

Lee.

 

[sizbut]

Pretty easy if the DDIs digits sent match the user extension numbers in some way.

Create a module which plays the message as part of the start action greeting and then uses a Transfer action with the destination $DDI.

If they don't directly match, lets say DDI 123 goes to extension 4123 it can still be done with some Generic action code.

If the DDIs don't match the target extensions then its probably an annoying series of Test Variable actions for each possible DDI with a transfer to the matching extension for each match.

Stuck in a never ending cycle of file copying.

 

[Okkie26]

In the ICR, enter the destination in the label field, route all ICR to one specific VM pro startpoint.

In that startpoint, play the greeting, and forward the call to $TAG

 

[Mr Lee]

Thank you both for you're replies,

With over 400 DDIs that do not match the extension (50 do) this was never going to a quick fix.
I have tried the $DDI but this then just sends the call out then back in on the DDI and $TAG sends the call out to line
I have set DDI 01234567890 ( user extension 890) to VMDIRouting > Start Point DDIRouting (plays my message) > Transfer/Specific / Destination / $DDI and then tried $TAG and also previously $TARGET ( $TARGET was suggest by our disti tech). Is the call flow correct ? I guess I am missing something.

Is there a way VM Pro can send the call back to the ICR Fallback Extension ?

Many thanks again,
Lee

 

[sizbut]

Okkie's suggestion is excellent (I've gave it a star, very clever use of the system).

It looks like the DDI you are receiving is the full external number. In that case, yes, transferring to $DDI would just send the call out of the system as an outgoing call that then comes back in. You would need to do something in the callflow to prune the leading digits of the value of $DDI (a Generic action that does String Manipulation to save the last 3 digits of $DDI as $CP0 and then transfers to $CP0).

The fact that an external call is made when you tried the $TAG method suggests too many digits in whatever you set for the value of $TAG.

In both cases, have the callflow temporarily use $TAG or $DDI as a greeting for the Transfer action so you can hear what value it thinks it is transferring to to help work out why they aren't matching extension numbers.

As for fallback, before the Transfer, you could apply a Test Variable action to which ever variable contains your transfer number to check it matches an extension or group number. If it does link that to the Transfer. if it does link it to a Transfer to whatever number you want used as the fallback.


Stuck in a never ending cycle of file copying.

 

[Mr Lee]

Thanks to Okkie and Sizbut, I have the DDIs that match the extension number routing successfully as you suggested.
For the non matching DDIs, can I have multiple DDIs in the test variable or do I need a Module / Test Variable for each DDI ?
Cheers, Lee.

 

[joe2938]

I would think a close match/wildcard might work

 

[Mr Lee]

Thanks All,

I now have this working as suggested, using Variable Routing ( from Telephony Actions - for those who like me are fairly new to VM Pro) with each DDI ( or at least a few for testing) listed within it then Transfer (again from Telephony Actions) to each individual extension as required.
Cheers,
Lee.

 

[Okkie26]

I would still use my method, cause it is easer to maintain.

You only need to make one new DID for each user instead of making a DID and a call variable in VM pro.

 

[sizbut]

Sadly between Okkie26s excellent method and mine the only other option I can think of would be using the Voicemail Pro database option.

I have had (a long time ago) a Windows based VMPro using the ODBC connector to look up simple number matches in an Excel spreadsheet.

Stuck in a never ending cycle of file copying.

 

[Mr Lee]

Okkie, I can't get your method to work, I am clearly missing something.
If all DDI's are routing to the same module then Transferring to $TAG how is the extension determined ?
To clarify I have a DDI pointed to VM:Routing. Then the start point plays the message then transfer to $TAG. Nothing else, what am I missing?
Thanks again.

 

[Okkie26]

In the incomming call route. Add the destination in the tag field.

 

[Mr Lee]

I have tried it with Tag as the extension I want it to go to but it is still trying to route the call via ARS

 

[Okkie26]

In the startpoint, annoucement tab. Add new announcement and just enter $TAG here.

Now when you call the callflow, VM pro will play the TAG value, which should be the destination. (200 in my example)

 

[Mr Lee]

I have now set this up on another site and it is working exactly how I want it, just you ( Okkie26) have described in his first reply.
I have copied and even exported the module from the working site to the non working site.
I have found that the $Tag option is not listed if I look in "System Defined Varables" within Telephony Actions > Transfer > Specific > Destination - but is there on the working site.
The non working site is on 9.0.5.0 the working site is on 9.1.8.0 is this a version issue or do I need to enable the variables somehow ?

 

[Okkie26]

No, you need to upgrade..

$TAG was introduced in 9.1

 

[Mr Lee]

Now upgraded to 9.1 and it is working just as Okkie has described and it's very easy when you have the knowledge.
Thanks Okkie and Sizbut I really appreciate you're help and patience, you have saved me from many hours setting this up the long way.