Page tree
Skip to end of metadata
Go to start of metadata

Last update: 20 November 2012

www.vitelity.com

This method uses the static ip address of your FreeSWITCH configuration. Changes must be made to your account at vitelity.com and also to local FreeSWITCH files. Follow this guide for complete instructions.

Network Configuration

Before setting up the vitelity gateways be sure ports 5060-5061 and 5080 are not blocked on your FreeSWITCH server. You may have to configure port forwarding on your router to make this work correctly. For a quick and dirty setup place your FreeSWITCH server outside your firewall; know that this can be a security threat.

Vitelity Web Portal Setting

Login to your vitelity account at vietlity.com. You will see the new version 2 interface.

Click DIDs along the top tabs, then click sub accounts. Scroll to the bottom where you see IP address authentication. This is important! Enter your public ip address and port number 5080. Save it.

Click the top support tab and then the setup wizard link.

On the configuration page copy down the host for [vitel-inbound] (should be something like inbound#.vitelity.net. Also copy down the host for [vitel-outbound] (should be something like outbound.vitelity.net)

We now need to find out the password to your vitelity gateway. This is also called a secret. Click the top support tab. Choose switchvox configuration. A new page will open. Copy the password from the new screen. It will be some random set of letters and numbers.

You should have the following information:

vitelity.xml

Create a new file /usr/local/freeswitch/conf/sip_profiles/external/vitelity.xml

Copy and paste the following code to vitelity.xml. Adjust the setting to reflect the vitelity settings you just found. Reference the vitelity web portal configuration section above if you need help finding your credentials. Proxy values are the are the same as the hosts.

public.xml

Add this to freeswitch/conf/dialplan/public.xml

Changing data="1000 ..." to a different number will change the extension to which the call is directed to.

 

default.xml

Add this to freeswitch/conf/dialplan/default.xml Replace the efective_caller_id_number=18001234567 with your phone number

 

Finish Up

You'll need to do a rescan to load the new gateway.

 

From the command line will do, it will even reload the dialplan at the same time.


Try calling your vitelity DID. If a sip phone is registered to extension 1000 the phone should ring. If a phone is not registerd the call should go to voicemail.

Try calling out from extension 1000. Dial with a leading 1 and the area code. Also try dialing with just the area code. Both should work.

Credit goes to the FreeSWITCH wiki and IRC channel. I've just pieced everything together.

If you have any questions please feel to try and find me on the IRC channel. Name: jch.

Registration Method

This seems to work easier. No acl's to mess with, and add inbound/outbound routes as normal. Also better integration with FusionPBX if that's your flavor.

Log into the web portal and set/get the following info.

  1. set a username/password
    • DIDs -> Sub Accounts
    • Create a new login and set a password.
  2. Route to your Registered Account
    • My Account -> Routing
    • Select Set default route to the account 'wwwusername_somethingyouset'
  3. Get the Proxy and Outbound proxy servers
  4. Support -> Generic SIP

vim /usr/local/freeswitch/conf/sip_profiles/external/Vitelity.xml

 

Notes

  • DTMF: Some of the inbound and outbound SIP gateways/proxies utilize a combination of inband 2833 DTMF as well as did not handle FreeSWITCH's generated 2833 DTMF (for whatever reason). To mitigate this Vitelity assigned us to two different gateways: (Inbound/origination): inbound21.vitelity.net and (Outbound/termination): sip22.vitelity.net. This completely resolved our issues with intermittent DTMF issues on calls to various numbers as well as total non-operation with T-Mobile voicemail, Google Voice interaction, and POTS inband pass-through. Apparently these gateways use different "switches" which "handle DTMF differently." Submit a support ticket and they might move your account to those gateways if you're having issues.
  • RTP timeout: Vitelity has a 60-second timeout on the lack of RTP media stream packets (e.g. rtptimeout configuration in sip.conf on Asterisk). This manifests itself as dropped calls when recording audio (e.g. voicemail) after 60 seconds. This is because FreeSWITCH does not send RTP media when recording (to save bandwidth). FreeSWITCH SVN revisions before r13144 could not work around this. FreeSWITCH has a record_waste_resources channel variable which transmits empty frames during record. Note also that the conference application has similar parameters.