From VoIP.ms Wiki

[checked revision]

---

Revision as of 20:52, 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) configuration to restrict SIP traffic to VoIP.ms servers only.

This setup follows the same structure and standards used in other VoIP.ms PBX guides.

Contents 1 Requirements 2 Create or Edit the VoIP.ms Gateway 3 Recommended Security: Access Control (ACL) 3.1 Notes and Troubleshooting

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: 123456_SubAccount)
• SIP Password

A selected VoIP.ms PoP (ex: montreal.voip.ms, newyork.voip.ms)

Administrator access to FusionPBX

Create or Edit the VoIP.ms Gateway

From the 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]

Verify registration status under Status → Gateways / Registrations

The gateway should show Registered

Recommended Security: 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: 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