What is our primary use case?
The main use case for Fortinet FortiVoice is that the customer needs to implement IP telephony and secure communication. They need unified security communication solutions. They want call center use cases, hotel management system integration with the hospitality license, in addition to soft client and FortiFone. Fortinet has multiple FortiFone models such as 280, 380, 400, 500, and nowadays, it comes with the 780P models.
Fortinet FortiVoice VoIP integration reduces telephony costs. I am working on the integration with Microsoft Teams, which requires a unified communication license in Fortinet FortiVoice. I have already completed the integration with PMS, a proprietary management system for hospitalities for check-in and check-out, call control, room conditions, and more. This requires an additional license in Fortinet FortiVoice.
What is most valuable?
The key feature of Fortinet FortiVoice is secure communication. Fortinet FortiVoice depends on secure communication as security, and simplicity. It offers a simplicity solution compared to competitors. It is very simple for deployment, configuration, operation, and troubleshooting. Additionally, you don't need a license to add IP telephony on Fortinet FortiVoice. This is a significant advantage against competitors, making the ROI comparatively better.
The centralized call management feature in Fortinet FortiVoice is useful. Fortinet FortiVoice can integrate with the security fabric solution and FortiGate, which can monitor Fortinet FortiVoice. Fortinet FortiVoice has many features out of the box without an additional license.
The call recording and call queuing based on agent skill are among the best features. Fortinet FortiVoice includes the call recording feature at no additional cost, unlike other competitors who charge for this feature.
The multi-location conference calling feature in Fortinet FortiVoice has a cloud solution and can be used with the FortiFone soft client. With Fortinet implementing SD-WAN, it becomes very useful for Fortinet customers to implement a Fortinet FortiVoice solution.
What needs improvement?
Fortinet can improve FortiVoice by adding integration with social media accounts such as WhatsApp and Facebook, and implementing native integration with popular database and CRM systems.
For how long have I used the solution?
I have worked with Fortinet FortiVoice for five to six years.
What do I think about the stability of the solution?
I would rate stability for Fortinet FortiVoice as perfect at 10 out of 10. The stability is very good.
What do I think about the scalability of the solution?
I would rate scalability for Fortinet FortiVoice as eight out of 10.
How are customer service and support?
I would rate Fortinet technical support as nine to 10 out of 10.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
The main competitors for Fortinet FortiVoice are Cisco and Avaya. Cisco, Avaya, and Grandstream are the three main competitors.
How was the initial setup?
The initial setup for Fortinet FortiVoice is extremely simple. It works with auto provisioning, IP phones, and it is the simplest voice solution I have seen.
Which other solutions did I evaluate?
Fortinet FortiVoice is less expensive than Cisco, Avaya, and Mitel. However, it is more expensive than Grandstream, Yealink, Yeastar, and other Chinese vendors. The price point sits in the middle range, rating at five out of 10.
What other advice do I have?
I mainly work with FortiSwitches, FortiAP, Fortinet FortiVoice, Manager, Analyzer, SIM, SOAR, FortiClient, and EDR. I work with all models of FortiSwitches, primarily models 323, 1024, 1048, and for small switches, 124, 148, and F and G series.
I work exclusively with on-premises deployments and have not worked with cloud deployments yet. The on-premises solution is very simple to manage.
Based on my experience, Fortinet FortiVoice is the best VoIP solution I have seen, and I can confidently recommend it to users. I would rate Fortinet FortiVoice 10 out of 10 overall.
Which deployment model are you using for this solution?
On-premises
