Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Using the $TAG feature from the ICR Tag in a VM Pro module 3

Status
Not open for further replies.

geoffjersey

Technical User
Jul 18, 2016
17
JE
I have found an old reference to using this 'feature', but haven't had any luck getting it to work.
The customer I have is requesting that all DDI are played the same corporate message, before transferring to the extension destination associated with the DDI.
I have sent the DDI to a VM module & entered the .wav in the specific entry tab. I have entered the variable $TAG in the destination field - saved & made live & tried it.
The call routes to the VM pro module OK & plays the message, it goes to the transfer - all you hear then is a new dial tone. I have also tried entering a generic action before the transfer and using the $CPxx to move the $TAG value into it, before the transfer - still no joy.
Has anyone got this to work ?
BTW: the customer currently on R9.0
Thanks
 
What service pack of R9.0? For instance R9.0.0 is junk and R9.0.12 is OK. Does IP 500 V2 version match the VM Pro version?

The more information you provide the more likely you will get help.

The truth is just an excuse for lack of imagination.
 
Don't forget to enter the final destination number in the TAG field in de incomming call routes.
 
Is there a 1:1 correlation between the DDI and the destinaton? For instance, does 213-555-1000 go to Ext. 1000, and 213-555-1001 go to Ext. 1001? If so, point the ICR to a VM module, play the corporate message, then set $CP0 to the last 4 digits of $DDI, and transfer to $CP0
 
Thanks for the replies you guys - much appreciated.
My apologies for not giving the full info.
In response:
critchey - R9.0.12.0 build 1006 & the VM Pro version matches
Okkie26 - I had entered the final extension in the Tag field in the ICR tab
TouchToneTommy - sadly, not a 1:1 correlation (they have x3 sites in their SCN with a customer-chosen extension plan for each site) that doesn't match their DDI ranges.

Thanks again for your thoughts and suggestions
 
What you can try to do is enter $tag in the announcement tab. That way you will hear the 'destination' you entered in the tag field of the icr..
 
Hold on. I see it.

The $TAG is added in release 9.1, not available in 9.0..




 
How many users? You can use Variable Routing action to match up to 15 items per action, and connect each to a transfer action. Connect No Match to another Variable Routing action to test another 15 items. If you're only talking 50 or so users, that's not too bad. Match to $DDI
 
Okkie26 - you're a star !!
I've bashed my head against this for a while - but couldn't find what version is was available in.
Sadly, the customer is staying on R9.0.12 for now, because they make substantial use of Phone Manager Pro...they've looked at One-X and don't like it - go figure ;-)
Looks like we're in a no-win here for a while !!
Thank you for the sanity check
Best regards,
 
Thanks TouchToneTommy for your insights.
They've >100 staff at the main location with ~125 DDI - ~70 at the second location with 100 DDI.
I could always run a load of indivual VM modules (see my previous post to Okkie26) about versions etc
Thank you for your help
regards,
 
Just route all calls to a shortcode, for example if your extensions are 4 digits, route to 95extn in ICR.
Make a shortcode 95XXXX, Voicemail Collect, "Welcome".
In module play message and use Generic to pick out the last 4 digits and transfer to that.

"Trying is the first step to failure..." - Homer
 
Ah, missed to point out that you use $TARGET to know which shortcode was used.

"Trying is the first step to failure..." - Homer
 
Thanks Janni78 - I'll look into this method to get me around the release version versus $TAG issue, as an interim solution for them.
 
Hi jannie,

This results in pretty the same like shortening $DDI in VMPro.

Best would be to use a database that translates the dialed DDI against the real target.

Think about a kind of fallback in case the database should not be accessible. And also in case that VMPro doesn't work.

IP Office remote service Fixed price SIP trunk configuration: CLI based cale blocking: SCN fallback over PSTN:
 
It's the same if DDIs matches extensions, if they don't well =)

Why would a database be the best way to do this?
Just seems like a lot of overhead.

"Trying is the first step to failure..." - Homer
 
Depends... If you only have a few DIDs where the internal number differs you can create a module with routing by variable. If more are different a DB may be better.

With embedded AA you can play a greeting and if the menu gets no valid input (timeout) the fallback target in ICR is used. Don't know if the same would be possible with VMPro. Guess not. So using the short code option can be the better way...

IP Office remote service Fixed price SIP trunk configuration: CLI based cale blocking: SCN fallback over PSTN:
 
Hi Janni78,
I did as you suggested and created the following :
Had an ICR that pointed to a shortcode 95XXX (3 digit extensions used by customer).
Created the shortcode 95201 with VM Collect and telephone number "Welcome"
Created Welcome module on VMPro, added the Generic - String Manipulation, select variable : $TARGET, Select variable for result as : $CP0, from position 3, position index 3
Added Transfer action with destination as $CP0.
The calls routes through properly (plays the welcome message in the entry prompt of the transfer action), but when the Transfer action happens, it just leaves the line 'open' no dial tone, no ringing...
GOK what I'm missing !
Have I left something out ?
Thanks again for your help with this
 
Update on progress (or lack of !):
Using the above process, I have checked the logs & it has thrown this up :
Exception has occurred in IVRNodeplayer:: PerformActionString (.\ivrnode.cpp[5680])
Anyone know how to fix this ?
Many thanks
 
Hi Okkie26,
tried that - but the inbound DDI isn't the target of the extension number I want to transfer it to (ie not 1:1) so the last three digits are not their extension number.
I had hope that the $TARGET variable would containing the value of the shortcode I had entered in the destination field of the ICR.
Not sure I can fix this now - I can't find the 'right' variable that I can use to extract the desired extension to use in the transfer action.
Thanks anyway
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top