allow both DAHDI and ZAP configurations. However, since both can't co-exist at the same time (or I think that is the case), they're still somewhat mutually exclusive. Things to do or think about:
- on upgrade, detect compatibility mode setting and installed modules and migrate zap to dahdi tables if the implication is these were running in compatibility mode. This will include:
- zap table => dahdi table
- zap trunks get all changed to dahdi trunks
- ZAP Channel DIDs needs to be renamed
- should be intelligent to detect either one so no migration needed
- do we take the opportunity to update it to some of the existing suggested tickets that might allow it to allow direct channel routing for SIP and others (find related tickets as example)?
- Do we make the GUI intelligent and only show ZAP or DAHDI choices after the migration since the other does not make sense?
- downsides to this, if someone has existing ZAP configuration after the migration, and then they switch out to dahdi we would lose their settings.
- We could check if any existing settings are there and if so, then show it and if empty, then not, which would allow them to see their settings but it would not provide a migration ability
- we could provide a simple tool to migrate manually
