• Switchboard
• Call Accounting System
• Recording Management System
• Call Center Reports (Stats)
• Dialer

https://github.com/VitalPBX/vitalpbx-cr-repo

Then enter the console and execute the following commands:

[root@vitalpbx ~]# yum clean all
[root@vitalpbx ~]# yum install sonata-dialer

Now a wizard will be displayed to guide us to finalize the configuration. 

a.- Database Settings: 

• Database User, MySQL user, if we are on the same server, you can leave the root user without password, otherwise you must create a user in Mariadb to access remotely. 
• Database Password, if we are on the same server the root user usually does not have a password, if we are accessing remotely the user and password must be created in Mariadb.

b.- PBX Settings: 

• Host, if installed on the same server it is advisable to write localhost otherwise, we must write the host or remote IP.  
• Port, if our server has a valid certificate and all requests are redirected to https, we should configure port 443 and we do not have https configure port 80. If we are going to access remotely remember to open these ports in the firewall. 
• App key, If Sonata Dialer is in the same server as VitalPBX it is not necessary to configure the API Key since it is obtained automatically. If Sonata Dialer is installed in a different server than VitalPBX it is necessary to create an App Key in VitalPBX to be able to connect, for which we go to the menu of VitalPBX, ADMIN/Admin/Application Keys, create a new one, copy it and write it here. 
• Secure, indicates a secure https connection, usually port 443 is used when this option is selected. 

c.- User Settings 

• Full Name, full name of the System Administrator. 

• Username, system administrator user, usually admin. 
• Password, password for administrator access. 
• Password Confirmation, password confirmation administrator. 

d.- Log in with the user and password previously created. 

In the menu we have the following options: 

• Dashboard, here we will be able to see the campaigns and active agents, as well as contacts attended, etc. 

• Campaigns, here the campaigns are completely configured, this menu has the following options: 

• Reports, Reports by Agent, Dispositions and Call by Agent. 
  • Agents Report, it is possible to generate reports on the activity of each agent within a campaign. 
  • Dispositions, it is possible to see the overall result of each campaign by layout. 
  • Call By Agent, shows the details of each Agent’s calls. 

• Users, here we create the system users with their respective privileges. 

• Users, create the users and associate them to the Role and Agent Profile, as well as to an extension. 
  • Pause Profiles, we create the pause causes which we are going to relate to the user. 
  • Roles, we create the role that gives us access to each module of the App. 
  • System Permissions, we associate the Agents with queues and campaigns. 

To create a campaign, the following must be considered: 

1. Contact Lists, is the list of contacts to call, a single list can be created and used in multiple campaigns. 

2. Disposition Groups, very important since the groups are created to typify the result of each call. 

3. Form, a form is created where additional data can be associated to the data imported in the Contact List. 

4. Queues, in order to store event history for each agent it is necessary to create queues, and these are associated to the campaign. 

Here is the most logical order to create a campaign from scratch. 

• Text, accepts any type of text. 
• Email, only accepts valid emails. 
• Select, shows multiple selections. They come predefined: 

• Country, list of all countries in the world. 
• US States, list of all U.S. states. 
• Gender, male, female. 
• Months of the year, months of the year. 
• Days of the week, days of the week. 

• Number, accepts only numbers. 
• Checkboxes, accepts only true or false. 
• Radio Buttons, accepts only one selection. 
• Date, accepts only date format. 
• Time, accepts only time format. 
• Textarea, like Text with the difference that it accepts multiple lines. 

All fields are read-only and required, which is optional when creating the field in the form. 

To create a disposition group, go to Campaigns/Disposition Groups.  

The default layout categories are: 

• Negative, can be associated when the call did not give the expected result. 
• Positive, can be associated when the call gave the expected result. 
• Call Later, can be associated when the contact person told us to call you back. 

The following is an example configuration: 

To create lists, go to Campaigns/Contacts Lists. The following formats are supported: 

• CSV 

And the headers must be included in the first line of the form since they will indicate the content of each field. You can add up to 3 telephone numbers in a list.