In order to integrate with property management systems (PMS) the PBX includes a PMS client that can send CDR to the PMS, and report maid codes and do-not-disturb events. For hotels, the admin can define whether room-to-room calls are allowed and what dial plans clients can use after check in, depending on their check-in type. Guests can program their wake up call through the phone in the room. The PBX supports popular hotel room VoIP phones as well as FXS gateways for simple hotel room phones.
The PBX comes with a CRM integration. The HubSpot integration generates a record for each call and automatically adds a contact if the number was not found in the contact list. The SaleForce integration plugs into the SalesForce web interface and serves as a softphone within SalesForce. As further generic methods, the PBX supports ActionURL and server-side EMCA script for integrating with non-mainstream CRM systems.
Call Data Records
Call data records (CDR) provide important information about what calls were made on the system. They can be written as simple CSV files to the file system, or sent over HTTP and TCP connections to remote servers for storage and further processing. The PBX is even able to send records directly to MongoDB and MySQL (coming soon). Complex records contain information about the call legs and call recordings in JSON or XML format. There are several ecosystem partners that accept Vodia PBX CDR into their CDR processing system for billing and analytical purposes.
Each extension and each domain has their own local address book which can be used to look up incoming numbers, determine whether to admit or reject calls and to place outbound calls using speed dial numbers. The address book is integrated with VoIP phones that support the LDAP protocol. In addition to that, the PBX integrates with Microsoft and Google contacts and automatically downloads the address from there.
The PBX uses a REST API in the web interface for all interaction with the inner settings of the PBX. The API is available for programming tasks on the PBX like creating accounts, retrieving lists or setting redirects. This makes it possible to run the PBX as a functional entity in the network and automate steps like creating domains, settings, rates and whatever would otherwise have to be done manually.
In order to connect the PBX to the public telephone network, the PBX uses one or more SIP trunks. It comes with a list of known providers where the administrator has to enter only the username and the password in order to set the trunk up. One or more dial plans distribute outbound calls on the trunks, making it easy to use different trunks for different routes. Outbound calls can be protected by PIN code and users can be prompted to enter a client matter code for each call. SIP trunks can use TLS and SRTP on the Vodia PBX if the trunk provider supports that.