VOS3000 guide

VOS3000 wholesale setup, step by step

The order matters: each step needs the one before it. Follow it once and every new customer and carrier takes minutes.

Updated · By the VOS3000 Web team

Quick answer: A first wholesale route on VOS3000 takes five steps: create a rate group and its rates, create the customer's account with that rate group, add a mapping gateway with the customer's IP, add a routing gateway with the carrier's IP and prefix, then send a test call and check it in the CDR.

Step 1
Rate group and rates
Step 2
Customer account
Step 3
Mapping gateway (customer IP)
Step 4
Routing gateway (carrier IP)

This follows the "First usage, Whole sales" example in the VOS3000 2.1.9.07 manual, with more detail. Every step can be done in the VOS3000 desktop client or in VOS3000 Web.

Before you start

  • The customer's IP (where their calls come from), for example 172.16.1.11.
  • The carrier's IP and port (where you send calls), for example 172.16.1.12, plus any technical prefix the carrier wants.
  • Your selling rates for the customer and the carrier's buying rates.
  • Both IPs allowed on your SIP firewall.

Step 1: rate group and rates

In Rate management, add a rate group for the customer, then add its rates: prefix, area name, rate per minute and billing increments. Add a second rate group with the carrier's rates for your cost. See VOS3000 rates.

Step 2: the customer's account

In Account management, add an account for the customer with the selling rate group, a balance (prepaid) or an overdraft limit (postpaid), and apply. See customers and payments. Add a second account for the carrier, as the vendor (clearing) account, with the buying rate group.

Step 3: the mapping gateway (customer side)

Add a mapping gateway for the customer: its IP, the customer's account, a line limit, and, if the customer sends a technical prefix, a rewrite rule to strip it. See mapping gateway.

Step 4: the routing gateway (carrier side)

Add a routing gateway for the carrier: its IP and port, the prefixes it takes (or leave empty for all), the vendor account, a priority and a line limit. If the carrier wants a technical prefix, add it with a callee rewrite rule such as :125. See routing gateway and routing order.

Step 5: test call and CDR

Ask the customer to send a SIP call, then open Recent CDR. A good call shows the customer's mapping gateway, your routing gateway, the talk time and a charge. Check that the caller and callee numbers are what the carrier expects. See VOS3000 CDR.

If the first call fails

End reasonUsual cause
NoAvailableRouter (-69)No routing gateway prefix matches the number, or the gateway is locked or full.
InsufficientBalance (-2)The customer's account has no balance or overdraft.
CallAuthenticationFailure (-6)The call came from an IP that is not on the mapping gateway.
403, 404, 503The carrier refused the call; see calls failing.

Then add alarms for balance and gateway problems (alarms) and check your margins in the reports.

Questions about this topic

How do I set up VOS3000 for wholesale VoIP?

Create a rate group and rates, an account for the customer, a mapping gateway with the customer's IP, and a routing gateway with the carrier's IP and prefix. Then make a test call and check the CDR.

What is the difference between a mapping and a routing gateway?

A mapping gateway is where calls come in from a customer; a routing gateway is where calls go out to a carrier.

Why does my first test call fail?

Look at the end reason in the CDR. -69 NoAvailableRouter means no routing gateway matched, -2 means the account has no balance, and a SIP code such as 403 came from the carrier.

Try every step in the live demo

Each screen in this guide is in the VOS3000 Web demo, with made-up data. Sign in with demo / demo.