Voicemail Pro 5.0 Migrate to new Server 2

[vtphilk]

Anyone have any idea of what the trick is to move Voicemail Pro 5.0?

I have done it in the past and just had to stop the services, copy the "VM" Folder, then start services. Do I have to backup registry or something now?

I'm trying to move from SBS 2003 to SBS 2008 (32bit -> 64bit).

So maybe the 64bit OS is the problem??? Basically I start up vmail pro and there are no users showing up in the client console.

THanks!

 

[Westi]

there will be nothing showing up until you tell the phone system to use the new PC with the changed IP address as voicemail, then the voicemail will get the information from the phone system.

Joe W.

FHandw., ACSS

insanity is just a state of mind

 

[vtphilk]

ugghh...why didn't i think of that ..haha I will give it a shot and let you know!

 

[vtphilk]

Welp, I finally got the stuff back by restoring the vmdata.mdb from a backup however I am not seeing all the mailboxes now when I connect to the avaya and the voicemail is not work (Just going to dead air).

Ughh..this should be easier!

 

[tlpeter]

Server 2008 has a strong(er) firewall then 2003.
Did you try turning it off ?
Did you reboot the ipoffice after changing the ipaddress in the voicemail tab ?


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

 

[IPOpotamus]

26 Apr 10 16:12
Anyone have any idea of what the trick is to move Voicemail Pro 5.0?

I have done it in the past and just had to stop the services, copy the "VM" Folder, then start services. Do I have to backup registry or something now? [/b]

Did you make the move without reinstall?

the migration of VMPRO is relatively easy without touching the register

Backup all the folders under VoiceMailPro/VM
specially Accounts, Names, Wav, VRL

when you fresh intall VMPRO Again, MailBoxes will be created automatically for every user and huntgroup

now you can start the services
and of course modify IP Office Config of the VoiceMailPro ip address

(that changes wont require reboot)

 

[vtphilk]

I'm still having trouble getting it running on my SBS 2008 server. I had to move it to a SBS 2003 server we had for another network and send voicemail over the two networks for now.

Any idea of what is up with VMail 5.x running on a 64-bit OS. Does it have problems or what?

I moved from a SBS 2003 server to a SBS 2003 (Both 32bit) and worked just fine. Stopped services, copied VM folder. Started services. Didn't even have to do backup restore of registry.

However, I cannot for the life of me get it working on the 64bit sbs 2008.

 

[TomMills]

how are you doing the shift? i typically do a clean install, stop the services, copy the old data across then start the services again.

ive not had any problems with 64bit os yet. have you disabled the firewall like tlpeter mentioned?

http://www.twitter.com/tem1985

ACSS-SME
Get well soon Aaron.

 

[vtphilk]

Yep..I did a fresh install, then stopped services on old server, copied VM folder, then started. I checked and there was a firewall rule in the firewall and nothing getting dropped but I can try disabling it all together but I think I have done that already.

I have Symantect Endpoint Manager Server and Blackberry Express running on this SBS2008 server. So i'm wondering if those are conflicting or something. They did not on the SBS2003 server however...

 

[vtphilk]

Still get the dang VM Pro working on 64-bit Windows SBS 2008. I was able to get it up and running but it never will detect all the mailboxes and callflows even thou I'm copying over the entire VM folder

 

[tlpeter]

Start from scratch.

Stop the service on the old server.
Look in monitor and be sure you see that the ipo looses the connection.

Be sure that the new server has a static ip and that the vmpro service is running.

Be sure that the vmro service has an exception in the firewall.
Turn of the firewall!
Turn of any anti virus!

Connect the vmpro machine straight in to the ipoffice.
Be sure that the ipaddress of the server is in the voicemail tab in manager.

Look in monitor and check that the ipo is getting a connection with the vmpro server.

If that is the case then migrate all mailboxes and messages.


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

 

[vtphilk]

Ok..so I think I found my problem. I tried launching the monitor and it won't connect. However, the system status is working as well. Something is funky here!

I disabled the SBS 2008 firewall still no joy.

I did a wireshark capture and I see a bunch of packets going to the IP of the IP500 however on port 50794. Is that correct.

Also, all the packets seem to have 0'ed out checksum so they are all black and red in wireshark. They also seem to only be in one direction (No response from the IP500). Anyone have any ideas what might be up.

This is a SBS 2008 Server running 64-bit with 24GB RAM. Also have Symantect Endpoint Manager Server (Not the antivirus client thou), and Blackberry Enterprise Express running on this server.

 

[vtphilk]

Nevermind..monitor working now, it was bad password. I had at somepoint screwed up the password and forgot it was different after the upgrade

 

[tlpeter]

But is VMPro working now ?
You can set a VMPro password too!!!
Is that set or do you not use that?


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.

 

[vtphilk]

No VMPro password set. I'm trying the swing of vmpro now.

 

[vtphilk]

So still no joy .

Here is the setup.

Server A = 192.168.9.2 (Running Windows 2003 SBS (32bit))
Server B = 192.168.6.4 (Running Windows 2008 SBS (64bit))

Server A right now just has VoicemailPro on it.
Server B has IP Office, Monitor, Manager, VoicemailPro, and Kiwi syslog server to collect IPDR from the SMDR logs.

Both are connected via the same ethernet switch however has two different subnets which are isolated by a router. However, there is no blocking or port firewalls etc..

Voicemail Pro working just fine on Server A. However, we need to decommission that server very soon. So if I shutdown the voicemail processes on Server A, I see from the monitor, that it is disconnecting:

563412561mS PRN: VMAIL - Down Server c0a80902
563412561mS PRN: Delete VMailClient 192.168.9.2
563412561mS ERR: TFTPReceiver Unreachable net=192.168.9.2 port=0


So I then go and turn on the Voicemail processes on server B. Then go into manager and update the IP on the voicemail tab to reflect 192.168.6.4 rather 192.168.9.2.

I then see it connect because I see all the voicemailStatus messages fly across the monitor.

I then check in monitor under voicemail sessions and it shows 192.168.6.4 is active. So sounds good right? NO .

If I go into voicemail pro client on the Server B, I see it is connected, but I CANNOT see any of the things under groups which is where the "Leave" is for each hunt group. So all the call flow is missing. This is AFTER I copied over the entire folder from the VM folder on server A to B and rebooted the entire server even.

This is what it looks like on Server A (WHICH IS GOOD):

This is what it looks like after I point the IPO to Server B (WHICH DOES NOT WORK) :

I have not tried doing a 'Save Make Live' while server B is active because I'm afraid I will wipe out the entire call flow or something.

Please help! Has anyone install IPO Voicemail on a windows 64-bit server? I had problems for awhile with getting it to work with Blackberry express on the same server. I had to move the blackberry port from 8085 to something else. However, after that is fixed, I think it should be good. I have even tried stopping all the blackberry services then try it and no luck.

Thanks in advance!~

PS> This is VMPro 5.0.25

 

[tlpeter]

Click on users and see if you can add one from the drop down list.


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.