Skip to main content

Connect a VoIP.ms sub-account from the dashboard

You can connect a VoIP.ms number (DID) to MediaSFU from the dashboard, with no code. VoIP.ms sub-accounts sign in by registering, so MediaSFU registers to your VoIP.ms server with the sub-account username and password, and the line's card shows the registration status once it is saved.

▶ Watch this: Connect a VoIP.ms sub-account with registration, 1:56.

At a glance:

  1. In the dashboard, open Phone & SIP Setup, choose Add a number, enter your DID in E.164 format, choose VOIP.ms and a call direction.
  2. On Peer Config, enter your VoIP.ms server (for example toronto1.voip.ms), use port 5060 for UDP or TCP (5061 for TLS), keep Register with Provider on, and enter the sub-account username and password.
  3. Optionally add call features or an AI agent, then choose Create SIP Config. The line's card shows the registration status.
  4. In the VoIP.ms portal, route the DID to the sub-account under DID Numbers → Manage DID Numbers.

Before you start​

  • A VoIP.ms account with a DID number.
  • A SIP sub-account in the VoIP.ms Customer Portal (Sub Accounts → Create Sub Account) that uses User/Password authentication. Set its password there; you enter it in MediaSFU in Step 2.
  • A MediaSFU account that can open Phone & SIP Setup in the dashboard.

Step 1: Add the number (Basics)​

  1. In the dashboard, open Phone & SIP Setup and choose Add a number. The Guided setup opens.
  2. Contact Number: enter your VoIP.ms DID in E.164 format: a plus sign, the country code and the number, with no spaces (for example +14155551234).
  3. SIP Provider: choose VOIP.ms. It is marked as needing registration.
  4. Call Direction: Both receives and places calls. Inbound Only or Outbound Only keeps the line to one direction.

Step 2: Server, registration and credentials (Peer Config)​

  1. SIP Server Host: enter the VoIP.ms server your sub-account uses, for example toronto1.voip.ms (a Canadian server). Pick the one closest to you. Enter the host only, with no port.
  2. Port and Transport: port 5060 for UDP or TCP. Choosing TLS (Secure) switches the port to 5061.
  3. Register with Provider: it is already on for VOIP.ms. Keep it on: sub-accounts must register to receive calls.
  4. SIP Username: the sub-account username, which is your VoIP.ms account number, an underscore, then the sub-account name (for example 100000_office).
  5. SIP Password: the sub-account password you set in the VoIP.ms portal, under Sub Accounts.

With registration on, the SIP Username and SIP Password are both required before you can go on.

Step 3: Finish and create the line​

  1. Features (optional): Auto Record records every call, and SIP Only keeps web participants out of the call. You can also add a Webhook URL to receive call events.
  2. AI Agent (optional): an AI agent can answer the line now or later. See Answer a phone line with an AI agent.
  3. Confirm: check the summary and choose Create SIP Config.

Step 4: Check the registration​

After you save, MediaSFU registers to that VoIP.ms server. The line's card in Phone & SIP Setup shows the registration status, when it last registered, and the last error if registration fails. In the VoIP.ms portal, Sub Accounts → Sub Accounts Registrations shows the same registration from their side.

Step 5: Route the number in VoIP.ms​

In the VoIP.ms portal, open DID Numbers → Manage DID Numbers, edit your number, and route it to this SIP sub-account (the Routing column then shows it, for example [SIP]100000_office). Incoming calls to the DID now reach your MediaSFU line.

If calls do not connect​

  • Registration fails: check the SIP Username format (account number, underscore, sub-account name) and the password, and that the server host matches the one your sub-account uses. The card shows the last error.
  • Registered, but incoming calls do not arrive: check that the DID is routed to this sub-account under Manage DID Numbers.
  • Registration is off: VoIP.ms sub-accounts need it on. Edit the line and turn Register with Provider back on.