SafiServerCE: A for free version that comes with limited features and a concurrent connection limit of 5 ports
SafiServerPro: A licensed version that has additional features (like Email integration and File I/O tools) and is licensed on a per-server/per-port basis
SafiServer is a standalone application server that supports a broad range of telephony applications
and serves as the platform upon which everything from call routing to complex database driven IVRs
can be built. SafiServer is built on enterprise level technology and has been designed from the
ground-up with extensibility, scalability and reliability in mind.
SafiServer can be ran in Windows or Linux and has the flexibility to either be installed on the same
system as your telephone switch (Asterisk or FreeSWITCH) or on a separate machine.
Saflets are call flow applications created and tested using SafiWorkshop and deployed to the SafiServer
for production use. Saflets have a graphical representation much like a flowchart and can be debugged
visually in real-time from the SafiWorkshop.
In the SafiSystems architecture, logical and physical processing power is distributed to maximize scalability,
reliability, and functionality. In a conventional Asterisk PBX environment, the switch server is responsible
for shouldering all the logical, database, and telephony demands related to call flow and IVR functionality.
In a Safi Systems environment, the Asterisk/FreeSWITCH servers become powerful low-level communication "appliances" and all
other functionality is pushed out to the SafiServer. Not only does this design result in improved scalability
but also provides a consolidation point for all IVR and call flow applications for ease of management, enhanced
functionality, and simplified application deployment. These advantages become even more apparent in a multi-Switch
Testing, Debugging and Publishing
Another major advantage of the Safi Systems' development model is the ability to debug live calls. After a Saflet has
been published to a SafiServer; it can be put into a debug mode that allows the developer to view the progress of the
Deploying a Saflet to a SafiServer is as easy as clicking the "Publish" button. Once a Saflet has been published, it
goes into service immediately - the next call that comes in will invoke that Saflet. Current calls are not affected
by the deployment, no server restart is required, and there are no configuration files to reload. Modern business is
dynamic and SafiServer has been built to facilitate that.
SafiServer's feature-set can be given a boost through the addition of "ActionPaks". ActionPaks include features such
as database connectivity, email integration, file i/o features, scheduling, web services, and many more.