Viocemail Pro issue...a new one for me.

[progc]

Last night after moving a system from the lab to the production environment I started getting an error. When I press the messages button on a 4602 it rings once and then silence. It used to work.
I had to change the IP's on the switch and voicemail server to the production range.

I have since restarted the switch, the voicemail server and the key server. It still is not working.

Here is a recent sysmon range:

1073770mS PRN: Monitor Status IP 406 DS 3.2(17)
1073771mS PRN: LAW=U PRI=1, BRI=0, ALOG=0, ADSL=0 VCOMP=8, MDM=0, WAN=0, MODU=0 LANM=0 CkSRC=0 VMAIL=1(VER=2 TYP=1) CALLS=0(TOT=33)
1074200mS PRN: Recv: RegistrationRequest 0a640544; Endpoints registered: 5; Endpoints in registration: 0
1074309mS PRN: Recv: RegistrationRequest 0a640547; Endpoints registered: 5; Endpoints in registration: 0
1075327mS PRN: Recv: RegistrationRequest 0a640545; Endpoints registered: 5; Endpoints in registration: 0
1082254mS PRN: Recv: RegistrationRequest 0a640548; Endpoints registered: 5; Endpoints in registration: 0
1089799mS PRN: TFTPServer::RRQ(from 10.100.5.25) deltaconfig/vmail/YE"'$A|"~s
1102228mS PRN: Recv: RegistrationRequest 0a640543; Endpoints registered: 5; Endpoints in registration: 0
1119799mS PRN: TFTPServer::RRQ(from 10.100.5.25) deltaconfig/vmail/YE"'$A|"~s
1129065mS PRN: Recv: RegistrationRequest 0a640544; Endpoints registered: 5; Endpoints in registration: 0
1129174mS PRN: Recv: RegistrationRequest 0a640547; Endpoints registered: 5; Endpoints in registration: 0
1130187mS PRN: Recv: RegistrationRequest 0a640545; Endpoints registered: 5; Endpoints in registration: 0
1137115mS PRN: Recv: RegistrationRequest 0a640548; Endpoints registered: 5; Endpoints in registration: 0
1149796mS PRN: TFTPServer::RRQ(from 10.100.5.25) deltaconfig/vmail/YE"'$A|"~s
1157083mS PRN: Recv: RegistrationRequest 0a640543; Endpoints registered: 5; Endpoints in registration: 0


Also previously, when launching the voicemail pro client the spash screen looked normal now it looks like jumbled letters.



This system was supposed to go live last night but thankfully the router that the provider gave us had a pad port so we got a small break.
anyone....

 

[progc]

I tried that also.

 

[aarenot]

discconect the ipo from the network. call from the analog ext port to the vm. the vmpro server must be plugged into the lan port on the ipo module. if that works.

turn the dhcp back on in the ipo, and test the ip phones again. if that works,

leave everything the way you have it except, turn off dhcp on the ipo, and plug it back into the network, and look for a connectivity, or adressing conflict issue on the network. are the ipo, and vmpro server ip's set up on the network as static non-public ip addresses, if not get them set up that way before proceeding. test again the analog ext, and the ip phones, both still plugged directly into the ipo itself.

 

[progc]

This issue has been resolved.

It's a "bug" in VM PRo.

It's a result of a password in the general preferences.
The system was originally set up with a password because the tech didn't know to leave it blank. Sometimes after clearing out the password and clicking "Save and make live" it still does not clear the password. I have been told by an "ACE" certified tech that this happens from time to time.

The resolution is to click save and make live more than once and then restart the VM Pro service.


Thank you all for your time in trying to help resolve this. I do appreciate it!

 

[tlpeter]

this is a issue in 3.2.17
like Big70 already said : UPGRADE
just do it
your current version is not so good
you will spend more time on this
so upgrade and save yourself that time

 

[crumthwacket]

That's not a "bug" - putting a password in the general preferences has been a "feature" for at least 4 years (what kind of feature I'm not sure - but labeling it a bug isn't accurate).

 

[jconrad0305]

check and make sure the password in manager for voicemial and the password for vmpro match. if they dod not you will get dead air.

 

[progc]

crumthwacket,

I appreciate what you are saying, however please re-read what I have posted:

It's a result of a password in the general preferences.
The system was originally set up with a password because the tech didn't know to leave it blank. Sometimes after clearing out the password and clicking "Save and make live" it still does not clear the password.

I have been told by an "ACE" certified tech that this happens from time to time.

 

[progc]

tlpeter,

I did the upgrade yesterday. It didn't fix it but at least it is now current.

Thanks!

 

[crumthwacket]

progc:
I get it now - sorry

 

[jconrad0305]

i had it happen once. the reason it happened was that i upgraded from 3.1 to 3.2 and forgot to up the password back into vm pro. i had to log into the security settings on the manager and clear the password and then reenter it. i could have left it blank but i don't want sofware happy it people loading rogue voicemail softwares out there.

 

[progc]

crumthwacket,

No worries my friend!