Getting Started
SessionPBX is managed as a Teams project in the SessionCloud portal. All Teams plans use the hosted PBX. There is no PBX server, operating system or firewall appliance for you to install.
Before you start
Have the following information ready:
- A short name for the project
- The voice region closest to your users
- The extension-number range you plan to use, such as
1000–1099 - The names and email addresses of your team members
- SIP carrier details if you need public phone numbers
- A simple description of where calls should go during and outside business hours
Create the project
- Sign in to the SessionCloud portal .
- Open Create Project and choose the Teams plan for a hosted SessionPBX workspace.
- On Name, enter a Project name containing 6–12 letters or numbers, with no spaces or punctuation. Select Next.
- On Region, select Europe, Americas or Asia, choosing the region closest to your team. Select Next.
- On Workspace, review the Workspace address and Provider name. The provider name appears in the apps and invitations.
- Select Create project & start trial.
The portal creates the project, starts its trial and requests the hosted workspace. Hosted Teams projects do not require the manual configuration checklist or approval submission used by other project types.
Check the workspace is ready
Open the project and wait for workspace provisioning to finish. If the project was created but the trial could not start, use Start free trial on the project to retry.
Review the initial team member and invitation before adding more members. Once the workspace is ready, the portal provides the administration pages included in the plan:
- Team Members
- Call Routing
- Call Flows — Teams Business
- Reports — Teams Business
Upgrade for advanced call handling
If the project is on the standard Teams tier, Team Members or Call Routing displays an Upgrade to Teams Business option. Review the prorated estimate before confirming the change.
Teams Business adds ring groups, queues, call flows, reports and logo branding. Existing team members and carrier configuration remain in the same project.
Plan your extension numbers
Use a consistent extension range before adding members. A simple plan is easier for people to remember and leaves space for system destinations.
| Purpose | Example range |
|---|---|
| Team members | 1000–1099 |
| Ring groups | 6000–6099 |
| Queues | 7000–7099 |
| Call flows | 8000–8099 |
These are examples, not reserved ranges. Every member, ring group, queue and call flow must have a unique number within the workspace.
Launch checklist
Before giving customers a new phone number, verify all of the following:
- Two extensions can call each other in both directions.
- Each user’s mobile or desktop app receives an incoming call.
- Outbound calls use the expected caller ID.
- Every inbound number reaches the correct destination.
- Ring-group and queue overflow routes work.
- Both branches of each business-hours rule work.
- Voicemail can be left, played and downloaded.
- Recorded-call access matches your organisation’s policy.
Continue with creating extensions.