FortiVoice
IP PBX, handsets and contact centre inside the Security Fabric
- Licensing
- By extensions and concurrent calls
- Deployment
- On-premises appliance, virtual machine or cloud
- Capabilities
- PBX, voicemail, auto-attendant, recording, contact centre
FortiVoice is a full IP phone system — PBX, handsets, voicemail, auto-attendant, call recording and contact-centre functionality — built by a security vendor, so voice traffic is visible to the FortiGate as voice and toll fraud and SIP attacks are handled as security events.
Where it fits — and where it stops fitting
Extensions size the system; concurrent calls size the trunk capacity. They are different numbers and we need both. Handsets are a real line item and they need PoE — which is exactly why quoting FortiVoice and FortiSwitch together stops you buying a switch that cannot power the phones.
Highlights
- Toll fraud and SIP attacks surface as security events
- Voice traffic prioritised and inspected by the FortiGate
- On-premises, virtual or cloud deployment
- One vendor for phones, switches and firewall
Typical deployments
- Replacing an ageing PBX with something inside the security perimeter
- Contact centre with queues, routing and recording
- Multi-site voice with centralised administration
What to work out first
FortiVoice is a full IP phone system — PBX, handsets, voicemail, auto-attendant, call recording and contact-centre functionality — that happens to be made by a security vendor, and therefore sits inside the Security Fabric rather than beside it.
The practical consequence is that voice traffic is visible to the FortiGate as voice, gets prioritised properly, and is protected by the same policy set. Toll fraud and SIP attacks are handled as security events instead of surfacing weeks later on a phone bill.
Deployment is on-premises appliance, virtual machine, or cloud, and one vendor relationship covers the phones, the switches that power them and the firewall that protects them.
Questions worth answering before you order
How many extensions and concurrent calls?
Extensions size the system; concurrent calls size the trunk capacity. They are different numbers and both are needed to quote accurately.
Do you need contact-centre features?
Queues, skills-based routing, wallboards and recording move this from a phone system to a contact-centre deployment, which is a materially different scope.
On-premises or cloud?
On-premises for regulatory or latency reasons and where you already have the rack. Cloud where you would rather not run it. Both are the same feature set.
What about the handsets and PoE?
Handsets are a real line item and they need PoE. This is where quoting FortiVoice and FortiSwitch together stops you buying a switch that cannot power the phones.
What this includes
Fortinet publishes no throughput table for this product — it is licensed per user, endpoint, workload or account. What follows is capability and sizing, not benchmarks.
What you are buying
| Licensing | By extensions and concurrent calls |
|---|---|
| Deployment | On-premises appliance, virtual machine or cloud |
| Capabilities | PBX, voicemail, auto-attendant, recording, contact centre |
How this is sized
Fortinet licenses this product per user, endpoint, workload or account rather than by appliance throughput, so there is no comparable performance table to publish. We size it from your actual environment — tell us the numbers and we will work it through with you.
| Licensing | By extensions and concurrent calls |
|---|
Sources
- Fortinet product line overview — retrieved 2026-09-01
Reproduced from Fortinet published documentation and subject to change without notice. Where a figure is load-bearing for your design, ask us to confirm it in writing before you order — we will.