Freeswitch POC: DB-Based Setup
Budget: $30 – $250 AUD
I’m building a proof-of-concept Freeswitch installation where every call-routing decision (CRDs) and the entire configuration lives in a MySQL back-end rather than flat XML.
Here is what I need delivered:
• Freeswitch installed and running on a clean Linux host (Debian 12).
• ODBC/MySQL integration fully configured so that SIP profiles, dialplan logic and all related settings are read from, and editable in, the database.
• Pre-populated data for:
– Two SIP profiles (internal/external)
– A basic dialplan covering inbound, outbound and transfer scenarios
– A set of extensions reachable both by IP authentication and by user/password registration
I should be able to drop new rows into the relevant tables and see the changes take effect after a reloadxml. No manual edits in conf/ should be necessary.
Please include concise documentation or SQL scripts that let me recreate the schema and seed data on another server, plus the Freeswitch commands I’ll need for verification (e.g., sofia status, reloadxml).
If you already have a proven approach or templates for database-driven Freeswitch, this should be a quick engagement; I mainly need a clean, reproducible starting point for further testing.
Here is what I need delivered:
• Freeswitch installed and running on a clean Linux host (Debian 12).
• ODBC/MySQL integration fully configured so that SIP profiles, dialplan logic and all related settings are read from, and editable in, the database.
• Pre-populated data for:
– Two SIP profiles (internal/external)
– A basic dialplan covering inbound, outbound and transfer scenarios
– A set of extensions reachable both by IP authentication and by user/password registration
I should be able to drop new rows into the relevant tables and see the changes take effect after a reloadxml. No manual edits in conf/ should be necessary.
Please include concise documentation or SQL scripts that let me recreate the schema and seed data on another server, plus the Freeswitch commands I’ll need for verification (e.g., sofia status, reloadxml).
If you already have a proven approach or templates for database-driven Freeswitch, this should be a quick engagement; I mainly need a clean, reproducible starting point for further testing.