CapitalPBX connects the phone system you already own, hardware or software, to our cloud platform in Romania, over SIP trunking or SIP registration, using the external IP-PBX connector. You keep your equipment and your extensions, and calls routed through CapitalPBX pick up the cloud features. It is an option on Virtual PBX plans, not a standalone trunk product.
You connect your existing PBX through SIP registration or SIP trunking, with the external IP-PBX connector, without replacing the equipment you invested in.
You are not replacing the system you invested in. You link it to CapitalPBX, and the numbers, the cloud routing and a record of your calls are added on top.
What stays with you: the PBX, the equipment wired to it and the extensions your team knows by heart. They stay exactly where they are. You are not replacing them and you are not starting over.
What CapitalPBX adds: the numbers, the cloud routing and a record of your calls. Calls that come through us pick up the cloud features, and calls that stay between your own extensions carry on exactly as before.
What we do not do: we do not sell SIP capacity by the channel and we have no standalone trunk product. SIP connection is an option on Virtual PBX plans, for companies bringing their own PBX into our cloud. If you want the whole picture of the platform, not just the connection layer, it is on the VoIP telephony page.
Not sure it fits your setup? Ask a consultant before you change anything in your configuration.
SIP registration or SIP trunking on a static IP. You choose based on what your PBX supports and how it is exposed on your network, not the other way round.
Routing follows the extension range you define when you connect, so calls for your team land where they already landed.
Calls between the two systems are recorded and appear in the CapitalPBX call history, identified by the system they belong to.
Calls that pass through CapitalPBX pick up the cloud features. Your PBX carries on doing what it did, with the cloud layer added on top.
Your PBX and the handsets connected to it keep their role, and the SIP connection happens without replacing them.
The one firm rule is that extensions on the two systems must not overlap, so we set the boundary between them at connection time.
There is no activation fee, and the term follows the plan you choose.
Kommo, amoCRM, Altegio, Pipedrive, HubSpot, Salesforce, Zoho CRM, Zendesk, Bitrix24 and Microsoft Teams as an additional option. Connection is over API, and the same goes for in-house systems, over REST API.
Not just software, but a team with over 20 years in telecom that joins you from setup to optimization.
Between signing the contract and the first call there are a few days, and migration support is included. Not a few minutes, because the contract, the numbers and the testing each take their own time.
In Cloud PBX settings you add it as an external PBX and give it a name, so you can recognise it in the panel.
Either SIP registration, with the connection details you get from the panel, or SIP trunking, if your PBX sits on a fixed IP address.
You state which extensions belong to your system, and routing follows that range.
At the end you check in the panel that the connection status shows as connected.
Four products that work together, in a single platform.
Leave a number and a consultant will call you back. We go through which connection type suits your system, which numbers you need and which plan covers your situation.
Tell us about your team and your call volume, and we'll prepare a custom setup for you.
We activate your numbers, IVR, routing and the integration with your CRM, together with your team.
Coordinated migration, so you don’t miss calls, with local support in Romania.
Guides on cloud telephony, call centres and call automation.
