Contents[ hide ] |
Example Configuration
The following is a list of phone providers that have been successfully tested with the FreeSWITCH software.
Please note that you should stick with adding these phone providers under the {FreeSWITCH installation}/conf/directory/default location. This means creating an XML file per specified phone provider under the conf/directory/default/ directory. Alternatively, you can also add the provider of your choice under the {FreeSWITCH installation}/conf/sip_profiles directory. The recommendation is to stick with using the "conf/directory/default" location. When in doubt copy the examples found in the source code under freeswitch/conf/directory/default/ . The sample file is named "provider .com.xml ". NOTE: the file is named "example .com.xml " on newer releases of FreeSWITCH.
Provider Configuration Pages
When adding a provider to this list within the wiki please observe these guidelines:
- include a generic configuration
- no marketing information
- keep them alphabetically listed
| A through E | F through H | I through P | Q through Z |
Note: If you are looking for an example with different destinations for the registration proxy and outbound proxy, see the example configuration for Peopleline.
Gateway Overview
As an example we will add a trunk to vitelity.com. PLEASE NOTE THAT THIS IS AN EXAMPLE. REPLACE WITH YOUR OWN CONFIGS FOR YOUR PROVIDER (see table below).
Vitelity.com uses different proxies for inbound and outbound calls, so we need to add two gateways (they can be in the same file). One for outbound and one for inbound. Many providers (Vitelity included) allow you to make outbound calls via the registration proxy for inbound calls and so you really only *need* to setup one gateway. Before we start that we'll need to know a couple different pieces of info:
- username
- password (also called secret)
- outbound server
- inbound server
sudo vim /usr/local/freeswitch/conf/sip_profiles/external/vitelity.xml
<include>
<gateway name="vitelity-outbound">
<param name="username" value="****yourusername"/>
<param name="password" value="****yourpassword"/>
<param name="realm" value="vitel-outbound"/>
<param name="proxy" value="****outboundurl"/>
<param name="register" value="false"/>
</gateway>
<gateway name="vitelity-inbound">
<param name="username" value="****yourusername"/>
<param name="password" value="****yourpassword"/>
<param name="realm" value="vitel-inbound"/>
<param name="extension" value="1000"/>
<param name="proxy" value="****inboundurl"/>
<param name="register-proxy" value="****inboundurl"/>
</gateway>
</include>
Keeping Connections Alive
You can use the following parameter in your configuration to force FreeSWITCH to re-register with your provider at certain intervals. This may be helpful for NAT issues by keeping the connection state open through your internal firewall.
<param name="expire-seconds" value="60"/>
You can also set FreeSWITCH to ping your gateway at intervals.
<param name="ping" value="30" />
See Also
<!-- NewPP limit report Preprocessor node count: 33/1000000 Post-expand include size: 854/2097152 bytes Template argument size: 699/2097152 bytes Expensive parser function count: 0/100 --><!-- Saved in parser cache with key wiki:pcache:idhash:1952-0!1!0!!en!2!edit=0 and timestamp 20101127015348 -->
