Ah the joys of distributed voicemail. We've been using it for ages since we were one of the original beta sites for it but not it is broken. While our ticket with Avaya works its way up the chain of support there I thought I would see if anyone has any ideas here.
We were running VMailPro 8.0.8.29 on all 8 distributed VM servers. We always replace our physical hardware every 3 years and this year it was time for site "B" to get an upgrade. We went virtual of course with ESX 5.0 update 1 (most of our VMPro systems run on ESX at this point.) The upgrade seemed to go fine, installed Win 2008 R2, copied the custom WAV files over, imported the local call flows, tweaked everything the way we like it, made sure the SMTP was set right and was working. Checked communication using dbgview and saw that the sync had started. All the account folders were created and I walked away to let it sync. Little did I know things had already gone pear shaped. Two days later I noticed that the status had not changed from "Starting" to "Up-To-Date".
SMTP is working, the messages are flowing, but on the remote site we get the usual cryptic message in dbgview "Distributed, Remote, Not registered, Uninitialised, Alive" while the centralised server appears to not have any pertinent error messages on it as it looks like the sync is starting. The two sites can communicate, the auto attendant portion of VMPro is working fine at site B. However, when an extension rings, VMPro never picks up. So aside from it being out of sync, the local VMPro box isn't even taking messages.
At Avaya's suggestion we upgraded the centralised and remote servers to 8.0.1011.0 with no improvement.
One thing we did notice in this process is that I didn't name the new VMPro server with the same name as the old one (same IP address). Avaya had us rename it several times and change IPs. Avaya has verified that the SMTP messages are flowing, but the initial tiers are at a loss. Anyone heard of this before? This is now a full two weeks of down time at this site and the natives are getting restless....
We were running VMailPro 8.0.8.29 on all 8 distributed VM servers. We always replace our physical hardware every 3 years and this year it was time for site "B" to get an upgrade. We went virtual of course with ESX 5.0 update 1 (most of our VMPro systems run on ESX at this point.) The upgrade seemed to go fine, installed Win 2008 R2, copied the custom WAV files over, imported the local call flows, tweaked everything the way we like it, made sure the SMTP was set right and was working. Checked communication using dbgview and saw that the sync had started. All the account folders were created and I walked away to let it sync. Little did I know things had already gone pear shaped. Two days later I noticed that the status had not changed from "Starting" to "Up-To-Date".
SMTP is working, the messages are flowing, but on the remote site we get the usual cryptic message in dbgview "Distributed, Remote, Not registered, Uninitialised, Alive" while the centralised server appears to not have any pertinent error messages on it as it looks like the sync is starting. The two sites can communicate, the auto attendant portion of VMPro is working fine at site B. However, when an extension rings, VMPro never picks up. So aside from it being out of sync, the local VMPro box isn't even taking messages.
At Avaya's suggestion we upgraded the centralised and remote servers to 8.0.1011.0 with no improvement.
One thing we did notice in this process is that I didn't name the new VMPro server with the same name as the old one (same IP address). Avaya had us rename it several times and change IPs. Avaya has verified that the SMTP messages are flowing, but the initial tiers are at a loss. Anyone heard of this before? This is now a full two weeks of down time at this site and the natives are getting restless....
