FreeSWITCH™ is a scalable open source cross-platform telephony suite designed to route and interconnect popular communication protocols using audio, video, text or any other form of media. From a Raspberry PI to a multi-core server, FreeSWITCH can unlock the telecommunications potential of any device.
FreeSWITCH also provides a stable telephony platform on which many telephony applications can be developed using a wide range of free tools.
Additional documentation:
Get in touch with FreeSWITCH here
Check out their help section for community or paid support.
Instructions For Configuring a FreeSWITCH IP Trunk
In this guide, you will:
Pre-Requisites
Create an IP connection on your Telnyx Mission Control Portal account, assigned this connection to a DID and outbound profile in order to make and receive calls.
IMPORTANT: FreeSWITCH™ v1.8 has been tagged End of Life. If you are on this version, you must upgrade. |
1. Configuring the Telnyx Mission Control Panel
For step-by-step instructions on each of the requirements on the Telnyx Mission Control Portal, please follow this guide.
Once you've configured your Telnyx account, you can now proceed to setup FreePBX V13 following the guide below.
2. Update default credentials
Your new FreeSWITCH instance is preconfigured with default credentials that must be changed to prevent unauthorized users from registering with your instance and making calls.
Open vars.xml:
root@ip1723154222:/# cd /usr/local/freeswitch/conf root@ip1723154222:/usr/local/freeswitch/conf# vi vars.xmlFind the line that begins with
<X-PRE-PROCESS cmd="set" data="default_password="Change the default password.
3. Update the external SIP profile
Navigate to sip_profiles/external.xml
...# cd sip_profiles
.../sip_profiles# vi external.xmlUncomment the following lines:
<param name="ext-rtp-ip" value="$${external_rtp_ip}"/>
<param name="ext-sip-ip" value="$${external_sip_ip}"/>
4. Create the SIP Trunk and build it to Telnyx
There are multiple ways that this can be accomplished, but the easiest way is to build your own gateway under the external SIP profile.
Navigate to the sip_profiles/telnyx.xml
.../sip_profiles# cd external
.../sip_profiles/external# vi telnyx.xmlYou'll see something like this:
<include>
<gateway name="telnyx">
<param name="proxy" value="dspfree.pstn.telnyx.com"/>
<param name="register" value="false"/>
<param name="caller-id-in-from" value="true"/> <!--Most gateways seem to want this-->
<param name="username" value="not-used"/>
<param name="password" value="not-used"/>
</gateway>
</include>
5. Create a Dialplan
Note that this is a sample dialplan, as each dialplan is typically unique. For more defailed information about setting up a FreeSWITCH dialplan, see FreeSWITCH's documentation.
Navigate to /user/local/freeswitch/conf/dialplan/public
Remove the files located here and create a new inbound dialplan xml. Here is an example of what this will look like:
<include>
<extension name="public_did">
<condition field="destination_number" expression="^(1{0,1}\d{10})$">
<action application="set" data="effective_caller_id_number=13125489677"/>
<!-- Replace 3125489677 with the DID you want as CID -->
<action application="bridge" data="sofia/gateway/telnyx/$1"/>
</condition>
</extension>
<extension name="local.com">
<condition field="destination_number" expression="^(\d{7})$">
<action application="set"
data="effective_caller_id_number=${outbound_caller_id_number}"/>
<action application="set"
data="effective_caller_id_name=${outbound_caller_id_name}"/>
<action application="bridge"
data="sofia/gateway/telnyx/+1${default_areacode}$1"/>
</condition>
</extension>
<extension name="domestic.com">
<condition field="destination_number" expression="^(\d{11})$">
<action application="set"
data="effective_caller_id_number=${outbound_caller_id_number}"/>
<action application="set"
data="effective_caller_id_name=${outbound_caller_id_name}"/>
<action application="bridge" data="sofia/gateway/telnyx/+$1"/>
</condition>
</extension>
<extension name="international.com">
<condition field="destination_number" expression="^(011\d+)$">
<action application="set"
data="effective_caller_id_number=${outbound_caller_id_number}"/>
<action application="set"
data="effective_caller_id_name=${outbound_caller_id_name}"/>
<action application="bridge" data="sofia/gateway/telnyx/+$1"/>
</condition>
</extension>
</include>
6. Network configuration
If you want to use the same profile for communication both inside and outside your network, you will need to tell FreeSWITCH™ when it should use the local IP or the external IP.
The autonat: prefix toggles on the usage of the local-network-acl, if you prefix the IP like that it will activate the dynamic ability to tell when it should use ext-rtp-ip vs rtp-ip based on the acl match.
<param name="ext-sip-ip" value="autonat:$${external_sip_ip}"/>
Note: In case FreeSWITCH fails to recognize your public IP you may "force" it to use a static Public IP by modifying sip_profiles/external.xml as follows:
<param name="ext-rtp-ip" value="8.8.8.8"/>
<param name="ext-sip-ip" value="8.8.8.8"/>
<!-- Replace 8.8.8.8 with your public IP -->
Additional Resources
Review our getting started with guide to make sure your Telnyx Mission Control Portal account is setup correctly!
Additionally you can:
Get in touch with FreeSWITCH here
Check out their help section for community or paid support.