How the connection works
3CX is a software PBX widely used by businesses, installed in the office or on a cloud server. To call out and receive calls on your numbers it needs a SIP trunk, that is, a link to a carrier. With Vohippo the trunk is an ordinary SIP account: 3CX registers with our server, your extensions' calls go out through it and your numbers ring on the PBX. The page on the Vohippo SIP trunk sums up what the service offers.
The division of labour is clear: Vohippo provides lines, numbers and caller ID, while 3CX handles extensions, groups, menus, queues and opening hours. Everything that happens inside the office stays in the PBX; we take care of what comes in and goes out.
Before you start you need administrator access to 3CX, an account on the Vohippo portal (if you do not have one, sign up to the portal) and at least one number to use as caller ID.
1. Create the SIP account in the portal
In the Vohippo portal, under SIP accounts, create one account for the trunk: that is where you get the username and password.
- Give the account the simultaneous channels you need
- If the PBX has a fixed IP address, you can choose IP address authentication instead of a password
- Enable only the countries you call and set a daily spending cap
Channels
Channels are set with «Simultaneous outbound calls», from 1 to 1000; each channel beyond the first costs €0.50 a month, pro-rated by day. The limit only applies to outbound calls. For an agency with eight desks that rarely all phone at once, four or five channels are usually a good starting point: increase them when the reports show calls rejected with «Maximum channels reached».
Authentication
There are three options: «Username and password», «IP address» and «Username/password and IP». With «Username and password» 3CX can register from any network, and it is the right choice if the office has no fixed IP. With «IP address» the platform recognises the PBX by its public address (up to 20 IPv4 addresses or networks); with «Username/password and IP» both are required, and it is the safest option if the IP is fixed.
Spending limits
Set the «Daily spending limit» straight away (it resets at midnight, Rome time), the enabled destinations («Only the selected destinations» if you only call your own country and a few others) and, if you like, «Block calls costing more than (per minute)». These are the defences that really count if the PBX were compromised, as the VoIP security guide explains.
2. Add the trunk in 3CX
In the SIP trunks section of the 3CX admin console, add a new trunk and choose the generic template (generic SIP provider). Then fill in:
- Registrar / server: sip.vohippo.com — port 5060, UDP transport
- Outbound proxy: leave it empty, or use the same server
- Authentication ID: the SIP account username
- Authentication password: the password of the same account
- Main trunk number: the virtual number you have on Vohippo
The authentication type to choose is the registration and account based one: 3CX registers with username and password and so tells us where it is. If instead you chose «IP address» in the portal, pick the option without registration (IP-based authentication) in 3CX and leave the credentials empty.
Copy the username and password without spaces before or after: it is the most common cause of rejected registrations. Set the trunk's number of channels in 3CX equal to the account's «Simultaneous outbound calls», so the two limits match.
The trunk at a glance
A few details, always the same: sip.vohippo.com, port 5060 and the account credentials.
- Registrar sip.vohippo.com, port 5060 UDP
- SIP account username and password
- Codecs G.711 a-law, µ-law and G.722
3. Caller ID and outbound rules
The number you show to the people you call must be verified in the portal. In 3CX's outbound rules you choose which calls go through this trunk.
- Outbound caller ID: your verified number, in international format
- If the account has a fixed caller ID in the portal, it overrides whatever 3CX sends
- Outbound rule: all calls, or only certain prefixes, to the Vohippo trunk
How the platform reads the number
On the platform every outbound call must carry a verified caller ID: if it does not, it is rejected and the call reports show «Caller ID not allowed». There is no anonymous outbound calling. If the account has no fixed caller ID but the option «Taken from the call (must be one of your caller IDs)», the number is read from the call in this order: P-Asserted-Identity, Remote-Party-ID, From.
With password authentication the account is recognised from its credentials, so the number in the From is enough. With IP authentication it is better for 3CX to put the number in P-Asserted-Identity: in the trunk's advanced options, among the outbound SIP parameters, you can choose what to write in each header. The safest format is the one with +, for example +39 06 1234 5678, or 0039, or the national format.
With the caller ID taken from the call you can give different departments different numbers: support calls out with one number, accounts with another, as long as they are all verified. Numbers bought on Vohippo are already caller IDs; those from other carriers are verified in the portal and cost €0.02 per answered call. The guide on caller ID covers every case.
Outbound rules
In the outbound rule, numbers should be sent as they are dialled on an ordinary phone: national format for domestic numbers, with 00 or + for other countries. A number without an international prefix is read as belonging to the country of the mobile number you verified. If the office never calls abroad, create a rule for domestic numbers only and enable only your country on the account: two barriers are better than one.
4. Inbound numbers
In the trunk configuration, in the numbers (DID) section, add the virtual numbers you have on Vohippo and decide where they go: an extension, a group or an IVR.
- In the Vohippo portal the number must ring the trunk's SIP account
- If you are not sure of the format of the incoming number, look it up in the 3CX logs on the first call
In the portal, the number's routing must include the «Ring SIP accounts» step pointing to the trunk account; a number without a flow ends up as «Calls rejected». How to build the steps is explained in the guide on how to set up an inbound number. Groups, IVR, queues and office hours are then set up in 3CX, in the inbound rules: they are PBX features, not platform features.
If you need more numbers, you can find them among the virtual numbers in 232 Italian cities and over 90 countries: an Italian geographic number costs €23.48 a month, inbound calls included.
5. Codecs and testing
Keep the G.711 a-law and µ-law codecs at the top, then G.722. Save: the trunk must show as registered.
- Trunk status registered in the 3CX console
- Outbound test call to a mobile
- Inbound test call to your virtual number
Why only these codecs
The platform accepts G.711 a-law (PCMA), G.711 µ-law (PCMU) and G.722. Remove G.729, Opus and the others from the trunk's list: they are not negotiated, and leaving them at the top can make the call fail. A G.711 call uses about 100 kbit/s per direction: five simultaneous calls need roughly 500 kbit/s of free upload. Keypad tones travel as RFC 4733. You will find the details in the VoIP codecs guide.
The tests to run
After the outbound and inbound calls, test the tones too (call a service with a menu and press a few keys) and check the call reports in the portal: every test must appear with its outcome. In the portal you also have the account's SIP log for the last 7 days, useful for seeing registrations and rejections on our side.
NAT, firewall and ports
If 3CX sits behind a router, it must know its public IP address: you set it in the 3CX network settings, which also include a firewall check to verify that the ports can be reached. Without the right public address, the typical result is one-way audio.
- Turn off SIP ALG on the router: it rewrites SIP messages and breaks them.
- Allow port 5060 UDP to and from
sip.vohippo.com. - Let the audio through: our RTP ports range from 10000 to 20000 UDP, and 3CX's are shown in its settings.
Our server also handles NAT on its side and sends keepalive packets on the audio every 30 seconds. How it works and which ports to open is covered in the guide on NAT, firewalls and ports.
If something goes wrong
The most common problems, in order of frequency.
- 403 or failed registration: wrong username or password, or IP authentication set up for a different address
- Call rejected: caller ID not verified, or destination not enabled on the account
- One-way audio: NAT; check the public IP address in 3CX and turn off SIP ALG on the router
Other cases that are less frequent but worth knowing:
| Symptom | Likely cause | What to do |
|---|---|---|
| The trunk registers and then stops | The platform firewall blocked the IP after too many errors | Fix the password, then unblock from «IP address security» |
| Busy on outbound calls | «Simultaneous outbound calls» reached | Increase the channels on the account |
| Call rejected although there is credit | «Daily spending limit reached» or rate above the limit | Read the reason in the call reports |
| Inbound calls do not arrive | Trunk not registered or number without routing | Check the status and the «Ring SIP accounts» step |
The platform firewall blocks an address after 5 authentication errors in 10 minutes, with longer and longer blocks: when you change the password in the portal, update it in 3CX straight away.
Frequently asked questions
Do I need a specific provider template for Vohippo?
No: the generic SIP trunk template is enough, with the details in this guide. There are only a few fields: server, port, credentials, main number and codecs.
Can I use IP authentication instead of a password?
Yes, if 3CX has a fixed public IP address: set it on the account in the portal by choosing «IP address» or «Username/password and IP». With IP authentication it is better to send the caller ID in P-Asserted-Identity.
How many channels does the trunk have?
As many as you set on the SIP account in the portal with «Simultaneous outbound calls», from 1 to 1000; you can add more when you need them. The limit only covers outbound calls.
Can 3CX do IVR, queues and office hours with the Vohippo trunk?
Yes: they are 3CX features and apply to the calls arriving from the trunk. Vohippo provides the lines and numbers; menus, queues and time conditions are configured in the PBX.
Why are calls rejected if the trunk is registered?
Registration only confirms the credentials. A rejection usually comes down to an unverified caller ID, destinations that are not enabled, credit or the spending limit: the reason is written in the call reports.