Book Image

Mastering FreeSWITCH

By : Russell Treleaven, Seven Du, Darren Schreiber, Ken Rice, Mike Jerris, Kalyani Kulkarni, Florent Krieg, Charles Bujold
4 (1)
Book Image

Mastering FreeSWITCH

4 (1)
By: Russell Treleaven, Seven Du, Darren Schreiber, Ken Rice, Mike Jerris, Kalyani Kulkarni, Florent Krieg, Charles Bujold

Overview of this book

FreeSWITCH is one of the best tools around if you’re looking for a modern method of managing communication protocols through a range of different media. From real-time browser communication with the WebRTC API to implementing VoIP (voice over internet protocol), with FreeSWITCH you’re in full control of your projects. This book shows you how to unlock its full potential – more than just a tutorial, it’s packed with plenty of tips and tricks to make it work for you. Written by members of the team who actually helped build FreeSWITCH, it will guide you through some of the newest features of version 1.6 including video transcoding and conferencing. Find out how FreeSWITCH interacts with other tools and APIs, learn how to tackle common (and not so common) challenges ranging from high availability to IVR development and programming advanced PBXs. Great communication functionality begins with FreeSWITCH – find out how and get your project up and running today.
Table of Contents (21 chapters)
Mastering FreeSWITCH
Credits
About the Authors
About the Reviewers
Contributors
www.PacktPub.com
Preface
7
WebRTC and Mod_Verto
Index

Change passwords


In the standard "demo" installation, you have SIP users (for example, devices) named from "1000" to "1019" that can register (from the local LAN, not from the bad Internet outside) to FreeSWITCH with password "1234" defined in conf/vars.xml and then make and receive calls. If you don't change that password, you will experience a 20 second delay before connecting calls, and a flurry of red error messages on the fs_cli console and in the FS logs. Changing that password to something else will remove the nagging, but you can do more. Best practice would be to go to conf/directory/default and move all of its content away, then bring back the files you need one by one, and edit all the security information they contain, particularly:

     <param name="password" value="$${default_password}"/>
     <param name="vm-password" value="1001"/>

Use absolute values here instead of $${var} variables, and make them unique to each user, and not easily guessable.