Busy signal after upgrading to VMPRO 5.0.21

[MAlcala]

After upgrading to VoiceMailPro 5.0.21, we get a busy signal instead of the auto-attendant. Anyone else experienced this issue?

We restored our VMPRO 4 and the auto-attendant worked again.

 

[hbsurfn]

Are you getting a busy when dialing *17? Is your IPO at release 5? Is the VM Pro service running?

ACA
CompTIA Convergence+
CCNA
CCVP

 

[MAlcala]

We are running IP Office 5.0.8. The VoiceMailPro service was running. The auto-attendant worked during the day. The next morning, we would get a busy signal calling from the outside or dialing *17. Restarting the service got the auto-attendant working for one more day. Then, we had to restore to version 4 to get the auto-attendant working again.

 

[PlatGuy]

You cannot run a V5 VM Pro on a V4 IPO.

You did upgrade the control unit too didnt you?

 

[jco9715]

I have found that on the 400 series if you are not using a serial dongle that is directly attached on to the unit you will have issues with certian lics after the R5 upgrade. The Lics i had issues with were mobilty and VM rest worked fine. To fix this I found if you reinstall the Feature Key server it works.

 

[amriddle01]

jco9715, has beat me to the line on this one, I was going to say on all recent upgrades not just to 5 the feature key server can become corrupted and needs a fresh installation, it has arisen a few times over the past year and a half or so

ACS - IP Office Implement

"What the Crocodile Hat....was that?

 

[MAlcala]

Yes, I upgraded the 406V2 control unit to 5.0.8. Should I restore the control unit back to version 4?

 

[amriddle01]

That error usually means something else on the network/PC is trying to use that port (50791). And that would indeed cause a problem

ACS - IP Office Implement

"What the Crocodile Hat....was that?

 

[amriddle01]

Open a command prompt on the VM server and type netstat -b and see if anything on there is using that port other than VM

ACS - IP Office Implement

"What the Crocodile Hat....was that?

 

[amriddle01]

Now look what's happened, I look like I'm talking gibberish, to qualify my above statements a trace was posted stating a socket binding error on the VM port my above post was in response to this, the original post has been removed due to a "debate" I was having

ACS - IP Office Implement

"What the Crocodile Hat....was that?