|
Joined: Oct 2011
Posts: 1
Member
|
OP
Member
Joined: Oct 2011
Posts: 1 |
I'm wondering if anyone has seen this issue before. I installed an LX voicemail at a client site back in 2007 and it's been functioning since that time without issue. The other day the client calls and says that their lines are not ringing transferring to voicemail. To test I go to site and place the IPK in night mode (which) DITs directly to the LX on all 5 incoming CO lines. However I get a busy tone on the line. In day mode, the phones ring but I eventually get busy tone if no one picks up a phone. OK the voicemail is not answering. I go to login to the LX administratively and it won't let me login and the browser says there is something wrong with the website. I am unable to bring up the login screen again using a web browser on any PC. I use putty and login that way and try to shut the system down. It spins for about 14 minutes saying "shutting down" and goes back to the menu saying that the system is "Running"?? I go to the LX shell command line to look at some logs and I see a core.xxxx file that indicates a core dump has taken place. I remove the core file. Still no success. I do a "ps -ef" to look at the linux processes and I see the shutdown command shells from my attempted shutdown still active but doing nothing?? Basically the LX is unresponsive. I power the phone system off and wait 5 minutes. I power the phone system back up and everything comes up fine including the LX. I check the messages while the system comes up and check the logs in the vmail directory and don't see anything suspicious. I can login administratively to the voicemail via the web and with putty and perform shutdown and startup. The LX ended up working for a day and a half and then I got a call from the client about the same issue. Again I try to access the LX via VPN and get the login page but I can't login using the web. I have putty access, but can't shutdown or reboot the LX. I was thinking that there were some maintenance commands that can be run from the shell which might help the situation. I remember doing maintenance on UM8000 and LX voicemail that fixed database inconsistencies and possibly file fragmentation (I thought linux systems didn't suffer from defrag issues?). It's been a year since I worked on these systems and my NEC tech ID has expired since I'm no longer with one of NEC's blessed partners. I also remember the activevoice support tech getting me to set some parameter using the shell that would prevent the buildup of core dumps. That's not really the problem here. Any assistance would be appreciated. The LX voicemail seems to work for a short period of time and then become unresponsive. Hopefully there are some maintenance commands that will resolve this issue.
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Jul 2005
Posts: 1,333
Member
|
Member
Joined: Jul 2005
Posts: 1,333 |
I suspect that the main board on the LX is on it's way out and may have a component that has heat issues..
Regards,
Paul W Now back to a 0 day week. Love these 7 day weekends.
|
|
|
|
Joined: Dec 2008
Posts: 189
Member
|
Member
Joined: Dec 2008
Posts: 189 |
Try pulling the voice mail, deleting the programming for it and re-doing the programming. I have found this to help sometimes.
|
|
|
Forums84
Topics93,959
Posts637,376
Members49,702
|
Most Online5,661 May 23rd, 2018
|
|
1 members (Curlycord),
17
guests, and
38
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|