Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
FreeSWITCH 1.8

You're reading from   FreeSWITCH 1.8 Get to grips with VoIP and WebRTC communication and quickly build robust telephony systems with FreeSWITCH

Arrow left icon
Product type Paperback
Published in Jul 2017
Publisher Packt
ISBN-13 9781785889134
Length 434 pages
Edition 1st Edition
Concepts
Arrow right icon
Authors (2):
Arrow left icon
Anthony Minessale II Anthony Minessale II
Author Profile Icon Anthony Minessale II
Anthony Minessale II
Giovanni Maruzzelli Giovanni Maruzzelli
Author Profile Icon Giovanni Maruzzelli
Giovanni Maruzzelli
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Architecture of FreeSWITCH FREE CHAPTER 2. Building and Installation 3. Test Driving the Example Configuration 4. User Directory, SIP, and Verto 5. WebRTC, SIP, and Verto 6. XML Dialplan 7. Phrase Macros and XML IVRs 8. Lua FreeSWITCH Scripting 9. Dialplan in Deep 10. Dialplan, Directory, and ALL via XML_CURL and Scripts 11. ESL - FreeSWITCH Controlled by Events 12. HTTAPI - FreeSWITCH Asks Webserver Next Action 13. Conferencing and WebRTC Video-Conferencing 14. Handling NAT 15. VoIP Security 16. Troubleshooting, Asking for Help, and Reporting Bugs

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...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image