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

Conditions (and "patterns")


Conditions are, broadly speaking, the building blocks for the "patterns" we talked about before in this chapter.

Conditions are contained by "extension". Conditions contain "action". Conditions have the following generic appearance:

<extension name="this_extension"> 
   <condition field="destination_number" expression=""^1234$"> 
         <!-- action --> 
         <!-- action --> 
   </condition> 
</extension> 

Inside a dialplan "context" (that is, it would be inside "default" or "public" context in demo configuration) we have a opening "extension" tag, then conditions begin. Between the opening and closing condition tag, we find actions.

In this case the condition will check if the "destination_number" call variable is matched by the "expression" (regular expression, or regex) "^1234$". If the number called was actually 1234, then the action(s) contained between this one condition opening and closing tags will be added to the TODO...