FusionPBX
From VoIP.ms Wiki
| [checked revision] | [checked revision] |
(Created page with "This guide explains how to configure a VoIP.ms SIP Gateway in FusionPBX (FreeSWITCH). It also covers the recommended Access Control (ACL) configuration to restrict SIP traffic to...") |
|||
| (6 intermediate revisions not shown) | |||
| Line 1: | Line 1: | ||
| - | + | [[File:FusionPBX.jpg|300px|right|link=https://docs.fusionpbx.com/en/latest/|FusionPBX]] | |
| - | + | ||
| - | This | + | This guide explains how to configure a VoIP.ms SIP Gateway in '''FusionPBX''' ''(FreeSWITCH)''. |
| - | + | It also covers the recommended Access Control (ACL). | |
| + | |||
| + | = Requirements = | ||
Before starting, make sure you have: | Before starting, make sure you have: | ||
| - | An active VoIP.ms account | + | :* An active VoIP.ms account |
| - | + | :* A Sub Account (SIP) created in the VoIP.ms portal | |
| - | A Sub Account (SIP) created in the VoIP.ms portal | + | ::* '''SIP Username''' (ex: ######_SubAccount) |
| - | :* SIP Username (ex: | + | ::* '''SIP Password''' |
| - | :* SIP Password | + | ::* '''Device Type''': ''Asterisk, IP PBX, Gateway or VoIP Switch'' |
| - | + | ::* '''CallerID Number''': ''I use a system capable of passing its own CallerID'' | |
| - | A selected VoIP.ms PoP (ex: montreal | + | ::* A selected VoIP.ms PoP for your DID ''(ex: montreal.voip.ms)'' |
| - | + | = Create or Edit the VoIP.ms Gateway = | |
| - | + | Access your FusionPBX web interface: | |
| - | + | ||
: 1) Go to '''Accounts''' | : 1) Go to '''Accounts''' | ||
: 2) Select '''Gateways''' | : 2) Select '''Gateways''' | ||
| - | :: [[File:FreeSwitch_Account_Gateway.png|500px|none| | + | :: [[File:FreeSwitch_Account_Gateway.png|500px|none|VoIP.ms Gateway configuration screen]] |
Create a new gateway (or edit an existing one) and fill in the fields exactly as shown below. | Create a new gateway (or edit an existing one) and fill in the fields exactly as shown below. | ||
| Line 44: | Line 44: | ||
:* '''Description''': Enter a description for your note | :* '''Description''': Enter a description for your note | ||
: Click '''[Save]''' | : Click '''[Save]''' | ||
| + | :: [[File:FreeSwitch_Gateway_Configuration.png|500px|none]] | ||
| - | : | + | '''Note''': Verify registration status under '''Status''' → '''Gateways / Registrations''' |
| - | + | ||
| - | + | ||
| - | Verify registration status under '''Status''' → '''Gateways / Registrations''' | + | |
| - | + | ||
The gateway should show Registered | The gateway should show Registered | ||
| - | = | + | = Access Control (ACL) = |
| - | + | For better security, it is strongly recommended to restrict SIP access to VoIP.ms IP ranges only. | |
| - | + | Access the Access Control Menu | |
:* Go to '''Advanced''' then '''Access Controls''' | :* Go to '''Advanced''' then '''Access Controls''' | ||
:: [[File:FreeSwitch_access_controls_menu.png|500px|none|Advanced → Access Controls]] | :: [[File:FreeSwitch_access_controls_menu.png|500px|none|Advanced → Access Controls]] | ||
| - | + | Create or Edit the '''"providers"''' and configure the ACL as follows: | |
| - | :* Name: providers | + | :* '''Name''': providers |
| - | :* Default: deny | + | :* '''Default''': deny |
| - | + | ||
| - | Example entry: | + | :* '''Add allow rules for VoIP.ms server IP ranges''' |
| - | :* Type: allow | + | ''Example entry:'' |
| - | :* CIDR: 208.100.60.0/24 | + | :* '''Type''': allow |
| - | :* Description: | + | :* '''CIDR''': 208.100.60.0/24 |
| + | :* '''Description''': ''Eg: "VoIP.ms POP Servers"'' | ||
: Click '''[Save]''' | : Click '''[Save]''' | ||
| Line 76: | Line 73: | ||
== Notes and Troubleshooting == | == Notes and Troubleshooting == | ||
| - | |||
If the gateway does not register: | If the gateway does not register: | ||
* Double-check Username / Password / Proxy (PoP) | * Double-check Username / Password / Proxy (PoP) | ||
Latest revision as of 22:38, 16 December 2025
This guide explains how to configure a VoIP.ms SIP Gateway in FusionPBX (FreeSWITCH).
It also covers the recommended Access Control (ACL).
Contents |
Requirements
Before starting, make sure you have:
- An active VoIP.ms account
- A Sub Account (SIP) created in the VoIP.ms portal
- SIP Username (ex: ######_SubAccount)
- SIP Password
- Device Type: Asterisk, IP PBX, Gateway or VoIP Switch
- CallerID Number: I use a system capable of passing its own CallerID
- A selected VoIP.ms PoP for your DID (ex: montreal.voip.ms)
Create or Edit the VoIP.ms Gateway
Access your FusionPBX web interface:
- 1) Go to Accounts
- 2) Select Gateways
Create a new gateway (or edit an existing one) and fill in the fields exactly as shown below.
Gateway Settings
- Username: Enter your Sub-Account username ######_SubAccount
- Password: Enter your Sub-Account password
- From User: Enter your Sub-Account username ######_SubAccount
- Proxy: Enter the your Preferred PoPServer. Eg: montreal1.voip.ms
- Realm: Enter "voip.ms"
- Expire Seconds: 120
- Register: Select True
- Retry Seconds: 30
- Auth Username: Enter your Sub-Account username ######_SubAccount
- Register Transport: udp (or TCP)
- SIP CID Type: Type "rpid"
- Codec Preferences: This must reflect your Sub-account, ensure you have the proper codec selected. 1
- Ping: 20
- Domain: Select your demain
- Context: Enter your context
- Profile: Select your profile
- Enabled: YES
- Description: Enter a description for your note
- Click [Save]
Note: Verify registration status under Status → Gateways / Registrations The gateway should show Registered
Access Control (ACL)
For better security, it is strongly recommended to restrict SIP access to VoIP.ms IP ranges only.
Access the Access Control Menu
- Go to Advanced then Access Controls
Create or Edit the "providers" and configure the ACL as follows:
- Name: providers
- Default: deny
- Add allow rules for VoIP.ms server IP ranges
Example entry:
- Type: allow
- CIDR: 208.100.60.0/24
- Description: Eg: "VoIP.ms POP Servers"
- Click [Save]
Important:
- VoIP.ms uses different IP ranges depending on the PoP.
- Make sure to add all required CIDR blocks for the PoP(s) you are using.
Notes and Troubleshooting
If the gateway does not register:
- Double-check Username / Password / Proxy (PoP)
- Ensure firewall and NAT allow UDP 5060 and RTP traffic
- Confirm your ACL includes the correct VoIP.ms IP ranges
Inbound and outbound call routing is configured separately using:
- Dialplans
- Inbound Routes
- Outbound Routes
