I came upon a new customer with freepbx on a PC. No one knows root password or freepbx login information and original installer is out of business. This is a restaurant. Must we start from scratch? I have managed to get myself back in to my own systems but I knew root password.
Is this a case of finding out the O/S and then googling it to find instructions?
It should be possible to reset a Linux root password if you have physical access to the machine. However, although, in principle, it isn’t that difficult, I don’t think it is something that should be detailed on a public forum.
Just to follow up it was not a Freepbx PC. After some investigation the PBX is a re-branded PBX appliance by Yeastar which I believe runs some sort of asterisk but we are locked out. Probably barking up the wrong tree here. Nonetheless no easy solution and customer isn’t too keen on rebuilding the whole setup.
It’s not clear what your relationship is to this customer but it seems like a clear opportunity to sell them something better, that you can support. They may not be keen on rebuilding the setup but I bet they would be happier about it if they knew a new FreePBX / PBXact system would be well cared for by johntgs and they won’t have another emergency like this.
Yes, that is going to be our goal. Get them on a good system with good support. I don’t believe in a magic but is there a way to somehow obtain the sip credentials over the network for the existing 15 - 20 IP phones or must we manually do so and then retype them into another pbx?
I don’t believe the SIP credentials are passed “in the clear” - though if this is a very old system maybe there is a chance of that? Also, I’ve found poorly setup systems tend to use the same password for all phones so you might luck out there.
Are you unable to reboot the system off of a “live linux cd” and then go look at the files in /etc/asterisk to get this info?
A slightly less dangerous option would be to pull the disk and duplicate it, then put it back. Use the duped copy for your forensics and you should be able to pull all of the information from the “/mnt” mounted file system. The advantage there is that you can do it in a more leisurely timeframe and have (as a side benefit) a backup you can use if the drive craps while you are working on the replacement.
This also gives you the advantage of being able to test everything before you get started with the “real” uprade.
you can then mount the output file produced somewhere convenient.|
In that image the directories etc/*var/lib/asterisk*var/spool/asterisk/* and var/lib/mysql will probably have useful breadcrumbs like asterisk’s .conf files and the asteriskdb sqlite3 file (this depending on how asterisk was deployed on the original appliance)