SIP Trunk Configuration for FreePBX

24 September 2014 | SIP Trunk telgo.SIP Connector

We’re staying on the subject of sip trunking today. This time we have installation guidance for SIP Trunks for FreePBX.

 

This setup information and the screenshots were kindly provided by a customer who has documented his PBX setup with the telgo.SIP Connector. To help speed up your setup, we would like to share these screenshots and comments.

 Obviously, this information (it is not advice) is provided “as is” without any representations or warranties, express or implied.

 

As previously mentioned: these are screenshots of a FreePBX Phone System with a telgo SIP Trunk. Thanks to Gerold G. for sending this in. Further inputs and information are always welcome (please don’t forget to send screenshots).

 

And here are the screenshots and comments:

 

 

Note 1:

The SIP Trunk is created here. It needs a name; in this case it has been called telgoSIPConnector. The outbound caller ID is set to the pilot number in E.164 format (international format without the leading zeroes), and “Allow Any CID” (Caller ID) is set for outgoing Calls.

Use the “Allow Any CID” setting if you want to set the caller’s number when you transfer a call to an external telephone. This requires the telgo CLIP No Screening option (available as an option for your package) to work. If you use another setting (e.g Block Foreign CIDs) The callee will see the PBX phone number / pilot number (and not the original caller’s number) for transferred or redirected calls.

The maximum number of channels needs to be set to the same number you purchased with your telgo.SIP Connector (standard is 4) in order to assure correct call handling.

 

Note 2:

Enter the username you received from telgo in this field.

This sample configuration is set to “allow = all”, which can lead to unexpected results if you use unsupported codecs.

We suggest using this configuration instead:

disallow=all
allow=G.722 (only if HD audio is enabled in your package and your bandwidth supports it)
allow=alaw
allow=ulaw
allow=G.729

 

 

 

Note 1:

Insert the username and password you received from telgo here.
This registers your PBX with our telgo.SIP Connector and is necessary to receive calls.

 

 

INBOUND and OUTBOUND Routes

 

Note 1:

After entering a fitting description, e.g. “telgo_inbound”, you will need to enter your pilot number in E.164 format (international format without leading zeroes).

 

Note 2:

You can use the CallerID Number in combination with the CID Priority checkmark to create special inbound rules for certain CallerIDs. 

In this case it is left empty because this inbound rule should work for all incoming calls.

 

Note 3:

Here the destinations for inbound calls are configured so they can actually ring somewhere.

In most cases extensions or groups need to be configured beforehand on your FreePBX.

 

 

 

 

Note 1:

Choose a descriptive name, and for telgo.SIP Connector set the RouteCID to “trunk1.at.telgo.cc”.
You can skip the Route Password. This would enable you to set a Password the user needs to provide before making a call via this particular route.

 

Note 2:

You can define dial patterns that determine which destination numbers will use this route.
Enter “X.” to make all destinations available via this route.

Alternatively, for example if you want your route to be used only for calls to numbers longer than 4 digits, you would use “XXXX.”
For more information on Asterisk pattern matching visit https://wiki.asterisk.org/wiki/display/AST/Pattern+Matching

 

Note 3:

Here we choose which SIP Trunk to use for this outgoing route. In our case this is the telgo.SIP Connector.

 

 

 

All the best for your install.

We hope these screenshots are helpful for your configuration.

 

Please note that this is not a complete installation guide.

It should help you to quickly get a working configuration for your FreePBX System with a telgo SIP Trunk.

Verify the integrity and security of your configuration before going live or connecting to any networks!

 

Don’t hesitate to send us any additional information or comments – and don’t forget the screenshots!

 

 

Previous Post Next Post