VMPRO Problems !!

[rmktech]

Hello, i have an IP Office 406v2 (r4.05), vmpro.(4.0). I am having the problem of failing to connect to the control unit. It connects for a second then i get the following message's.

.812 - Voicemail Pro Server Version 4.0 (15)
15:41:04.484 - Create New User 192.168.1.99 port=4099

15:41:04.515 - Licence Summary for 192.168.1.99
15:41:04.515 - Voicemail Pro is licenced
15:41:04.515 - Integrated messaging is licenced
15:41:04.515 - VPIM is NOT licenced
15:41:04.515 - Voice recording library is licenced
15:41:04.515 - 3rd Party Database is licenced
15:41:04.515 - VB Scripting is licenced
15:41:04.515 - Outlook Calendar based greetings is NOT licenced
15:41:04.515 - ScanSoft TTS Support is licenced for 1 ports
15:41:04.515 - Generic TTS Support is licenced for 1 ports
15:41:04.515 - BulkInfoRequest 192.168.1.99 2
15:41:04.515 - PBX Requesting ULaw companding
15:41:04.515 - Initialize Sequencer tx_seq=0, rx_seq=0
15:41:04.515 - TFTPLoadFile 192.168.1.99
15:41:04.515 - 0 mailboxes were open (but not active) when flushed
15:41:04.515 - DevIO::StartTask 192.168.1.99
15:41:04.531 - DevIO:rocessReceiveBuffer 192.168.1.99
15:41:34.468 - BulkInfoRequest 192.168.1.99 2
15:41:34.468 - PBX Requesting ULaw companding
15:41:34.468 - Initialize Sequencer tx_seq=0, rx_seq=1
15:41:34.468 - TFTPLoadFile 192.168.1.99
15:41:34.468 - DevIO:etach 192.168.1.99
15:41:34.468 - 0 mailboxes were open (but not active) when flushed
15:41:34.484 - DevIO::StartTask 192.168.1.99
15:41:34.484 - DevIO:etach 192.168.1.99
15:41:34.500 - DevIO:rocessReceiveBuffer 192.168.1.99
15:42:04.468 - BulkInfoRequest 192.168.1.99 2
15:42:04.468 - PBX Requesting ULaw companding
15:42:04.468 - Initialize Sequencer tx_seq=0, rx_seq=1
15:42:04.468 - TFTPLoadFile 192.168.1.99
15:42:04.468 - DevIO:etach 192.168.1.99
15:42:04.468 - 0 mailboxes were open (but not active) when flushed
15:42:04.484 - DevIO::StartTask 192.168.1.99
15:42:04.484 - DevIO:etach 192.168.1.99
15:42:04.500 - DevIO:rocessReceiveBuffer 192.168.1.99
15:42:34.468 - BulkInfoRequest 192.168.1.99 2
15:42:34.468 - PBX Requesting ULaw companding
15:42:34.468 - Initialize Sequencer tx_seq=0, rx_seq=1
15:42:34.468 - TFTPLoadFile 192.168.1.99
15:42:34.468 - DevIO:etach 192.168.1.99
15:42:34.468 - 0 mailboxes were open (but not active) when flushed
15:42:34.468 - DevIO::StartTask 192.168.1.99
15:42:34.484 - DevIO:etach 192.168.1.99
15:42:34.500 - DevIO:rocessReceiveBuffer 192.168.1.99
15:43:04.468 - BulkInfoRequest 192.168.1.99 2
15:43:04.468 - PBX Requesting ULaw companding
15:43:04.468 - Initialize Sequencer tx_seq=0, rx_seq=1
15:43:04.468 - TFTPLoadFile 192.168.1.99
15:43:04.468 - DevIO:etach 192.168.1.99
15:43:04.468 - 0 mailboxes were open (but not active) when flushed
15:43:04.484 - DevIO::StartTask 192.168.1.99
15:43:04.484 - DevIO:etach 192.168.1.99
15:43:04.500 - DevIO:rocessReceiveBuffer 192.168.1.99


My 406 is at 192.168.1.99
my voicemail pro is at 192.168.1.7

I have unloaded and reloaded the software about 3 times, so a software load issue i asssume is not the culprit. Anybody have any ideas's


Thanks
Ron K.

 

[etel]

Best thing to do is upgrade to the new maintence releases of both Admin and VMP

 

[aarenot]

*17 not getting you to VM? I am assuming you are haviong trouble getting into your vm froma phone, and not via the VMPRO client. What have you done? Turn off windows firewall, set exceptions, plug straight into the IPO for LAN, run firewall batch file?

 

[rmktech]

etel: Did that..........

aarenot: did that.

I still, get the jibberish i stated above.

No firewall!
No virus Protection!

latest version of vmpro & 4.0.7

Thanks

RMK

 

[aarenot]

you did not answer my questions, or confirmed ny assumptions.

 

[fshaw]

Can you ping the IP Office from the VM Pro PC?

I have seen the connection between the IP Office hub/switch and the 406 control unit with 4.0(5) have issues with an overheating chip. Since nothing can consisently connect, VM Pro, SSA, Monitor, Call Status, and Phone Manager all have issues.

To test, start up Monitor. If it keeps giving a Connection Lost message, then you may have this issue. Then unplug the IP Office for 5-10 minutes to let it cool down. Power back up and see if you get a good connection for awhile. The issue will start reappearing. (If you just unplug for a second, there is no improvement in performance.)

Tech Support recommended going back to 3.2(55). They recommended defaulting the IP Office configuration. They also set up a ticket for an RMA of the 406.

In the end I did both RMA the unit and wrote a new config file from scratch. No further issues.

Good Luck,
Frank

Frank Robertshaw
The Phone Guy
Nashville, TN

 

[rmktech]

aarenot: *17 goes nowhere, Yes i am having a problem getting voicemail from the telephone. VM Pro client says it connect, however i get a little nag window saying it lost the connection after 5 or so minutes. What have I done? I loaded the 4.05 software to my computer, loaded vmpro software also. (fresh install, deleted older versions). Upgraded 406v2. Chose vmpro in System/Vocemail. eneterd ip address of VMPro Server. Uploaded changes, ran VMPro client, created startpoint for AA, saved and made active.created shortcode for above AA. uploaded. (I know extra work) restarted VMPro server and then i got the display that I had posted.

That is what did before. Today I ran the Avaya fw.bat program, removed system from network, disabled all firewalls and virus programs. plugged into 406v2, ran dhcp, obtained 192.168.42.2 then is set it static. Rebooted all an ran again Vmpro still spit out the same as displayed above. Monitor now shows a new line that just keeps printing out

PRN: TCP: CHECKSUM FAILED 61da against cc6a (src c0a80101 dest 0)

This line is continuos until activity on the system..


fshaw:
Yes I am able to ping the 406v2.

I will try the power issue out.

Thanks both for your reply...........

rmk

 

[rmktech]

fshaw: I powered the unit of all day and then powered back up and i still get the same output on monitor and Vmpro server report.

 

[PlatinumGuy]

The client window saying it is logging off is nothing to worry about. If you do nothing in the client it will log off. This is so that you dont tie up client access to the vm server in case somebody else on the network wants to access it. You can change this timer under preferences/general.

I would say try a different machine to prove a point.

ACA - IP Office Implement
ACS - IP Office Implement
ACE - IP Office Implement
ACI - IP Office Implement

 

[aarenot]

is the VMPRO plugged directly into the IPO LAN port? If not, try it there. Also, check monitor, manager, phone manager for connectivity to the IPO from your network.

 

[littlegates]

How do you have the service setup on the server. Is it a local service, or Username/password?

start
run
services.msc

check voicemail proDB service

Make sure it's set to log on locally
don't interact with desktop

Restart the services, and double check your IP settings in Manager.