I want a production-ready FreeSWITCH-based Session Border Controller that registers or peers with my clients’ PBXs by username and password, transcodes to Opus, and then hands the calls off to two preset wholesale carriers. The core logic is: • Country-level routing priorities stored in MariaDB. – Example: US/Canada → Carrier 1 first, fail over to Carrier 2; EU → Carrier 2 first, fall back to Carrier 1 on 404 or no answer. • Each client may present several PBXs and DIDs, all of which must map cleanly to those database rules. • Carrier trunk details stay hard-coded in the FreeSWITCH XML/JSON configs; only the client and route data live in MariaDB. I also need a small web interface (PHP, Python Flask or a similarly light stack is fine) that lets me add, update, and delete routes without touching the server console. A clean table view, country pick-list, priority drag-and-drop, and basic auth are enough for the first release. Deliverable checklist 1. FreeSWITCH SBC build files and working configuration with Opus transcoding enabled. 2. MariaDB schema covering clients, PBXs, numbers, and routing priorities. 3. Web portal to add / update / delete routes and instantly reload FreeSWITCH. 4. README with deployment steps, firewall ports, and a quick test plan (two SIP softphones to emulate PBX and carriers). The solution must install on a fresh Debian or Rocky Linux VM and pass a live demonstration: a US call failing over to Carrier 2 on simulated 503, and an EU call doing the opposite.