Mitel 200 ICP voicemail crashing

[mmikk]

I have a customer with 200ICP AX and embedded EMEM voicemail. PBX has no issue with phones, trunks, or anything else but voicemail will stop working about every week or so and system needs to reboot to work again. I had someone go on site and update the software and it seemed to resolve the issue for awhile but started again,, not quite as frequently.
Any other suggestions?

 

[nytalkin]

Is this a hospitality system? If connected to PMS check the ip to serial convertor for the VM interface, I've seen these cause the problem you are having.

I suppose you're entitled to your opinion, I'm just not going to suppose very hard.

 

[nytalkin]

Found this service note:

Summary
200ICP embedded voicemail fails to answer.
Question
Why does my Embedded voicemail fail to answer?
Answer

Sites may experience embedded voicemail failing to answer. Sites in this case would typically in the hospitality market. Those whom would use tcp port 6830 where the PMS server connects to the 200ICP controller's voicemail system. All sites whom have had this issue all have used the Precidia Ipockets for SX200 ICP to PMS integration.

Only a system reboot will recover the Embedded voicemail functionality, and even when doing so, this problem generally will return. Using the start and stop commands from secure port 2002 shell for the embedded voicemail does not resolve this problem.

When troubleshooting a site which meets the symptoms and details outlined above, the easiest way to validate that this bulletin relates to the site is as follows:

1-From port 2002 (secure telnet)
2-Enter the following command: inetstatShow
Search through the output for a line similar to the one below:




-> inetstatShow
inetstatShow
Active Internet connections (including servers)
PCB Proto Recv-Q Send-Q Local Address Foreign Address (state)
-------- ----- ------ ------ ------------------ ------------------ -------
e64363c TCP 0 0 10.40.196.4.4818 10.37.55.130.1067 SYN_SENT
e644320 TCP 0 0 10.40.196.4.4817 10.40.196.50.1067 SYN_SENT
e6434b0 TCP 0 0 10.40.196.4.4816 10.40.196.90.1067 SYN_SENT
e6443a4 TCP 0 4830 10.40.196.4.6830 10.40.196.5.55585 ESTABLISHED
e64342c TCP 0 0 10.40.196.4.2002 10.40.196.5.55583 ESTABLISHED
In the output above, this identifies that
VMPMSSrv is the process
4404 are the amount of errors in the Send Q at the time, and will keep growing and the problem will soon occur. (data has proven that once this reaches 8000 the voicemail will no longer answer).
10.40.196.4 is the ip address of the 200ICP
10.40.196.5 is the ip address of the Ipocket for the PMS to voicemail connection.

The only known solution to this problem has been resetting the actual Ipocket that uses port 6830.
The Ipocket that is used for the PMS to 200ICP is not affected by this problem. It does not need to be reset.

Precidia has not reported any known problems with the current units or firmware. This problem was not duplicatable in the Mitel support labs. The information and workarounds are based on site investigations and run time after resetting of the Ipocket.

I suppose you're entitled to your opinion, I'm just not going to suppose very hard.

 

[The mitel guy]

it sounds like it could have a malfunctioning hdd or partition.

 

[mmikk]

Thank you for the replies. nytalkin - the service note you provided was very helpful. I replaced the LAN 232 converter for VMS/PMS interface and after several weeks (knock on wood) the issue has not resurfaced. What is strange is that it was affecting admin voicemail as well, which I would not think is affected by PMS interface.