Telstra - SIP Connect (Enterprise Trunk)
On this topic
Telstra’s SIP Trunking solution is simple, flexible and gives users complete control over their service as they can manage it themselves from the online portal. With a wide range of plans and options to choose from Telstra’s SIP Trunking solution is ideal for any Australian business being a start-up or a large enterprise.
Reference website: Telstra
Before configuring the SIP trunk it is required to go through the following checklist and make changes where necessary:
- NAT (when used) created to 3CX
- Firewall Checker passed
- Firewall SIP ALG checked and if present disabled
Further setup information can be found in our Academy: 3CX Academy Basic Course.
Some providers gained support and compatibility with 3CX on a specific product version. It is advisable to always run the latest version of 3CX to ensure ongoing compatibility.
Minimum 3CX Version: 3CX Phone System 15.5 SP5
Below is a short overview of the provider's capabilities and services and whether they’re supported or not:
- CLNS (Clip No Screening): No
- Catch All Routing: Yes
- Fax T.38 support: No
- CLIR (Number Suppression): Yes
- DTMF via RFC 2833: Yes
- Codec Order: G722, G711A, G711U, G729
- NAT Support: Yes
Before starting to configure your Telstra SIP Connect Enterprise Trunk in 3CX, you must first make sure that your network is setup correctly.
What you will need to have before reading this section is the following:
- The Telstra Edge Router IP(s).
- The Primary and Secondary Telstra DNS Servers.
- The SBC FQDN(s) Telstra has instructed you to connect to.
All of the above will be provided to you by your Telstra representative.
In order to use a Telstra SIP Connect Enterprise Trunk, you will be provided with a Edge Router device that will be managed by Telstra and through which you will be exchanging VoIP traffic with the Telstra network. The network topology should look similar to the following:
In the above network topology example, the 3CX Server will be accessing the internet via the Internet GW, while all Enterprise Trunk related traffic will be traversing the Telstra Edge Router device.
3CX Server NIC Setup
Following the above example, the NIC on the 3CX Server will have the Internet GW as its Default Gateway. In order however for the SIP traffic to traverse the Telstra Edge Router, there is some configuration that is required.
The first thing you must do is add the 2 Telstra DNS Servers as primary and secondary in the NIC settings of the 3CX Server. The DNS IPs will be provided to you by your Telstra representative.
The reason this is necessary is because Telstra provides you with a specific Outbound Proxy which is only resolvable by these DNS Servers.
Important! Failing to set the DNS servers will result in your Enterprise Trunk not registering.
Adding Static Routes
Next you must add some static routes so that the traffic from the 3CX server towards the Telstra servers is routed out through the correct Gateway. To do this on a Windows OS, you would open a command prompt using the “Run as Administrator” option, then run the following commands:
- Static Routes for the DNS Servers:
route -p add [Primary DNS IP] mask 255.255.255.255 METRIC 1 [Telstra Edge Router IP]
route -p add [Secondary DNS IP] mask 255.255.255.255 METRIC 1 [Telstra Edge Router IP]
route -p add 10.86.113.20 mask 255.255.255.255 METRIC 1 10.2.2.1
route -p add 10.86.114.20 mask 255.255.255.255 METRIC 1 10.2.2.1
After adding these static routes, it is recommended that you check that the 2 DNS servers are reachable from the 3CX Server and that they accessed through the correct Gateway. To do this you can use the “tracert” command from the command prompt.
- Static Route for Telstra SBCs:
Telstra SIP Connect Enterprise Trunks usually consist of at least 2 Trunk Groups, each of which will register against a different Telstra Regional SBC, thus offering resilience.
At this point you must find the IP of the Outbound Proxies (SBCs) that Telstra has instructed you to use. To do this open the command prompt and type in the command:
nslookup [SBC FQDN] [Primary Telstra DNS Server]
nslookup sbc-cw.ipvs.net 10.86.113.20
Repeat this for each Outbound Proxy (SBC) address/FQDN Telstra has provided you with.
Once you have the IP addresses, you need to add static routes for each IP as well to be routed through the Telstra Edge Router IP:
route -p add [Telstra SBC IP] mask 255.255.255.255 METRIC 1 [Telstra Edge Router IP]
route -p add 192.168.175.132 mask 255.255.255.255 METRIC 1 10.2.2.1
Remember to add a static route for each Outbound Proxy (SBC) IP you have been instructed to use.
After adding the static routes, it is again recommended that you check that the SBC IPs are reachable from the 3CX Server and that is accessed through the correct Gateway(s) using the “tracert” command.
- The IPs and FQDNs in this section used as examples may vary from the ones you must use. If you are unsure which information you must use, contact your Telstra representative.
- The Internal LAN IP that your Telstra Edge Router will have must be according to RFC1918 (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16).
Configuring the Trunk with 3CX
The general instructions outlining how to add a new SIP Trunk to your 3CX installation can be found here.
Collecting 3CX Configuration Information
After the network configuration, it is time to set up your Telstra SIP Connect Enterprise Trunk in 3CX. Before starting, make sure you have the following information available as given to you by your Telstra representative in the RRAS Order:
- Outbound Proxy/SBC FQDNs
- SIP Realm/Domain
- Trunk Pilot Numbers of all the Trunk Groups
- Authentication User IDs of all the Trunk Groups
- Authentication User Passwords of all the Trunk Groups
- Number range/DIDs of all the Trunk Groups
With the above information you can proceed to the next section which explains how you use this information to configure the Trunk in 3CX.
Adding the Trunk
Telstra SIP Connect Enterprise Trunks usually consist of more than 1 Trunk Groups. This means that each Trunk Group registers against the Telstra SBCs individually. This means that each Trunk Group in 3cx will be a separate “SIP Trunk” entry.
Also note that each of your Trunk Groups can either be registered on a single 3CX Server, or you can have a Trunk Groups registered on multiple 3CX Servers spanned across multiple physical sites. For more information about which setup suits your needs best, it would be advised to speak with your Telstra representative.
To register an Enterprise Trunk Group in 3CX, go to “SIP Trunks” and select “Add SIP Trunk”
- Select Country: AU
- Select Provider in your Country: Telstra - SIP Connect (Enterprise Trunk)
- Main trunk number: Enter the Trunk Pilot Number in a 9-digit format (National excluding the leading ‘0’), e.g. 280743741
- Press OK
Under the “General” tab in the “Authentication” section, fill in the information as shown below.
Important! In the “Registrar” field, make sure that “transport-tcp.” is proceeding the SIP Realm as you enter it. If for example your SIP Realm is “sip.contoso.com”, you would enter “transport-tcp.sip.contoso.com”.
At this point you may also want to adjust the value of “Number of SIM Calls” to match the number of SIP Channels your Telstra Trunk Group allows for.
Once you have filled in these fields as given to you by Telstra, scroll to the top of the page and press OK. At this point if you refresh the page you should see your Telstra Trunk appear as Registered.
Note: If you will be registering all you the Enterprise Trunk Groups on the same 3CX installation, repeat this section for each Trunk Group. It is also recommended that you slightly variate the Trunk Name for each SIP Trunk you create in 3CX.
Adding Additional DIDs
Each Telstra Enterprise Trunk Group has a unique DID/Number range allocated to it, however any Trunk within the Enterprise Trunk can send and receive calls from any of the DIDs contained in the Enterprise construct. This means that all of your DIDs of all your Trunk Groups, should be associated with each one of the “SIP Trunk” entries you have created in 3CX.
To associate all the DIDs/Number, go to the Management Console → SIP Trunks, double-click on your Telstra Trunk and go to the “DIDs” tab.
Here you should already see 1 entry, the Main Trunk number you have set. Add all other DIDs/Numbers you have to the list in a 9-digit format (National excluding the leading ‘0’).
Remember to repeat this for each one of your “SIP Trunk” entries, each time adding all the DIDs of all your Trunk Groups.
Creating Inbound Rules
Now that you have associated all your DIDs/Numbers with your SIP Trunk in 3CX, you can create Inbound Rules to set where calls will be routed when those numbers are called. Instructions on how to create Inbound Rules can be found here.
When configuring Telstra Enterprise Trunks in 3CX, all numbers should be entered in a 9-digit format (National excluding the leading ‘0’)
Outbound Caller ID
Telstra Enterprise Trunks allow you to present any one of your DIDs as the Caller ID when making Outbound Calls. For this to work, when configuring the Outbound Caller ID in 3CX, make sure that you enter the numbers in a 9-digit format (National excluding the leading ‘0’), e.g. 280743741.
When configuring your Outbound Rules make note that Telstra allows outbound calls to be made in any valid number format.
More information about how to create Outbound Rules and how they work can be found here.
As mentioned earlier in this guide, Telstra SIP Connect Enterprise Trunks consist of multiple Trunk Groups, each of which registers individually to a different SBC on the Telstra network.
If you have multiple Trunk Groups registered in the same 3CX system, you can do the following to setup redundancy for incoming and outgoing calls.
Inbound Call Routing
When creating Inbound Rules, you now need to create multiple rules for each DID/number, once for every Trunk Group you have registered on your 3CX system. This way, regardless which Telstra SBC the call originates from, the call will still be routed inbound to the correct destination. An example of such a setup is shown below:
Outbound Call Routing
For your Outbound Rules, in order to make use of the multiple Trunk Groups, all you need to do is make sure that you have set them as the subsequent “Route” options. An example of an Outbound Rule is shown below:
On the Telstra network, there is a Malicious Call Trace (MCT) function that can be initiated. The Feature Access Code for this function is *57. In order for this functions to work correctly for endpoints via 3CX, you must do the following:
- Make sure you have created an Outbound Rule in 3CX that allows for dialing this number.
- The default 3CX dial code for CLIR is *5 which conflicts with this function. You must go to the Management Console → Settings → Dial Codes and change the “Block Outbound Caller ID” dial code to a different value.