VoIP.ms PBX
From VoIP.ms Wiki
| [checked revision] | [checked revision] |
| Line 90: | Line 90: | ||
* [[Multi-Tenant_Locations|'''Multi-Tenant Configuration''']] — Set up isolated routing, extensions, and voicemail for separate locations or clients within one account. | * [[Multi-Tenant_Locations|'''Multi-Tenant Configuration''']] — Set up isolated routing, extensions, and voicemail for separate locations or clients within one account. | ||
* [[Reseller_Detailed_Guide|'''Reseller Program''']] — Sub-reseller accounts, per-client billing, and white-label options for MSPs and service providers. | * [[Reseller_Detailed_Guide|'''Reseller Program''']] — Sub-reseller accounts, per-client billing, and white-label options for MSPs and service providers. | ||
| - | * [[ | + | * [[API_Overview|'''VoIP.ms API''']] — Automate provisioning, DID management, and call routing programmatically via the REST API. |
|} | |} | ||
Latest revision as of 14:16, 6 March 2026
|
VoIP.ms PBX
Hosted cloud PBX, built into the VoIP.ms portal. |
|
What is VoIP.ms PBX?
VoIP.ms offers a complete PBX directly in the customer portal at no additional cost. Incoming calls arrive on a DID, pass through your configured routing (eg. an IVR, ring group, queue, time condition, or voicemail) and reach the right device or destination. No server to manage, no software to install. This solution is ideal for:
Prefer to run your own PBX software and use VoIP.ms SIP Trunks only? See PBXs for third-party options including Asterisk, FreePBX, and 3CX. |
Contents |
Call Routing
|
Extensions
|
Voicemail & Messaging
|
Call Management
|
Deployments
|
VoIP.ms supports deployments across multiple sites, offices, or tenants. Each location or client can have its own DIDs, subaccounts, IVRs, voicemail boxes, and call routing.
|
Security
|