s
smith_cad2

Smith C.

@smith_cad2

Voip Setup, AI Automation

États-Unis
Anglais, Allemand
Certaines informations sont présentées en anglais.
À propos de moi
VoIP & Automation Engineer with 6+ years of experience delivering scalable and reliable communication systems for businesses. Specialized in Asterisk, FreeSWITCH, SIP, SMPP, call routing, and advanced VoIP troubleshooting. I design and implement AI-driven solutions including chatbots, voice agents, and workflow automation systems to streamline operations, enhance customer interaction, and reduce manual workload. Experienced in API integrations, CRM connectivity, and Linux-based server deployment, ensuring secure, efficient, and fully integrated business solutions tailored to client needs.... Plus d’infos

Compétences

s
smith_cad2
Smith C.
hors ligne • 
Temps de réponse moyen de 1 heure

Voir mes services

VoIP et Téléphonie
I will install voip, sip trunk, freepbx, astericks, vicidial, magnus billing
VoIP et Téléphonie
I will do asterisks, voip, vicidial, freepbx, sip trunk, goautodial, twilio, vitalpbx

Portfolio

Expérience professionnelle

FreeSWITCH ESL Security Hardening & Live Panel Recovery on a Production FusionPBX Server

VoIP Business

Jun 2026 - Jul 20261 mo

The situation: A client running a live FusionPBX/FreeSWITCH VoIP system needed secure remote API access (ESL) so their application could pull real-time call events and send commands, without exposing the server to unauthorized access. What made it complex: Server was live, actively handling real business calls, so every change had to be zero-downtime Default configuration used a well-known factory password with no access restriction After securing the connection, the admin dashboard broke, requiring root-cause tracing through multiple independent layers: FreeSWITCH's own access control, OS-level firewall rules, fail2ban, and finally an undocumented password stored separately inside FusionPBX's own database Diagnosed and resolved a subtle "default-deny" behavior in FreeSWITCH's built-in loopback protection that silently blocked all non-local connections What was delivered: Hardened Event Socket Library (ESL) access: strong authentication, IP-based access control, dual-layer protection (application + firewall) Root-caused and fixed a dashboard outage introduced by the security changes, tracing it to a hidden, undocumented credential store Verified working end-to-end from the client's actual external application server Clear documentation so the client's team could maintain and extend the setup independently Why it mattered: This wasn't a "run one command" job. It required layered debugging across the OS, the telephony engine, the database, and the web application, on a system where mistakes could have dropped live customer calls. That's the kind of reliability and care that generic scripts or copy-paste tutorials can't offer.