After we upgraded the firmware to 2.1 we had a problem with people dialing our backdoor number and reaching the auto attendant.  When the caller either dialed the extension or dialed by name they never got the chance to record their message, but the mailbox would have a 30 second message containing nothing but dial-tone.

We installed VM Pro 2.1 yesterday, thinking there was a compatibility problem, which apparently there was.  Once VM2.1 was installed callers could use our attendant to leave messages by dialing the extension, but dial by name still produced the above results.  In our VM Pro the dial by name was set to some type of "Assisted Dial Ext" where it provided three options to move forward: answered, busy, no answer.  Busy and no answer then pointed to the users voicemail box.

I bypassed the Assisted Dial block and pointed to a "Dial Ext" (same way dial extension by number was setup) and that seemed to take care of it.

I appologize if none of that makes sense, I need more coffee. :)

Should be no big issues, Just insert the VM Pro disk and it will prompt you to backup, however I would suggest you export your .MDB before upgrading just incase it goes pearshape :)

0

No big changes.. I'm using custom variable in generic boxes ($CP1 for example) to point to wav files and now with the new release it doesnt support to have a dot (.) in the variable I just did some adjustments and it works fine...

Our switch is live since a full week with the 2.1 release and no problems at all so far it seems really stable and its really nice to be able to merge new users and hunt groups!

Many thanks, I have done the first upgrade without any problems, once again thanks for your input.

Francis999, do you have any extra documentation on using generic actions you can share with us?  How are you assigning values to those variables?

Peter

Ok just found the CPx: generic command in the new 2.1 toolkit.

Would love to get my hands on a full list of commands available via the generic action - one gets the feeling there are many cool things that can be done this way.

Peter

Just put de generic box, then in the Specific tab you define your variable that way :

CP1:Test

CP2:MyValue

then you can reuse theses inside the Entry Prompts actions like this :

C:\Program Files\Avaya\IP Office\Voicemail Pro\VM\Wavs\$LOC\$CP1.WAV

You could also put the value of this variable inside a user-defined variable to use it with the Test User Variable box later....

As far I know, you can use $CP0 to $CP9.   Each calls is a thread so you can assign different values to theses variable and it will be attach to the current call.  Once the call get out of the voicemail the variable content is cleared...

I use them a lot...more than user variable.

For the above to work I suspect you would need TTS, no?

If CPx where numeric though it should be fine without TTS.

No this way it doesnt try to TTS when there is a path specified it convert the variable value to text...

So if I put the value 1040 in a generic box for $CP1, and put the following string in a menu entry prompt :

C:\Program Files\Avaya\IP Office\Voicemail Pro\VM\Wavs\$LOC\$CP1.WAV

The voicemail convert it to:

C:\Program Files\Avaya\IP Office\Voicemail Pro\VM\Wavs\enu\1040.WAV

If I would have put $CP1 only in the entry prompt the voicemail would probably try to TTS it but since there is a path specified its looking for a filename.

I use that for multilingual mailboxes and menu in conjunction of some modules I've built.