Welcome, Tenant Admin
This section is for the people who run a VeloPBX tenant day-to-day — provisioning extensions and devices, configuring SIP trunks, building the routing logic that gets calls to the right place, monitoring queues and recordings, and pulling reports for billing or compliance.
If you are an end user looking to manage your own extension, see the End User guide instead.
Who this is for
You are the right reader for this section if you:
- Manage your organization’s VeloPBX deployment
- Add and remove extensions when staff change
- Configure SIP trunks with your carrier
- Build inbound and outbound call routing rules
- Set up IVRs, ring groups, queues, and conference rooms
- Review CDRs, call recordings, and voicemail for the tenant
- Troubleshoot when something is not behaving as expected
You access the admin features through the Web Portal:
https://pbx.fortis-tele.com:8887Where to start
If this is your first time in the Web Portal, work through the pages in order — they build on each other. If you are looking for a specific feature, jump straight to it from the table below.
| # | Section | What it covers |
|---|---|---|
| 1 | Dashboard | The home page — system status, active calls, key counters |
| 2 | Security Policy | Password policy and two-factor authentication for the tenant |
| 3 | Users & Extensions | Create and manage extension accounts; speed dial |
| 4 | IP Phones & Devices | Provision desk phones, softphones, mobile clients; BLF; DECT |
| 5 | SIP Trunks | Connect VeloPBX to your PSTN carrier |
| 6 | Call Routing | The principles that link inbound, outbound, and internal calls |
| 7 | Inbound Rules | Decide what happens to calls coming from outside |
| 8 | Outbound Rules | Decide which trunk and prefix carry each outbound call |
| 9 | Office Hours & Holidays | Time-of-day routing for after-hours and holidays |
| 10 | IVR / Auto-Attendant | The voice menu that greets external callers |
| 11 | Call Park | Park calls into orbits and retrieve them from any phone |
| 12 | Call Pickup | Pick up a colleague’s ringing call from your own phone |
| 13 | Ring Groups | Ring several extensions at once or in sequence; paging |
| 14 | Call Queues | Hold callers in line for a team of agents |
| 15 | Voicemail | Mailboxes, PINs, email notifications |
| 16 | Call Recording | Tenant-level and per-extension recording |
| 17 | CDR / Reports | Browse, filter, export, and webhook call data |
| 18 | Conferencing | Audio-only conference rooms |
| 19 | Meetings | Scheduled audio + video meetings with invitees and recording |
| 20 | Feature Access Codes | Master FAC reference for the whole tenant |
How the pieces fit together
A typical tenant build looks like this:
- Set the security baseline — define the password policy and decide whether to enable 2FA (Section 2) before adding any users.
- Provision people — create extensions for each user (Section 3) and provision their devices (Section 4).
- Connect to the outside world — configure at least one SIP trunk with your carrier (Section 5).
- Define the routing skeleton — read Call Routing (Section 6), then build inbound and outbound rules (Sections 7–8).
- Layer time and behavior — Office Hours & Holidays (Section 9), then IVR menus (Section 10), Call Park / Pickup (Sections 11–12), Ring Groups (Section 13), and Queues (Section 14).
- Add the supporting features — voicemail (Section 15), call recording (Section 16), CDR / reports (Section 17), conferencing (Section 18), and scheduled video meetings (Section 19).
- Reference & quick wins — the Feature Access Codes page is a printable cheat sheet of every dial code your users can call from a phone.
You do not have to do everything in week one. Most tenants start with extensions + a single trunk + one inbound rule + one outbound rule, and add IVRs, queues, and recording once the basics are stable.
Getting help
If something does not behave the way the documentation describes, or you need a feature that is not covered here, contact the VeloPBX support team:
- Email: [email protected]
- Phone: +374 60 443310
When you write in, include your tenant name, the affected extension or trunk name, and the approximate time the issue occurred — that combination is enough for support to look up the relevant CDRs and logs.
Last updated: 2026-05-01