This system is the hub of a multi-location school district. ALL outside calls go through this machine. So I need a solution to this error that won’t shut the system down at all if possible. We are in the process of consolidating all the systems into a single machine. I need to get a crapton of info from that system If the fix for the KVStore is iffy, can I get info similar to Bulk handler, especially extensions.
Thanks for any suggestions!
Thanks Lorne
I have several DB saves but when I tried to restore to a different system there was no info to be restored. Because of that I think something more sinister is going on. Is it possible to get system DIDs, Extensions, ring groups, etc info from the config files? can those files be parsed into a csv that version 17 can read from bulk handler?
Thanks James
Not sure I know what dmdixed is. Can you explain to me like I am 5?
Thanks Lorne I’ll try that and see what I can get off the system.
Somewhat related question. This new system will be onsite, since we will be utilizing a PRI ckt. We thought about setting up a cloud system, making all the necessary programming and then saving the db a nd restoring it to the local system. I realized we hadn’t used the --dahdi switch when we built the cloud system and I tried to create a new one and the kernel version for the new instance was newer than the version for the dahdi, so the script exited. Do the dahdi drivers need to be installed on the cloud system in order for th ebackup /restore to work as I described above? I get that the setup for the card will need to be hand done but that isn’t much.
Not that I know of. Even if there was, it would rely on fwconsole which probably won’t work either.
I would expect backup/restore to still work, but my experience with DAHDI is quite old now, and I’ve forgotten a lot of what I once knew. I pretty much only exclusively work with gateways now, not line cards.
TangoPBX is a trademark of TangoPBX LLC, FreePBX is a trademark of Sangoma US Inc, Asterisk is a trademark of Digium Inc.