Book Image

FreeSWITCH 1.2 - Second Edition

Book Image

FreeSWITCH 1.2 - Second Edition

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. It is always exciting to design and build your own telephony system to suit your needs, but the task is time-consuming and involves a lot of technical skill."FreeSWITCH 1.2" comes to your rescue to help you set up a telephony system quickly and securely using FreeSWITCH. It is rich with practical examples and will give you all of the information and skills needed to implement your own PBX system.You will start with a detailed description of the FreeSWITCH system architecture. Thereafter you will receive step-by-step instructions on how to set up basic and advanced features for your telephony platform.The book begins by introducing the architecture and workings of FreeSWITCH before detailing how to plan a telephone system and then moves on to the installation, configuration, and management of a feature-packed PBX. You will learn about maintaining a user directory, XML dial plan, and advanced dial plan concepts, call routing, and the extremely powerful Event Socket. You will finally learn about the online community and history of FreeSWITCH."FreeSWITCH 1.2" is an indispensable tool for novice and expert alike.
Table of Contents (24 chapters)
FreeSWITCH 1.2
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Protecting passwords


Passwords are used in FreeSWITCH when phones register. When FreeSWITCH registers to external gateways and when administrators authenticate into the FreeSWITCH system itself. Most of these areas utilize weak plaintext passwords.

In addition, many users set their passwords to simple easy-to-guess combinations. Worse yet, some don't ever change or set up their voicemail boxes, leaving the defaults in place.

These passwords are very often targeted and once gained, they are exploited to commit fraud.

There are a few mechanisms available to mitigate this.

Registration passwords

Registration credentials do not need to be passed or kept on disk in plain-text. When defining SIP credentials in your folder, instead of including the following line:

<param name="password" value="samiam"/>

replace it with a pre-calculated a1-hash of the password, like the following:

<param name="a1-hash" value="c6440e5de50b403206989679159de89a"/>

To generate a1-hash, get the md5 of the string username...