Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - jjc8008

Pages: [1]
1
MiVoice Office 250/Mitel 5000 / Restoring new flash card from backups
« on: February 13, 2024, 05:57:09 PM »
Our old card bit the dust and we have a new one on the way, but I had a quick question about applying our backups to it: I have a "database-only" backup from right before when the card bit the dust, and a full backup from about a month ago. Is it possible to apply the full January backup to at least have some semblance of voicemail content, and then the database-only backup after that to get our extensions and such current?

2
Recently (after some planned internet outages by our cable internet provider, possibly just coincidental), all of our outgoing calls appear on recipient devices/caller ID as "<3digit area code>-111-1111". This is obviously problematic, as our normal number for all outgoing calls has always been something "normal" like "<3digit area code>-555-7890". After calls to our carrier, they insisted that our Mitel box is to blame. Ok fine, Saturday morning, initiate a reboot directly from the front of the Mitel box itself, but now it's stuck in a constant boot loop:

In preboot...
Self-Test...
Booting...
<repeat these 3 perpetually>

I've tried reseating the PCB boards that are inserted in to what I gather is the PRI? But no luck. Both PRI "boards" are lit up:

Green beside DSL, DSL 1, and DSL2
Red beside DS1 and ALM
Yellow beside "ESF/SF (YEL||GRN)" and "B8ZS/AMI (YEL) (GRN)"

The only possible culprit I've turned up so far is that it could be the storage/flash card (either missing or corrupt). It is indeed inserted in to the back of the Mitel box, but whether it's corrupt or not remains to be seen.

Update: I've gotten putty access, and during the boot looping it's outputting what appears to be some standard stuff, then lots of errors that point toward what I mentioned above (bad flash card):

-------------------
fsck.ext2: Attempt to read block from filesystem resulted in short read whda: task_in_intr: status=0x51 { DriveReady SeekComplete Error }
hda: task_in_intr: error=0x44 { DriveStatusError UncorrectableError }, LBAsect=1699182, sector=1699182

fsck failed.  Please repair manually and reboot.  Please note
that the root file system is currently mounted read-only.  To
remount it read-write:

   # mount -n -o remount,rw /

CONTROL-D will exit from this shell and REBOOT the system.
-------------------

I guess the last card to play is mount the file system in read-write mode and run fsck against it...

3
When receptionists leave, historically they've pressed Fwd All, then "Answ Svc" (Answ Svc is a phantom extension that redirects to a 1-800 answering service who take messages during our off hours), but when an outside call comes in, the phones just ring through and then ring endlessly. When the call comes in, one of the two reception phones will flash "Invalid fwd destination" for less than a second, then just display the callers name & number, BUT even when manually typing the 1-800 number after pressing Fwd All it doesn't say Invalid Forward Destination, it still just rings through to the office phone forever. The number for the answering service is good, if you pick up the phone and press the "Answ Svc" button it calls them, same as if you manually type that phantom extensions 4-digit number, as well as dialing the entire 1-800 number, the call goes through successfully each of those three ways, those two reception phones just don't seem to want to forward all calls. I've been sniffing around the system admin/DB programming menus but really didn't want to attempt to change anything before inquiring with folks who might have any suggestions first, thanks!

Edit: I'm seeing mentions of hunt group calls not being forwarded, these two phones are part of a hunt group (only two in the group), so if they're BOTH set (all of the phones in the hunt group) to forward all, will it not get forwarded?

Pages: [1]