How to setup VoIP destinations

A guide to set up Call Fowarding to a VoIP User can be found here

VoIP Destinations

A VoIP destination is an address on the Internet which can receive telephone calls using a VoIP protocol (for instance; SIP, IAX or H.323). The calls will travel over the Internet rather than the Public Switched Telephone Network (PSTN). Many companies who use in-house PBX or Call Management systems may wish to receive calls by VoIP as their system has Internet connectivity.

Like Telephone Numbers, VoIP destinations are provided and managed by service providers. Unlike Telephone Numbers, anyone with the equipment and know-how can build a VoIP system to receive calls over the Internet. Because of this there are hundreds of VoIP providers all offering a variety of different services in the market. Depending on what you are trying to achieve will depend on which kind of VoIP provider to use.

VoIP is generally the cheapest Call Forwarding option available (free in some cases). However, if you want to receive calls on your landline or mobile, it is unlikely that VoIP will help you. You may be able to forward you calls from a TTNC number to a VoIP provider for free, but they will charge you to get the call to your landline or mobile. This is because there is an inherent cost to call any telephone number (except for Freephone numbers). You may as well simply forward to your landline or mobile directly using TTNC, as this will mean fewer people in the chain, and higher reliability of service.

Some companies will describe telephone numbers, or telephone lines as VoIP numbers, or VoIP lines. They usually do this to describe the nature of their internal network, or how the calls are delivered to your home or business. If they provide you with a UK telephone number to receive calls, then this is not a VoIP destination and will have a charge associated with calling it.

SIP/IAX URIs

To set up VoIP Termination using myTTNC you'll need to type in a SIP or IAX URI. These look a little like email addresses. Please see the examples below:

[email protected] – using username and domain
[email protected] – using username and IP address
Username:[email protected] – using username, password and domain

Please specify the following for IAX or SIP:

I:[email protected] – if forwarding to IAX
S:[email protected] – if forwarding to SIP

These are only examples to demonstrate URI formatting and will not work if set up in myTTNC.

Your SIP provider may not give you your SIP destination in the form of a URI, but you can create one from your SIP credentials;

Username – this may be called your account number/name or your 'inbound route' name.
Password – you will probably have a couple of passwords from your VoIP provider to distinguish these. They may call this the 'secret'.
VoipHostDomain – this may be called the 'Domain', 'Host' or could be the inbound IP they provide.

Originating IP Addresses

Sometimes you may wish to protect your end equipment by placing it behind a firewall. Please can you ensure that at a minimum you allow incoming traffic from us on the following IP addresses on all ports:

SIP:
87.117.252.2
87.117.252.3
88.150.143.83
88.150.143.84
51.255.58.50
51.255.58.51
51.255.58.34
51.255.58.35
87.238.72.129
87.238.72.130
87.238.73.129
87.238.73.130
87.238.74.129
87.238.74.130

IAX:
87.117.252.7
87.117.252.8
88.150.143.85
88.150.143.86
51.255.58.54
51.255.58.55
51.255.58.37
51.255.58.38
87.238.72.140
87.238.73.140
87.238.74.140

RTP:
In addition, RTP traffic may originate from any of the IP addresses contained in the following subnets:

87.117.252.0/28
88.150.143.80/28
51.255.58.48/28
51.255.58.32/28
87.238.72.128/26
87.238.73.128/26
87.238.74.128/26
87.238.77.128/26

If you firewall UDP traffic on your network, you must ensure the above subnets are permitted.

DTMF

We support RFC2833 DTMF and inband DTMF.

Codec

We support G711a (PCMA).