Getting Started
SessionPBX is managed as a Teams project in the SessionCloud portal. 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 Projects and select Create Project.
- Under Teams, choose Free Trial.
- Enter an App Name. It must contain 6–12 letters or numbers with no spaces or punctuation.
- Under Phone system, select Use our hosted PBX.
- Select Europe, Americas or Asia as the voice region.
- Select Create.
The app name identifies the project in the administrator portal. Your hosted workspace is created after the project has completed review and approval.
Complete the setup checklist
Open the new project and complete every item shown on its overview page. For a SessionPBX project, pay particular attention to:
- Provisioning — confirm the app and account experience used by team members.
- Miscellaneous — confirm the phone-system choice, region, appearance, language and support details.
When the completion indicator reaches 100%, select Submit for Approval. After approval, activate the trial or subscription when prompted. The portal then makes the SessionPBX administration pages available:
- Team Members
- Call Routing
- Call Flows
- Reports
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.