XML Configuration
FreeSWITCH understands its configuration in terms of an all-encompassing XML tree. That XML tree is continuously searched and queried, as long as FreeSWITCH is running. Each time the FreeSWITCH core, or one of the modules, needs whatever information from the configuration, they ask (again and again) for that specific snippet of configuration. For example, let's imagine a SIP phone (or a WebRTC client) originates a call. The call is originated by user 1010@mydomain.org. When the first signaling of the originating call reaches FreeSWITCH, then the mod_sofia module (responsible for SIP) or mod_verto (responsible for... Verto!) will need to check the user authorization to make that call. The module will ask: in the users' directory, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access