Voicemail Channels are all in use. SYStem status

[iagaoe]

So i did the dreaded upgrade this weekend to the newest software release. 4.2(4) and now i can not communicate with voicemail pro. I check in system status and have 6 alarms total. and one of them that i think may be causing it is all voicemail channels are in use.

Is there anyone that can help me with this?

The other alarms i have are LINE:1 is a yellow alarm
Line 2: 2 yellow alarms and 1 red alarm.

Under link i have link/resource down expansion 4.

And 1 says 8khz clock source changed. Previous source was internal.

Thanks again.

 

[NYSTECH]

Lets start with Basic information
What type of system...
From what version did u upgrade from and did u do the .99 for control units and DS modules

ACS- IPOffice Implement

 

[iagaoe]

IP 406 DS 4.2(4)
Upgraded from 4.1
"Did you do the .99 for control units and ds modules."
i have no clue what that means sorry for my ignorance.
Thanks

 

[Westi]

from 4.1 to 4.2 there should be no interim release needed so forget about the 3.2.999 information.

are your licenses valid?
can you ping the IPO from the voicemail?
is the voicemail pro programmed as VM Pro with the correct IP address in the system information of the IPO?

Joe W.

FHandw., ACS

If you can't be good, be good at it!

 

[NYSTECH]

Did not know what version you upgraded from.. so Wasn't sure if you loaded the 3.2.99 bin files for the control unit and the digital module..

Since you started on 4.1 I assume the control unit was already done...

Are the licenses valid?

Is the feature key running?



ACS- IPOffice Implement

 

[iagaoe]

Control unit was already done.
The vm pro is on the same box as ipo so pinging it would do me no good.
In system yes the correct ip is set for the vm server ip.
Feature key is running.
Licenses are valid.

Should i try downgrading vm pro back to the previous version?

 

[NYSTECH]

You should be able to ping the IP Office 406 from the pc running VM Pro.. They should be 2 seperate Ip address

ACS- IPOffice Implement

 

[iagaoe]

Yes i can ping the IP office hardware from the computer running vm pro.

 

[CarGoSki]

I might try to reflash the ipo and modules. Sometimes you have to power cycle the IPO to restore order. Also did you say that you upgraded the vmpro to the new release?

 

[NYSTECH]

Turn off any anti virus software and firewall settings.

Restart VM services.

ACS- IPOffice Implement

 

[Westi]

your system status shows the voicemail channels as in use or just as congested and the problem counter goes up because it won't answer.
Voicemail Pro "service" is running
service logs on to local account?




Joe W.

FHandw., ACS

If you can't be good, be good at it!

 

[iagaoe]

I figured it out, unistalled new vm pro. restarted, installed new voicemail pro, restarted, power cycled the system. reimported .mbd and good to go.

Guess it had to do with the new voicemail pro.

 

[NYSTECH]

Weird.. Thought you did not have to unistall VM Pro if your already on 4.1

ACS- IPOffice Implement

 

[r6wraith600]

I experienced some issues, well major issues, upgrading from the latest 4.1 VM Pro to 4.2. I had to in the end rebuild the clients VM call flow manually, even though I had a export before the upgrade.

 

[iagaoe]

Ya, i just had to unistall and reinstall vm pro again!.....i keep getting the coiemail channels are all in use error and it won't work? This is not good...

 

[r6wraith600]

OK this is what I had to do. I really truly completely uninstalled, renamed the existing old VM Pro directory to VM pro BACKUP for example. This way it was like a fresh install. You have to remember that uninstalling VM Pro doesn't remove the old directories since such as the greetings folder.

There is something in there, that I couldn't spend the time at site to determine what file exactly "broke" the upgrade.

In my case, after it was reinstalled everything looked fine, until i imported my call flows and old setup back, it was seem to work but no communication to the IPO switch (no messages, greetings, menu's). So I did the above all again and manually rebuild the call flow. Then i copied over ONLY the core .wav files. I did not take any files that were tagged other then a .wav extension since they were all fine.

There is a specific file or several that is not upgrading properly and once you have gone up to 4.2 you can't go back. Trust me I tried. I backed up the call flow before hand but in hind sight I didn't back up the "VM" folder. I think if I did that I would have salvaged the build.

So I suggest to stop trying to fix it since you likely in the same boat as many others are now and jsut rebuild it. Since I rebuilt it everything has been working very well.