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 TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Dual Language Prompts

Status
Not open for further replies.

wimico

Vendor
Jun 8, 2004
21
US
I want to front end an auto attd with the choice of English or Spanish and through experimentation have figured out how to get to the English or Spanish menu with a language selection module.
When I select Spanish, and through a menu prompt go to DBN, Get Mail, Leave Mail the prompts are in Spanish. However, if I hit the menu prompt to dial a known extension, the call transfers via $KEY and the default vm answer prompt is played in English instead of Spanish.
What am I missing?
Switch is 3.2(54) VM is 3.28.4
 
I guess it don't remember the setting for the specific call after leaving the VM Pro and ending up there again.
 
If the target users locale is set to english then the locale of the external call will be changed to english.
 
If you transferring to the extension via transfer actions, then the call has left the voicemail pro system totally. When the extension doesn't answer and the call goes to voicemail to leave a message, to the VMPro its seen as a new session and pickups the language setting of the mailbox user.

I'm not near a system at the moment but I would try doing the transfer with an assisted transfer action which then goes to a leave mail action for the same $Key. Hopefully the VMPro will treat it as a continuous session and use the same language throughout.
 
You can store the original locale into a $CP(x) variable and everytime the call goes back to vm copy the value of $CP(x) to the $LOC variable before palying any prompts.
Use a generic action and in the default action enter:
CP(x):$LOC were x = 0-9, later do the same but the other way around : LOC:$CP(x).
Maybe first test if there is any value in CP(x) otherwise you can end up with a empty $LOC wich may crash the VM Server and that is not what you want.
Create a condition with a compare and test if $CP(x) <> empty value. You can leave this out if you are sure the CP(x) has a value ( proper programming ), every call wich first hits VM must have a action to copy the $LOC to $CP(x).
The $CP(x) value will be valid during the lifetime of a call so if the call leaves VM Pro $CP(x) will keep its value for that call. Each call have its own $CP(x) variables.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top