VM Pro and Media Manager on Different Servers 3

[gknight1]

Everything is R11...

Custoemr had existing VM Pro running on a Windows server. We upgraded them to R11 and they of course lost their Contact Store and will now be using Media Manager. I can't seem to find a way to point the Media Manager to the VM Pro server to get the recordings. Is this even possible?

I guess i could move voicemail to the application server running media manager, but I am not 100% sure on how to migrate everything from a windows server to the app server.

 

[IPGuru]

migrate the VM to the app server.
should be a simple case of export & import call flows + copy custom wav files



Do things on the cheap & it will cost you dear

 

[gknight1]

thats what i ended up doing last night...

 

[gknight1]

well, things didn't go as planned. voicemail is not really functioning correctly. Voicemail works in the sense that the auto attendant works, user greetings work, but after I leave a message, the messages are never left on the phone. any ideas?

 

[TouchToneTommy]

Did you change any file permissions in order to get recordings onto the app server?

 

[gknight1]

I used the following. It appears the users could update their greetings though. I'm rebooting the app server shortly to see if that resolves it.

open Putty and connect avaya ipo ucmodule/avaya ipo server edition
Login as: Administrator
Administrator@10.130.22.19's passworduse administrator password)
Last login: Mon Jan 16 21:00:23 2017 from 135.27.170.185

********************************************
* Avaya IP Office *
* *
* WARNING: Authorised Access Only *
********************************************

Welcome Administrator it is Wed Jan 18 19:39:57 IST 2017
> admin
Please enter Service User:Administrator
Please enter Administrator password: ( Administrator Password)
Login successful
Admin> root
Password: (enter root password )
[root@005056A53A8A ~]# chmod -R ugo+rw /opt/

 

[janni78]

So you added +rw for everyone to all files and directories under /opt ?
Why on earth would you do that?

"Trying is the first step to failure..." - Homer

 

[gknight1]

Just to move the files over and because I don't know Linux well, and it worked.

How can I change it to give only root and Administrator +rw privileges?

 

[janni78]

Of course it worked since you gave everyone the rights to read and write whatever they want.
You basically wrecked the file rights on all Avaya applications.
Root always have rw rights to everything, but the vmpro files should be owned by vmpro, the same as if you look at other files. If they are owned by Administrator VMPro will complain.

"Trying is the first step to failure..." - Homer

 

[gknight1]

So I need to reinstall the ova or is there a way to fix it?

 

[janni78]

If you don't have a backup of the whole server, the only other way would be to compare all the files with another system at set the rights back.

The problem is that the way Avaya implemented this is really stupid.
You are supposed to use the File Manager in Web Manager but it will only allow you to save all files in one folder, and it deletes all files before it uploads them again, so any manually added files would be lost.
This has caused techs run all kind of commands on the servers that should never be done on a Linux dist, a properly programmed application shouldn't even start if it has to much rights due to security risks, now that's not an issue with Avaya apps

The only proper way to do this at the moment is to upload the files as Administrator via SCP to your home folder (/home/Administrator).
Then SSH in as Administrator, run admin, run root, change the owner of the files to vmpro (chown vmpro:vmpro file) and move them to the proper location /opt/vmpro/Wavs (/CustomPrompt)

"Trying is the first step to failure..." - Homer

 

[gknight1]

so teh reboot last night delivered the new messages that I left yesterday that the user never received. i tried leaving another message and its been 30 minutes and it hasn't shown up in the users mailbox.

 

[TheSmash]

Star for excellent explanation and work around.

ACSS (SME)

 

[gknight1]

thanks janni78 for the info, i think I got it all sorted out with your help. When I originally ran the command, I only did it for the opt/vmpro folder. I changed the owner using "chown hR vmpro /opt/vmpro" commmand and then tightened down the permissions it it all seems to be good now.