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....

 

[aarenot]

why did you have to change the ip's.
other items such as phone manager, call status, ip of the vmpro server itself, soft console, ip's of ip phones may need to be changed as well.

 

[progc]

we went to a production environment.
All of the ip's are changed and the phones get dhcp.

 

[big70]

First thing if you placed it last night why isn,t it on 3.2(53) and VM-Pro 3.2(28).
I would upgrade first.

If you get dead air is your licences for VM-Pro valid?


Greets Peter

 

[progc]

Voice mail pro is valid. Not sure how upgrading is going to fix a system that used to work....

 

[aarenot]

do the ip phones work other than this issue with calling vm.

can you ping the ipo from the vmpro.

was subnet changed

do you have non ip phones, and do they have issues.

 

[big70]

3.2 (17) is the first 3.2 release and everyone knows the first new release is a bad one.

Never used 3.2 (17) add a customer side only add home.
Have installed many 3.2 (53) and looks very good to me.

So i almost never start trouble shooting on a version where there is a list with more then 50 adreesed fixes.

In VM-Pro can you see if it will answer the call in debug mode. In Services you can say interact with desktop or something like that.
Then you can see whats its doing like VM-lite.

Greets Peter

 

[progc]

yes phones can call one another

I can ping the switch from the VM server

The systems went from 10.10.60.X to 10.100.5.X

No non-ip phones

 

[jml2665]

maybe a DHCP conflict? who's providing the DHCP?? if the IPO is and the customers server is then that might be an issue, also check the DHCP range, You need to have static IP's for your VMPro and license server and maybe those are not available or being given out by the customers DHCP

 

[Shine52]

Try putting an IP route in the IPO that associates w/ your new range. Is a firewall blocking anything?

Figure it out damn-it!

 

[progc]

the Domain Controller is handing out DHCP. The IP Office was before.

DHCP is now off on the IP Office now and has been.

 

[progc]

Shine52,

There is no firewall.

 

[big70]

He says licences are valid and getting silence so the IPO must see the VM-server else you get busy.
Silence is mostly a licence problem but if you restart the VM-Pro service sit should work at least one houre without a licence.

Did you put the VM-Pro Pc directly on IP-Office.

Greets Peter

 

[progc]

Peter,
You mean on the IP Office switch? No.

I've restarted the VM Pro service already and it didn't fix it.

 

[big70]

Try to put it on the port on the IPO maby its a setting on the switch like a port thats set to 100MB full or negotiation off.

Greets Peter

 

[aarenot]

since the system was working prior to you moving things we should be able to guess that it is not a system issue. therefore it must be something you have overlooked in your changes.


since you moved from one 'environment' to another, check to make sure that all of your components in your system, and settings for connectivity have been changed to reflect the changes in the 'environment'. ip's;vm, lan1, time server, tftp server, in the ipo config. ip's;voicemail server nic card static ip, subnets, gateways, including the ip phones.

ping the ipo from the vmpro server to start.

do the ip phones work other than the vm calling issue.

i never willingly use ga releases, i wait for maint releases, so i would recomend going to a maint release, unless it has a known issue with somehting that will effect you. i consider all ga releases as beta releases until they have been in the field, and you know the field issues. that happens when the maint release comes out in my opinion for all software.

ping the ipo from the vmpro, then pull the configuration from the vmpro server using manager. look in manager under licenses and double check the vmpro licences are valid. reboot the vmpro server, it should work for about 2 hours even if licenses are invalid then shut down. check the license dongle be it serial, or usb is connected well.
plug an analog phone into the pots ext port on the system, make sure it is set up as a valid user, and call vm from it, dial star17. does the vm answer properly from there.

 

[aramsay]

Have you changed the IP address of the VMPro server within the IPO config? Somewhere in the system tab I believe.

 

[progc]

yes I have changed all of the ip's and and have verified that they are correct.

 

[progc]

how would I telnet to the switch and see if there are any routes in the ifconfig that I need to get rid of.

 

[aarenot]

also, plug an ip phone into the ipo lan ports, and see if they work from there.