Book Image

FreeSWITCH 1.8

By : Anthony Minessale II, Giovanni Maruzzelli
Book Image

FreeSWITCH 1.8

By: Anthony Minessale II, Giovanni Maruzzelli

Overview of this book

FreeSWITCH is an open source telephony platform designed to facilitate the creation of voice and chat-driven products, scaling from a soft-phone to a PBX and even up to an enterprise-class soft-switch. This book introduces FreeSWITCH to IT professionals who want to build their own telephony system. This book starts with a brief introduction to the latest version of FreeSWITCH. We then move on to the fundamentals and the new features added in version 1.6, showing you how to set up a basic system so you can make and receive phone calls, make calls between extensions, and utilize basic PBX functionality. Once you have a basic system in place, we’ll show you how to add more and more functionalities to it. You’ll learn to deploy the features on the system using unique techniques and tips to make it work better. Also, there are changes in the security-related components, which will affect the content in the book, so we will make that intact with the latest version. There are new support libraries introduced, such as SQLite, OpenSS, and more, which will make FreeSWITCH more efficient and add more functions to it. We’ll cover these in the new edition to make it more appealing for you.
Table of Contents (23 chapters)
Title Page
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface

Exploring and Using the Demo Example User Directory


After a fresh install, out of the box, you'll find the "directory" main XML file located at /usr/local/freeswitch/conf/directory/default.xml . That main file will then include many other files, as we'll see.

Let's understand its most important lines.

Domains and groups

First things first, we set the "domain" we're talking about. In SIP and in Verto, addresses are in the form "userid@domain", very much like in email (actually SIP borrowed this format from SMTP, the mail protocol, and Verto borrowed it from SIP). We can have multiple "domain" items, they would be added after the closing </domain> XML tag (not in the screenshot).

Then, a "params" XML container starts, surrounding the "param" items that belongs directly to the "domain" we're defining. Those "param" items will be linked to both the "users" that are contained into this domain, and the "group" items (then, the "user" items that belong to the "group" items) contained into the...