Centralized Voicemail vs Distributed, can anyone clarify this for me?

[Cat5Jive]

Good evening gents,

I have two IP Office units, 9.0, both with Preferred License and SCN installed and both IPOs connected via VPN.

My initial understanding was that I could set up one IP Office as "Voicemail Pro" and the 2nd as "Distributed" and all voicemails would sync between both servers via SMTP so that I would have independent IP Office voicemail systems in case connectivity was lost. After a lot of fooling about, I could not get this configuration working correctly.

My upstream Avaya support has since informed me that "Centralized" is my only option, despite my original understanding. I have configured for Centralized and have it working, but have already invested in the VM Pro channel licensing at the 2nd location which is now wasted. I would prefer to have a Distributed configuration based on my understanding.

Can anyone clarify how Distributed should actually work, and can anyone point me towards documentation on correct configuration? The help file is lacking in this regard.

Thank you so much!

C5J

 

[tlpeter]

You should use distributed.
The install manual for VMPro has this covered but it is not easy somehow.
You will need to use FQDN's and not IP addresses but that does do the server edition too so you could try that.


BAZINGA!

I'm not insane, my mother had me tested!

 

[IPGuru]

it took me some time to get a Distributed/centralised server setup working

Is your VM running on windows servers or the Application server?

For windows IIS & SMTP need to be set-up correctly BEFORE installing the VMPro service, it cannot be retrofitted.

On application Server this Linux equivalents are already in place & correctly configured
(just one more reason why Application server is the preferred option for installing VM pro)

once installed you need to configure the smtp services in the VM pro client & ensure they have the correct email addresses to communicate.
IIRC they are vmsyncmaster@<fqdn of server> for the central VM & vmsyncslave@<fqdn of slave>

Ip addresses are acceptable as the FQDN of the server.



A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear