|
Joined: Jan 2005
Posts: 264 Likes: 1
Member
|
OP
Member
Joined: Jan 2005
Posts: 264 Likes: 1 |
I think I've been making that face for the past few days. This is an odd one. (Edit spelling)
Last edited by tylan; 11/28/18 01:58 PM.
|
|
|
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: Jan 2005
Posts: 264 Likes: 1
Member
|
OP
Member
Joined: Jan 2005
Posts: 264 Likes: 1 |
Installed the second new card last week on Thursday. So far so good. The goal is to make it past seven days, since the last new card took about six days to act wacky like the last one. I decided to put the new card into slot 1 and the known good card into slot 4. Mainly because slot 1 has more extensions, and failed faster when I was testing.
So, here we go...
|
|
|
|
Joined: Jan 2005
Posts: 264 Likes: 1
Member
|
OP
Member
Joined: Jan 2005
Posts: 264 Likes: 1 |
All stations still working fine on both cards. However, something is going on that is probably related to whatever the original problem was...
Several calls have been cut off in voicemail, and some issues getting into and/or checking VM.
The VM is on ports 15 & 16 on the LDS in slot 1. This is the 2nd new card. Original problem card was in 3. New card went into 3 and failed after 6 days. Tried new card in 1 and moved 1 to 4. Card in 1 failed within minutes of booting 2nd new card installed in slot 1 - 5 or 6 days ago.
Not sure what to think now... CPU? Cabinet / backplane? Should I restore a backup before this all started some time ago?
|
|
|
|
Joined: Dec 2007
Posts: 6,800 Likes: 18
Retired Admin
|
Retired Admin
Joined: Dec 2007
Posts: 6,800 Likes: 18 |
Did I read Backplane?
If you believe that it is a Software Corruption then if you default the system and reload the database you have a great chance of uploading the corruption. The best way is to sit with two computers and hand copy, screen-by-screen the database, from the suspect database to a clean version.
Been there, done that, got the T-shirt.
|
|
|
|
Joined: Jan 2005
Posts: 264 Likes: 1
Member
|
OP
Member
Joined: Jan 2005
Posts: 264 Likes: 1 |
Did I read Backplane?
If you believe that it is a Software Corruption then if you default the system and reload the database you have a great chance of uploading the corruption. The best way is to sit with two computers and hand copy, screen-by-screen the database, from the suspect database to a clean version.
Been there, done that, got the T-shirt. LOL you read correctly. I believe that was your opening comment here. I really have no idea what it could be. As for the software I have backups that go back pretty far... Like several years. Starting from scratch wouldn't be that hard either. It's a simple system that should have been something like a DX-80, but I think this was installed prior to us selling that system. Dunno for sure. I rebooted the the voicemail, ran a full scandisk (no errors), and powered it off / on. I doubt the cut off messages would be the VM at this point, but maybe it's unrelated (just thought I'd go through the motions). I feel like this has the potential to bleed on until something major happens.
|
|
|
|
Joined: Aug 2004
Posts: 9,159 Likes: 17
Admin
|
Admin
Joined: Aug 2004
Posts: 9,159 Likes: 17 |
A services board will also cause random issues. I'd see if the customer is a 5 day a week organization. If so I'd load a default database on Friday after close of business and see if it runs clean over the weekend. That would eliminate the database. You can save the database as a .dbr file and email it to me. I can look at it or load it in one of my test systems to debug/stress test.
Dave
|
|
|
|
Joined: Jan 2005
Posts: 264 Likes: 1
Member
|
OP
Member
Joined: Jan 2005
Posts: 264 Likes: 1 |
A services board will also cause random issues. I'd see if the customer is a 5 day a week organization. If so I'd load a default database on Friday after close of business and see if it runs clean over the weekend. That would eliminate the database. You can save the database as a .dbr file and email it to me. I can look at it or load it in one of my test systems to debug/stress test.
Dave It doesn't seem like that is long enough for the oddball issues to show. Or do you mean put one of the earlier "bad" LDS cards back in?
|
|
|
Forums84
Topics94,299
Posts638,875
Members49,770
|
Most Online5,661 May 23rd, 2018
|
|
0 members (),
109
guests, and
299
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|