How SIP Trunking Works with Thinktel
To request a SIP trunk interop with ThinkTel, please fill out this form
The following are the basic settings required to start a SIP trunk interop with ThinkTel.
Our main switch is located in Edmonton: Metaswitch - 18.104.22.168
Signalling and RTP Information by Proxy
For edm.trk.tprm.ca, tor.trk.tprm.ca, eico.thinktel.ca(non-Microsoft Lync)
Signalling - If using any of these proxies you will need to allow UDP 5060 signalling as appropriate:
Þ edm.trk.tprm.ca (22.214.171.124) Primarily assigned to Western Canada based PBX trunks - accepts NAT and public IP
Þ tor.trk.tprm.ca (126.96.36.199) Primarily assigned to Eastern Canada based PBX trunks - accepts NAT and public IP
Þ eico.thinktel.ca (188.8.131.52) Legacy proxy for public IP PBX trunks
RTP - If using any of these proxies you will need to allow RTP UDP for ports 10000 through 65500 as appropriate:
Þ edm.trk.tprm.ca 184.108.40.206/27, 220.127.116.11/27, 18.104.22.168/26
Þ tor.trk.tprm.ca 22.214.171.124/27, 126.96.36.199/27, 188.8.131.52/26
Þ eico.thinktel.ca 184.108.40.206/27, 220.127.116.11/27, 18.104.22.168/27, 22.214.171.124/27, 126.96.36.199/26, 188.8.131.52/29, 184.108.40.206/27 (Added Feb 2018), 220.127.116.11/28 (Added Jun 2018)
To find out more info on migrating your services from eico.thinktel.ca over to our new geographically located proxies edm.trk.tprm.ca(West Coast) or tor.trk.tprm.ca(East Coast) please review article SIP Proxy Migration
For edm.ocs.tprm.ca, tor.ocs.tprm.ca (Microsoft Lync)
Signalling - For Lync proxies you will need to allow TCP 5060 signalling as appropriate:
Þ edm.ocs.tprm.ca (18.104.22.168) Western Canada based Lync trunks
Þ tor.ocs.tprm.ca (22.214.171.124) Eastern Canada based Lync trunks
RTP - For Lync proxies you will need to allow RTP UDP for ports 49152 through 57500 as appropriate. You must allow all outbound UDP traffic to us on ports 10000 through 65535.
Þ edm.ocs.tprm.ca 126.96.36.199/27, 188.8.131.52/27, 184.108.40.206/26
Þ tor.ocs.tprm.ca 220.127.116.11/27, 18.104.22.168/27, 22.214.171.124/26
For more information on the required ports your mediation server must have published please see the following Microsoft documentation.
We identify each SIP trunk with a pilot number, a 10 digit number local to your VoIP gateway, similar to how Telco's assign pilot numbers to conventional PRI's. Please refer to your pilot number when placing orders for DIDs, channels, etc. The requested number of channels for a SIP trunk is activated once the initial interop stage is complete and your account is active with ThinkTel. This can also be done via uControl.
Ensure that your PBX or gateway supports DNS SRV records.
By default, we offer the following codecs: G711, G729 (renegotiation to T.38 is accepted from g711 when supported for Fax over IP). Other codecs might be available upon request.
Configure your gateway to send and receive 10 digit North American numbers. 11 digit is available upon request.
Configure DTMF for RFC2833 (out of band).
If you are running Asterisk, TrixBox or OpenPBX, please ensure that canreinvite=no is set in the SIP settings.
Disable any SIP ALG service on a routers or firewalls as it is not compatible with our services. If enabled you may experience registration or audio related issues that will negatively impact your ability to use our service.
Our switch sends out a SIP keep-alive OPTIONS request to the contact IP for your SIP trunk every 30 seconds.
This is a standard SIP OPTIONS request that must be responded to with any valid SIP response. If no response
is received within 30 seconds of the request, the switch will send a request every 4 seconds, disable the SIP
trunk binding associated with that particular IP and will not send further SIP invites until a response is
received. This negates the need for REGISTER and registration should be disabled whenever possible.
We authenticate calls by both methods:
• IP address: the VIA and Contact header must contain your contact IP address and port.
• SIP credentials: the supplied username and password credentials must be sent in the authentication digest
for all SIP requests that require authorization (INVITE, UPDATE, BYE, etc).
We allow up to 8 IP addresses per SIP trunk.
• Each IP address/port combination creates a "binding" that is assigned to your SIP trunk.
• Assigning the same binding to multiple SIP trunks can be accomplished with the following restriction:
o Only one trunk is allowed to manage changing the caller ID with the use of a Custom Calling Party ID number.
o Example: If 3 different SIP trunks all use the same binding, only one of the SIP trunks will be configured to allow an arbitrary calling party number. That SIP trunk and associated charge number (Pilot) will be billed for all calls that have a Custom Calling Party caller ID.
Each binding/IP assigned to a SIP trunk is used for origination and termination.
• The following options are available to route calls to your binding(s) / IP address(es):
o Round Robin: Incoming calls are sent to each binding assigned in your SIP trunk in turn. If the SIP
response from your gateway is > 303 (404/Not Found or 503/Unavailable), our switch will send an INVITE to
the next IP address until the INVITE is accepted with a SIP response < 303.
o Lowest Available: Use the preferred binding for as long as the trunk/binding will permit it and move on to
the next in the list if the ones before are full/unavailable.
- You can configure an Unavailable Call Forward for the SIP trunk as well as for individual DIDs. If all of
your bindings are down (not responding to our OPTION requests) calls will be forwarded to the defined Call
Forward. The full procedure is documented here.