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!

Voicemail pro Edit Play list option says "message has not yet been recorded" 1

Status
Not open for further replies.

HBPSYS

Technical User
Dec 18, 2008
103
GB
Hi I wonder if anyone can help me as I may be missing something. Have customer who is on Avaya IPoffice 11.1 I have a new application server running the voicemail pro. we sued the voicemail Pro client to record various greeting which by default are save to /opt/vmpro/wavs. These files seems to get saved as .opus .wav. Anyway they work fine when you call in to a menu for example to greeting is there and plays fine the issues is I a use the Edit Play list option in VM pro client and point to one of these .Opus files. When you call this module as select for example 1 to re record AAMenu1 aamenu.opus it says message has not yet been recorded even though it has and is working. It odes this for all of them.

I had a little play around and logged in with Putty and used chown -R Administrator /opt/vmpro so I could then use winscp to rename the file to aamenu.wav. This then worked and allowed me to put the Edit playlist at the file with this extension then the greeting was there and could edit in the normal way. Is this normal behaviour I've not done this for any other files as after changing this one it didn't quite behave right when browsing through the files and even though I had renamed it to .wav on the actually auto attended menu the file was still called aamenu.opus and it wouldn't let me enter it or browse to the file which was actually called aamenu.wav. Also in WINSCP the file was still listed as aamenu.waz but as the menu was looking for the file name aamenu.opus I though this would mean the AA menu wouldnt actually work but still does somehow.

I have also put the permissions back to chown -R vmpro /opt/vmpro otherwise vmpro client no longer has access to those files

Hope this makes sense and any help is appreciated

 
Just want to Say thanks to rlsabin this was indeed the case and I got Avaya to send me the patch. Applied within seconds rebooted and problem sorted
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top