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

NAT and WebRTC (SOLVED)


OK, WebRTC has been defined barely yesterday, actually is being defined right now. It's completely unencumbered by legacy shortcomings, particularly when dealing with NAT. So let's say using WebRTC as transport solves all NAT problems.

You define your ext-rtp-ip and ext-sip-ip in SIP profiles, then your ext-rtp-ip in verto.conf.xml, and you're all set.

The magic of ICE, used by default by all WebRTC clients to determine how to connect, and implemented on FreeSWITCH side too, is almost sure to guarantee a perfect flow of signaling and media.

If you have a very strange situation, for example you want to use WebRTC inside LANs without using public addresses or DNS names, then you will need to implement your own ICE/STUN server and configure your WebRTC clients to use that server(s). But if you have such a project, you probably already know you need your ICE infrastructure.