| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
This document will guide you through the process of configuring the Session Border Controllers to work with FreePBX or PBXact. There are two major applications - 1) SIP Trunking solutions, 2) Remote Phone solutions. This document describes the configuration of SIP Trunking.
Introduction
For Trunking solutions, SBC to FreePBX - PBXact Configuration Guide provides detailed information about the configuration requirements in the SMB SBC, Vega SBC, Netborder SBC and the Software VM SBC. A typical deployment connects SIP Trunking Service Provider across Internet or other networks into the SBC, where the SBC provides Security, Routing, Interoperability and more, then delivers the SIP Trunk call to the FreePBX - PBXact IP-PBX. Using SIP Protocol the SBC and the FreePBX - PBXact create a Trunk together.
...
SIP Trunking
Bringing SIP Trunks from SIP Trunking Service Providers into the SBC and then deliver the SIP Trunk calls to the FreePBX - PBXact.
...
FreePBX - PBXact IP: 192.168.77.112
SBC LAN IP: 192.168.77.124
SBC DMZ IP: 10.10.32.170
SBC Public WAN IP: 104.145.12.182
ITSP FQDN: itsp.sangoma.com
| Info |
|---|
Note: In the following configuration example, this is a DMZ-LAN setup of the SBC, and the FreePBX-PBXact is located on a Private LAN. This is one of many different network topologies that the SBC supports. Not all network topologies will be documented in the document, please consult other Wikis for slight changes in deployment styles of the SBC. Slight changes in configuration from this example to other network topologies are expected. |
FreePBX-PBXact Configuration
General Configuration
The FreePBX-PBXact will typically have a Static IP or Fully Qualified Domain Name. In this configuration we are defining the SBC as a Trunk, then assigning a Outgoing Calls and Incoming Calls to/from the SBC.
Trunks
Open the Trunks Module. ( Connectivity > Trunks )
...
host=192.168.77.124 - This is the IP Address of the SBC Internal LAN interface
port=5060 - This is the Port of the SIP Profile on the SBC Internal LAN Interface
type=peer - We are creating a Peer relationship with the SBC, no Registrations - IP Authentication only
disallow=all - Disallow all codecs
allow=ulaw - Then define the list of codecs to send to the SBC
context=from-pstn - Define the Asterisk Context as from-pstn
sendrpid=yes - Optional. Turn on the use of sendipid
trustrpid=yes - Optional. Turn on the Asterisk to trust the RPID
dtmfmode=rfc2833 - Use rfc2833 for DTMF
...
| Info |
|---|
Note: When Peer is selected, the FreePBX-PBXact Admin GUI doesn't report on the state of that peer, so it shows up as Unmonitored in the Server>Connection Status>VoIP Providers. |
.png?version=1&modificationDate=1703875586298&cacheVersion=1&api=v2&width=400)
Click "Submit"
...
Inbound Routes
Open the Inbound Routes. ( Connectivity > Inbound Routes )
...
Description: Any Description - SBC
DID Number: Enter in the DID (or range) being delivered from the SBC
CallerID Number: This is a filter, to match for the Source CallerID
Alert Info: Optional. Change the Ringer type
Set Destination: Select the Destination to ring when a voice call comes in over this SBC or channel. The destination can be any extension type (your receptionist’s phone, an IVR, Queues, etc.).
...
Click "Submit"
...
Outbound Routes
Open the Outbound Routes. ( Connectivity > Outbound Routes )
...
Run through the Dial Plan Wizard. Or configure your Dial Plan.
...
Click "Submit"
...
SBC Configuration
General Configuration
The following configuration will focus on the FreePBX-PBXact to SBC requirements. It is only half of the configuration needed for proper operation, as the SIP Trunking Service Provider will also need to be configured, along with the External WAN interface and external SIP Profiles and related configuration. The document will reference the SIP Trunking Service Provider but not show how to configure the provider. There are other Wiki's that document how to configure SIP Trunking with SIP Trunking Service Providers.
...
FreePBX-PBXact IP: 192.168.77.112
SBC LAN IP: 192.168.77.124
SBC DMZ IP: 10.10.32.170
SBC Public IP: 104.145.12.182
ITSP FQDN: itsp.sangoma.com
| Info |
|---|
Note: In the following configuration example, this is a DMZ-LAN setup of the SBC, and the FreePBX-PBXact is located on a Private LAN. This is one of many different network topologies that the SBC supports. Not all network topologies will be documented in the document, please consult other Wikis for slight changes in deployment styles of the SBC. Slight changes in configuration from this example to other network topologies are expected. |
...
IP Settings | Network
The default IP Address of the SBC is 192.168.168.2 root/sangoma The IP Address needs to be changed and a new admin user created.
...
At this point you can access the SBC from the New LAN IP Address.
IP Settings | Media Interfaces
Go to Configuration | IP Settings | Media Interfaces
...
Ensure the Transcoding Mode is to Hardware Hidden mode for all Vega SBC and Netborder SBC. Then click Save.
| Info |
|---|
Note: For SMB SBC and Software VM SBC the Transcoding Mode is to Software. The click Save. |
...
Next click Detect Modules. Once you modules are detected click OK to continue.
...
IP Settings | Access Control Lists
Go to Configuration | IP Settings | Access Control Lists
...
Policy: Set to Allow
IP Address: Here you will need a list of any IP Address(es) used by the SIP Trunk Service Provider - Enter the Network Address or IP Address and Mask
...
Signaling | SIP Profile
Two SIP Profiles are needed. One for the LAN side - for 'Internal' communications with the FreePBX-PBXact, and another for the WAN side - for 'External' communication with the SIP Trunk Service Provider.
...
Display Name: Give the SIP Profile a name. ServiceProvider_External
User Agent: This is the name displayed on the User-Agent Header. Does not need changing.
SIP IP Address: Select the LAN IP Address of the SBC
External SIP IP Address: Enter in the WAN IP Address of the Firewall/Router. This setting is only used when the SBC is behind a Firewall/Router.
Port: Port 5060 is default.
Transport: Select the Transport you want to use, UDP+TCP is default. Or individually UDP or TCP.
RTP IP address: If different than the SIP IP Address, select the IP here.
External RTP IP address: Enter in the WAN IP Address of the Firewall/Router. This setting is only used when the SBC is behind a Firewall/Router.
SIP Trace: Optional: Enable. It is useful when you have a problem.
Strict Security: Optional. Enable when strict security is required, here all traffic from non whitelisted and/or registered IP addresses, on that SIP Profile, will be blocked. This means that with this feature enabled you need to assign ACLs or register endpoints in order to be able to make calls through the profile. Enabling in SIP Trunking solutions, allows the SBC to lock down to specific SIP Peers.
Authenticate Calls: Select Disable,
ACL for Inbound Calls: From the Available list, select and use the Arrow key to move over the Internet_WAN_External_ACL list created earlier.
...
Press Save
...
Signaling | SIP Trunks
Two SIP Trunks Profiles are needed. One for the FreePBX-PBXact and another for the SIP Trunk Service Provider. SIP Trunks Profile is where the Peer attributes are configured.
...
Display Name: Give any Name. PBXact
Domain: Enter the IP Address or FQDN of the FreePBX-PBXact
User Name: Not required.
Authentication User Name: Not Required.
Password: Not Required.
From User: Not Required
From Domain: Not Required.
Transparent CallerID: Select Enabled.
Transport: Select UDP
OPTIONS Ping Frequency: Optional: Enter 60 for 60 Seconds
OPTIONS Max Ping: Optional: Enter 5 for 5 tries
OPTIONS Min Ping: Optional: Enter 5 for 5 tries
SIP Profile: Select the "PBXact_Internal" SIP Profile created earlier
...
Press Save
...
Setup the SIP Trunking Service Provider in a SIP Trunk Profile
...
Display Name: Give any Name. ITSP
Domain: Enter the IP Address or FQDN of the SIP Trunking Service Provider. itsp.sangoma.com
User Name: Specific to Service Provider requirements.
Authentication User Name: Specific to Service Provider requirements..
Password: Specific to Service Provider requirements..
From User: Specific to Service Provider requirements.
From Domain: Specific to Service Provider requirements.
Transparent CallerID: Select Enabled.
Transport: Select UDP
OPTIONS Ping Frequency: Optional: Enter 60 for 60 Seconds
OPTIONS Max Ping: Optional: Enter 5 for 5 tries
OPTIONS Min Ping: Optional: Enter 5 for 5 tries
SIP Profile: Select the "ServiceProvider_External" SIP Profile created earlier
...
Press Save
...
Routing | Call Routing
The SBC will require two Call Route Dial Plans. One Dial Plan to send calls from the FreePBX-PBXact to the SIP Trunking Service Provider, and another Dial Plan to send calls from the SIP Trunking Service Provider to the FreePBX-PBXact.
...
Your Call Routing should now look like this for Inbound Calls to the FreePBX-PBXact.
...
Signaling | SIP Profile
Two SIP Profiles were created earlier. We need to go back and assign the appropriate Call Routing Dial Plan to the correct SIP Profile. The Inbound_Calling Dial Plan is assigned to the ServiceProivder_External SIP Profile, as calls from the SIP Trunking Service Provider will will be going Inbound_Calls to bridge to the FreePBX-PBXact. And the other direction, the FreePBX-PBXact will call the PBXact_Internal SIP Profile which will go to the Outbound_Calling Dial Plan, which will bridge the call to the SIP Trunking Service Provider.
...
Under Session Routing change the Routing Plan to Inbound_Calling. Then click Save to continue.
...
Apply Configuration
You are Done. Time to save your efforts.
...
Or Here
...
Finalizing the Installation
Starting the SBC application and other useful features on the SBC.
...