The SMS module is only available through any of our licensing plans.

Once the add-on is installed, refresh your browser and you will find a new section in the PBX navigation menu.

For this module, we have homologated multiple VoIP vendors that provide an SMS service. The first step to using SMS with VitalPBX is to create a connection with one of the homologated vendors with your VitalPBX installation. The number of vendors is constantly growing and we can’t cover all of them in this guide. For detailed articles covering each vendor, you can head over to our blog at our website, https://vitalpbx.com/?s=SMS. Depending on the vendor, the fields you will find under PBX > SMS > Messaging Providers will vary.

When you establish a connection, a Web-hook URL is generated. This can be used with the vendor to receive messages and get information on the status of sent messages.

Under SMS Numbers, you will see the numbers you have acquired with the vendor to send and receive SMS messages. You can add the numbers manually by clicking Add Number.

To add a number enter the number with the appropriate format for your vendor, and a description to identify this number. Some vendors allow you to retrieve the numbers through the API, so you can use the Get Numbers from API button.

When sending an SMS message, you will need to enter the recipient in the To field, and the message in the Message field. The format of the number is validated, so you need to enter the recipient with the correct format supported by the vendor. Usually, you need to use E.164 format.

When you have the numbers available, you can edit or delete them from the Actions column. You also have the ability to send an SMS message from a number on the list. This allows you to test that you can send SMS messages from VitalPBX.

Once you have your connection with your preferred vendor, you can now use SMS messaging with VitalPBX in multiple ways. The first one is the Messaging Notifications feature. Go to PBX >SMS > Messaging Notifications.

This module allows you to create an automatic SMS message as a destination in your VitalPBX. Whenever a caller is calling from a mobile device or from a phone number that supports SMS, an SMS message is automatically sent.

To configure a Messaging Notification, you need to enter a Description to identify the notification. You can then select the phone number from which the SMS is sent.

Then, set the Message you wish to send. You can then establish a Final Destination to send the caller to after the SMS message is sent.

Click Save and then Apply Changes.

Optionally, you can define a static recipient for the SMS message in the To field. This way, when a caller reaches this notification, the SMS message is sent to this phone number. This is useful if you want to send an SMS message to a particular user or service as part of your incoming call chain. You can add a Prefix if this is needed as part of your Dial Plan.

Next, you can see your Messaging Logs. This is like a CDR for SMS messages. Here, you can see the history of all the SMS messages sent and received from your VitalPBX. This allows you to keep track of all messages sent and received.

You can set a date range to filter for specific messages, search by number or message content, and delete message entries.

With the SMS module configured, you can now assign the numbers directly to any extension. Go to PBX > Extensions > Extensions. Here, select any extension and go to the Advanced Tab.

Here, you can set an SMS Number assigned to this extension. This way, any device with this extension registered that supports PJSIP messaging can send and receive messages as a PJSIP message. Whenever you send a PJSIP message to an E.164 number this will be sent as an SMS message. When an SMS message is sent to the number assigned to the extension, it will be converted to a PJSIP message, and forwarded to the registered devices for the extension.

With this set, you can now use SMS with VitalPBX.

To add authentication codes, you will first need to add a Description to identify the codes. Afterward, you can select an Instruction Message you have uploaded to Settings > Voice Prompts > Recordings Management.

Afterward, you must upload a CSV file containing the codes to consider. The format can be downloaded by clicking the Download CSV Format button in the lower left-hand corner. You can edit this CSV file in any number processing application.

Once you have the CSV file with the codes selected, you can define the Destination When the codes Match and when they Don’t. This way, whenever the calling party enters a code that exists in your codes list, they will be taken to a specific destination.

Finally, you can click on Save and then Apply Changes.

The Authentication Codes can be set as a destination at any part of your call flow pipeline. This way, you have a more dynamic way to route your incoming calls.

The CRM Connector add-on is a commercial add-on module available with any of our licensing plans. You will need to have a Licensing Plan subscription to be able to use this commercial add-on. To start using the CRM Connector add-on, you will need to install it through the add-ons module at Admin > Add-Ons > Add-Ons. Once the add-on is installed, refresh your browser. You will now see a new section in the navigation menu to the left called Apps. Go to Apps > CRM >Integrations.

At the moment of writing, only Zoho and Salesforce CRM integration is available. Once again, 0you can go to the following link to find articles with more recent CRM integration guides,
https://vitalpbx.com/?s=CRM. Depending on the CRM you choose to use, the connection instructions may vary, follow the instructions from the guides for your specific CRM to continue.

With the CRM Connector now connected you can now Enable or Disable the connection. You will also have the ability to Enable Call Journaling. With this, calls will start to get logged in your CRM.

Under the Contacts Settings, we define how the calls get logged in your CRM. You can choose whether toSync your Contacts from your CRM Contacts, Leads, or Accounts. And whether or not you wish to enable this feature. This will create a Phonebook with our Phonebooks add-on module that will contain your contacts. This can later be used with our CID Lookup feature to apply the CID Name to incoming calls and be able to identify the callers.

Next, you can select whether you create New Contacts From Inbound or Outboundcalls. This feature can also be Enabled or Disabled. With this, whenever your synced users place or receive a call, a new contact will be created. Finally, you can select whether this new contact is created as a Contact, Lead, or Account. In this case, we will leave the default options on, so new calls are created as contacts.

Lastly, you will have the Users section. Here you will be able to synchronize the different usersthat you have created in your CRM. To synchronize them, click on the green Sync Users button.

With the users synchronized, you will now have a button to Auto Assign Extensions. For this option to work, you must make sure that the extensions have the same email addresses assigned to your CRM users. Click on this button to assign the extensions. Otherwise, you can always edit the user by clicking the blue Edit button next to them.

Here you can assign the Extension number that belongs to the user. Afterward, you can click on Update.

With your users and their extensions assigned, you can start placing or receiving calls. These will now appear in your CRM. For this article, since our contacts are created and synced as Contacts, you will find the activities inside the contacts.

Here, you can see information on the call itself. When it was created, its duration, the user that is involved in this call, as well as the Call Recording. It is important to note that the call recording option is only available with ZOHO CRM at the moment.

For this feature to work, your VitalPBX installation needs to be accessible via the internet with either a Public IP Address or ideally an FQDN. This will allow ZOHO CRM with your permission to point toward the URL of the call recording.

And with this, you now have a full connection between your VitalPBX installation and ZOHO CRM. The process was straightforward, and you can now log your calls with your Contacts, Leads, or Accounts.

This makes the tracking of the activity with your customers easier and more manageable. Resulting in a better management experience and customer relationships.

Microsoft© Teams

The MS Teams Connector add-on is a commercial add-on that is licensed separately from any VitalPBX Licensing Plan. You will need to purchase a separate license to be able to declare more channels with MS Teams extensions. Without any licensing, you can declare 2 MS Teams extensions that can be called through VitalPBX.

Here are some recommendations before we start configuring the connection with Microsoft© Teams.

• In this manual, we are going to create a Trial account to have access to MS Teams with Voice plan.
• We use the latest version available of VitalPBX.
• We must have a valid domain (FQDN) that we have access to configure at a DNS level.
• We must work from Windows since we are going to use PowerShell for some configurations and module installations. Although there are also versions of PowerShell for MacOS.

When using your own SIP Trunk (BYOT) in combination with a VitalPBX to set up Direct Routing to Microsoft© Teams you will need to make some firewall rules.

Note: This applies to Microsoft 365, Office 365, and Office 365 GCC tenants.

When configuring Direct Routing you will need to setup 3 FQDNs for signaling.

• sip.pstnhub.microsoft.com
• sip2.pstnhub.microsoft.com
• sip3.pstnhub.microsoft.com

The first one will be located by location and performance metrics. If your location is EMEA, your 2nd location will be the US and the 3rd ASIA.

These FQDNs resolve to the following IP Address ranges.

• 52.112.0.0/14
• 52.120.0.0/14

In the list below you will find the extracted IP Address Ranges.

• 52.112.0.0/16
• 52.113.0.0/16
• 52.114.0.0/16
• 52.115.0.0/16
• 52.120.0.0/16
• 52.121.0.0/16
• 52.122.0.0/16
• 52.123.0.0/16

When we talk about media ports (not in media Bypass mode 2) the following ranges are used. Media is using a separate service in the Microsoft© cloud, these are called Media Processors.

Locations where both SIP proxy and media processor components are deployed.

• US (two in US West and US East data centers)
• Europe (Amsterdam and Dublin data centers)
• Asia (Singapore and Hong Kong data centers)

Locations where only media processors are deployed (SIP flows via the closest data center listed above).

• Japan (JP East and West data centers)
• Australia (AU East and Southeast data centers)

The following ranges are being used.

• 52.112.0.0/14
• 52.122.0.0/15

This information will help you configure your Firewall to prevent having these IP Addresses blocked. With all these recommendations, we can proceed to configure VitalPBX with MS Teams.

First, we go to the Microsoft© page and create an Office 365 E5 Trial account which already comes with MS Teams and the Phone System plan enabled. As Microsoft© constantly changes the links, we recommend going to microsoft.com and searching for the appropriate location for the Office 365 plans.

Note: If in your country this type of plan is not available yet, and you want to choose the US. You must make sure that you have a cell phone number from the US so you can receive the codes they will send you by SMS.

It is also possible to use the Office 365 E1 Plan or Microsoft 365 Business Basic, but we would have to purchase the Phone System plugin separately.

During the account creation, we select the domain that contains mydomain.onmicrosoft.com. In this example, we will be using vitxi.onmicrosoft.com. Later, we will create a new domain that is the one that will be configured in our VitalPBX Server.

Once the account is created, we must take into consideration the following.

• Microsoft© 365 admin center – This is where we create users, domains, groups, etc.
• https://admin.microsoft.com/
  
  
• Microsoft© Teams administration – This is where we are going to configure the interconnection with VitalPBX.
• https://admin.teams.microsoft.com/
  
  
• Microsoft© Teams – This is where we will be able to make calls, conferences, chat, etc.
• https://teams.microsoft.com/

Now, we must go to the Microsoft© 365 admin center. Enter the username and password you used at the time of registration.

Go to User > Active Users. Here, you can manage the users you have created or create a new one. Here, we verify that our users have the appropriate licensing

Now, go to Settings > Domains on the left-hand side navigation menu. You might have to click on Show All to see the settings option. Here, you will see the domain that was created during the initial configuration of your account creation. We can also create a new domain from here.

Next, we create a domain that matches the domain that we are going to connect our trunk to through Direct Routing of MS Teams. For this, click the + Add Domain button. This must be a domain that we have full control of, as we will be asked to make some changes to our DNS configurations, to prove our ownership of the domain. Once the domain is created, you will see it as follows.

In this example, we are using vitxi.com. Take into consideration that our VitalPBX does not necessarily have to be in the domain itself, but it can be in a sub-domain of it, i.e.msteams.vitxi.com

Note: The domain on the user’s email must match the domain for the VitalPBX installation we are connecting with.

Afterward, we will need to connect to Microsoft© Teams using PowerShell. Run PowerShell as an Administrator.

Then, run the following commands from PowerShell.

PS C:\Windows\system32> Install-Module MicrosoftTeams 
PS C:\Windows\system32> Import-Module MicrosoftTeams 

Next, run the following commands which will prompt for the Office 365 administrator credentials. Enter the user and password you created previously.

PS C:\Windows\system32> $credential = Get-Credential

cmdlet Get-Credential at command pipeline position 1
Supply values for the following parameters:
CredentialPS
C:\Windows\system32> Connect-MicrosoftTeams 
Account Environment Tenant TenantId 
------------------------------------------------------------------------------- 
rcuadra@vitxi.onmicrosoft.com AzureCloud 5c199xxx-c629-4475-8fxx-a3edxxxxa92 5c199xxxc629-4475-8xxa-a3edxxxea92 
PS C:\Windows\system32> Get-Command *onlinePSTNGateway* 
CommandType Name Version Source 
------------------------------------------------------------------------------- 
Function Get-CsOnlinePSTNGateway 5.5.0 MicrosoftTeams 
Function New-CsOnlinePSTNGateway 5.5.0 MicrosoftTeams 
Function Remove-CsOnlinePSTNGateway 5.5.0 MicrosoftTeams 
Function Set-CsOnlinePSTNGateway 5.5.0 MicrosoftTeams

This shows that the connection was successful and the commands are now available. Now, we will proceed to create the Direct Routing. We run the following command on PowerShell to do so. Remember to change the domain to the domain you have created previously.

PS C:\Windows\system32> New-CsOnlinePSTNGateway -Fqdn mydomain.com -SipSignalingPort 5061 -MaxConcurrentSessions 10 -Enabled $true

$trueIdentity                       : mydomain.com
InboundTeamsNumberTranslationRules  : {}
InboundPstnNumberTranslationRules   : {}
OutboundTeamsNumberTranslationRules : {}
OutboundPstnNumberTranslationRules  : {}
Fqdn                                : mydomain.com
SipSignalingPort                    : 5061
FailoverTimeSeconds                 : 10
ForwardCallHistory                  : False
ForwardPai                          : False
SendSipOptions                      : True
MaxConcurrentSessions               : 10
Enabled                             : True
MediaBypass                         : False
GatewaySiteId                       :
GatewaySiteLbrEnabled               : False
GatewayLbrEnabledUserOverride       : False
FailoverResponseCodes               : 408,503,504
PidfLoSupported                     : False
MediaRelayRoutingLocationOverride   :
ProxySbc                            :
BypassMode                          : None

Afterward, we create the Incoming Call Routing. To configure the routing of incoming calls within MS Teams, you must configure in MS Teams which phone number will be associated with it. To do this, execute the following commands on PowerShell. Remember to change the user to the user you created previously.

PS C:\Windows\system32> Set-CsPhoneNumberAssignment -Identity myemail@mydomain.com -EnterpriseVoiceEnabled $true
PS C:\Windows\system32> Set-CsPhoneNumberAssignment -Identity myemail@mydomain.com -PhoneNumber “3000” -PhoneNumberType DirectRouting

With these commands, we have assigned the number 3000 to our user. This would be similar to assigning an extension number. This must be different from the numbering plan on your VitalPBX installation, so we can have easier routing when configuring our VitalPBX.

Now, we must configure the Outgoing Call Routing. For this run the following command on PowerShell. Remember to change the domain to the domain you have added previously.

PS C:\Windows\system32> Set-CsOnlinePstnUsage -Identity Global -Usage @{Add=”Default”}
PS C:\Windows\system32> New-CsOnlineVoiceRoute -Identity “All” -NumberPattern “.*” -OnlinePstnGatewayList mydomain.com -Priority 0 -OnlinePstnUsages “Default”
Identity                : All
Priority                : 0
Description             :
NumberPattern           : .*
OnlinePstnUsages        : {Default}
OnlinePstnGatewayList   : {mydomain.com}
BridgeSourcePhoneNumber :
Name                    : All

Now, we will create an Auto-Attendant so we can later test our calling.

First, we will create a Resource account. Go to the Teams Admin Center, and go to Voice > Resource Accounts. We must create this account with our original domain using the onmicrosoft.com domain. Click on + Add, then add a Display Name to identify the resource, a Username, and set the Resource Account Type to Auto Attendant. Then click on Save.

Once the resource is created it will look like this.

Now we go to the Microsoft© 365 admin center and assign a license that contains Voice. For this, we go to Users > Active users, select the resource account user we just created, and edit it to assign the Office 365 E5 license.

Since we have created the new resource with the voice permissions, we must go to PowerShell and execute the following command, where +3100 is the number that we are going to dial to access the Auto Attendant.

Note: It may take up to 30 minutes for the new resource to recognize the license, so if you get a license error, wait for a moment.

PS C:\Windows\system32> Set-CsOnlineApplicationInstance -Identity “auto@vitxi.onmicrosoft.com” -OnpremPhoneNumber +3100
RunspaceId        : 738753bc-e7e9-4948-9d56-6a29b633920e
ObjectId          : 9142a4f7-cf90-4058-afa2-1e0311dbf825
TenantId          : 5c199f18-c629-4475-8f1a-a3ed1644ea92
UserPrincipalName : auto@mydomain.com
ApplicationId     : ce933385-9390-45d1-9512-c8d228074e07
DisplayName       : auto
PhoneNumber       :

Then, on the MS Teams admin center go to Voice > Auto Attendants, and follow the instructions. Verify that the extension was configured by entering the resource, which should look like this.

Now we are going to create our Auto Attendant, for which we go to the MS Teams admin center, then to Voice > Auto Attendants. Click on the + Add button.

Under the General Info tab, give the auto-attendant a name to identify it. Then, leave the Operator option as is, set the time zone to your time zone, and select the language you are going to use. Click on Next.

Under the Call Flow tab, for the First Play a Greeting Message option, you can type in a greeting message if you don’t have an audio file.

Next, under the Then Route The Call option, we will configure the dialing instructions so the caller can reach the desired destination.

In our example, we have other users with the telephony plugin added to their accounts. If you only have one account, you will only be able to add that account as a menu option. Afterward, there is the option to add a schedule, but we will leave it as is.

With this, we now have an auto-attendant resource in Microsoft© Teams that we can dial
from any MS Teams user.

Now, we must verify the configurations in the Microsoft© Teams admin center. Go to Voice >
Direct Routing, and verify that the trunk towards our VitalPBX has been created. An error might appear at the beginning since we have not configured VitalPBX’s side, but after configuring VitalPBX, we will see the following screen.

Now, we can go ahead and configure VitalPBX for the MS Teams connection.

Before we proceed, remember that your VitalPBX installation must have a valid FQDN pointing to it using the same domain that you added to the Microsoft© admin center. This FQDN domain must have a valid SSL certificate, which can be created under Admin > System Settings > Certificates using Let’s Encrypt or a Custom Certificate. This will not work with self-signed certificates.

The certificate will then need to be assigned to the VitalPBX installation under Admin > System Settings > HTTP Server under the Certificate field, and Force HTTPS must be enabled.

Now, install the Microsoft© Teams Connector add-on under Admin > Add-Ons > Add-Ons. Once the add-on has been installed, refresh your browser and go to Settings > PBX Settings>Microsoft© Teams

Here, you can declare the users and phone numbers we created in Microsoft© Teams. This way, we can call them and receive their calls on VitalPBX. To add the users, you can click the Add button under Allowed Numbers.

You can enter a description to identify the user and the number associated with this user. Remember to add the plus (+) sign at the beginning of the number. Then click on Save. If you have multiple users, you can import a CSV file with all the user data. A template is available under the Download CSV Format button in the lower left-hand corner. Once the file is added to the CSV field, you can click on Import in the lower right-hand corner. With the users created or imported, you can see them listed under Allowed Numbers, and edit or delete them.

The next step will be to configure the PJSIP settings. Go to Settings > Technology Settings > PJSIP Settings. You will now see a new field for MS Teams under NAT Settings, where you must declare the MS Teams Domain.

Additionally, we must set the Certificate we have created previously, set the SSL Method to tlsv1_2, add the External Media and Signal Addresses, and add the Local Net (optional, if available). Click on Save and then Apply Changes.

Now, we must create a new PJSIP Device Profile. Go to Settings > Technology Settings > Device Profiles.

Here, we select PJSIP as the technology. Then, set the Profile to the device profile we just created. Set the Codecs to ulaw, alaw, gsm, and the silk codecs. Under General Configurations, add any name without spaces to the Local Username. This will be used only to identify this trunk. Set the Transport to TLS + MS Teams. This transport is created when installing the MS Teams Connector add-on. For the Contacts enter sip:sip.pstnhub.microsoft.com, this is provided by Microsoft©. Under Match enter sip-all.pstnhub.microsoft.com, this is also provided by Microsoft©. Finally, under From Domain, enter the domain for your VitalPBX installation.

Then click on Save and then Apply Changes.

Next, we must configure our Outbound Routes. For this, go to PBX > Calls Routing > Outbound Routes.

Here, add a Description to identify the outbound route. Enable Intra-Company to use the internal CID information of extensions. Under Dial Patterns, we must Prepend a plus (+) sign to our Pattern since MS Teams only sends and receives calls with E.164 formatting. Since our MS Teams extensions start with a 3, we add the 3XXX pattern, but this may vary based on your configurations. Click on Save and then Apply Changes.

Now, we must configure our Inbound Routes. For this, go to PBX > Calls Routing > Inbound Routes.

For this, we will create an inbound route using a DID Range as the Routing Method. We then add a description to identify this inbound route. Under the DID Pattern we enter +20XX, as MS Teams will send the DID information with a plus (+) sign in front, and our extensions go from 2000 to 2099, in our example. This may vary based on your configurations. Under Range Parameters, we set the Digits to Take to 4, as we are interested in the number dialed without the plus sign. This will essentially, remove the plus sign to find the appropriate extension. We can leave the rest of the options as default. Click on Save and then Apply Changes.

With this, you can now try calling a Microsoft© Teams user from a VitalPBX extension or calling the Auto-Attendant we have configured.

You have now successfully connected Microsoft© Teams with your VitalPBX installation.

With a custom context, you have the freedom to integrate any external service with VitalPBX at a deep level. Custom Contexts will allow you to interface between the Asterisk dial plan, VitalPBX, and any external service or application. You are expected to have Asterisk knowledge to use this feature within VitalPBX. Throughout this lesson, we will be showing one example of using Custom Contexts, but your imagination and Asterisk knowledge are your only limits.

Before using the Custom Contexts add-on, we need to have a context created. In this example, will be creating a service to playback the public IP Address of our server to callers that dial a special code. For this, we will be using the services of ipinfo.io and the CURL application for Asterisk.

Now, log in via SSH to your VitalPBX server, ideally as the root user. Use the following command to go to where the .conf files are located in VitalPBX.

root@debian:~# cd /etc/asterisk/vitalpbx

You will notice that all of the .conf files here have a number. This is used to maintain a sequence order of how the files are read. You can create a new .conf file using the following structure: extensions__{ANYNUMBER}-{DESCRIPTION}.conf, where {ANYNUMBER} is a consecutive number that represents the order that Asterisk will read the files, and the {DESCRIPTION} is any string used to identify what the file contains. So for our example, we will run the following command to create a new .conf file for our custom context using nano.

root@debian:/etc/asterisk/vitalpbx# nano extensions__90-custom.conf

With this, we make sure that our custom context is considered after the extensions’s contexts.

Inside the extensions__90-custom.conf file, we add the following content as our context.

[say-public-ip]
exten => s,1,NoOp(Say Public IP Address)
 same => n,Answer()
 same => n,Set(PUBLIC_IP=${CURL(http://ipinfo.io/ip)})
 same => n,Playback(your-public-ip-is)
 same => n,SayDigits(${CUT(PUBLIC_IP,.,1)})
 same => n,Playback(letters/dot)
 same => n,SayDigits(${CUT(PUBLIC_IP,.,2)})
 same => n,Playback(letters/dot)
 same => n,SayDigits(${CUT(PUBLIC_IP,.,3)})
 same => n,Playback(letters/dot)
 same => n,SayDigits(${CUT(PUBLIC_IP,.,4)})
 same => n,PlayBack(silence/1&vm-goodbye)
 same => n,Hangup()

Then we Save and Exit nano. Then, we reload the Asterisk Dial Plan using the following command.

root@debian:/etc/asterisk/vitalpbx# asterisk -rx "dialplan reload"

Note: When creating the new .conf file, notice that there are 2 underscores(_) after extensions. So it is extensions__90-custom.conf, not extensions_90-custom.conf.

You may notice the your-public-ip-is sound file that does not come with VitalPBX by default. This sound can be downloaded and added to your system using the following command.

root@debian:~# wget -P /var/lib/asterisk/sounds/en/ https://github.com/VitalPBX/custom-contexts/raw/master/sounds/your-public-ip-is.wav

With the context created, you must install the add-on from Admin > Add-Ons > Add-Ons. Once the add-on has been installed, refresh your browser, and go to PBX > Applications >Once the add-on has been installed, refresh your browser, and go to PBX > Applications > Custom Contexts.

Here, you must add a Description to identify this context. Then under Context, enter the name of the context without the square brackets. Optionally, you can specify the Extension and Priority of the context. Under Destination, you can set a destination where you will take the user after they reach the custom context. Click on Save and then Apply Changes.

To test the custom context, we will create a custom application so we can have a code to dial the custom context. Go to PBX > Applications > Custom Applications.

Add a Code to dial, set a Name to identify this custom application, and add the custom context as the destination. Then, Save and then Apply Changes. Now when you dial this code, you will go to your custom context.

The Maintenance add-on is a commercial add-on that requires a license to work to its full potential. You can acquire a license separately just for the Maintenance add-on, or it also comes included with any of our licensing plan subscriptions. To start using the Maintenance add-on, you must install it through the add-ons module under Admin > Add-Ons > Add-Ons. Once the add-on is installed, refresh your browser and go to Admin > Tools > Maintenance. If you installed the Multi-Tenant add-on module, the Maintenance add-on is automatically installed.

Here you can Enable the Maintenance for specific Tenants and the Main System. You can configure the time in days to Delete the Oldest CDR, Recordings, Voicemails, and SMS messages. So all call recordings, voicemails, CDR records, and SMS messages will be deleted if they are equal to or older than the set amount of days. You can set the time in seconds to consider the deletion of short call recordings. So call recordings shorter or equal to the specified time in seconds will be deleted. You can change the Audio Quality and Convert Recordings from WAV to MP3 files.

The maintenance can be run manually by clicking the Execute Now button in the lower left-hand corner, or you can Schedule the maintenance to run automatically using a Cron Profile. Once again, Cron Profiles can be created under PBX > Tools > Cron Profiles.

Once you have the maintenance set as you would like, click on Save and then Apply Changes.

The Branding add-on is a commercial add-on that requires a license to work to its full potential. You can acquire a license separately just for the Branding add-on, or it also comes included with any of our licensing plan subscriptions.

To start using the Branding add-on, you must install it through the add-ons module under Admin > Add-Ons > Add-Ons. Once the add-on is installed, refresh your browser and go to Admin > Tools > Branding.

On the General tab, you can change the Base Color for the whole interface, so lettering, highlights, and accented items will use this color instead of the base green. It is also possible to change the APP Title and Name, so there is no mention of VitalPBX on your application. This is perfect if you are using the Multi-Tenant add-on to provide a PBX on the cloud service to your customers. You can change the Slogan and Social media links that are displayed on the login screen, as well as the Login Footer. You can upload your Logos for Desktop and Mobile view for Light and Dark Mode. The mobile logo is also used for the Favicon. You can quickly disable the branding to revert to the default VitalPBX branding at any time. This is useful to check the differences or if an uploaded logo does not fit on the first try.

There is also a Meet URL option. This option will change the base URL for the video conferencing link under PBX > Extras > Video Conferencing. By default, we offer a courtesy server we host based on Jitsi. You can learn how to set up a Jitsi-based server in this article we made at https://vitalpbx.com/blog/jitsi-videoconference-with-vitalpbx/. With the Meet URL option, you can change the base URL to your meeting server.

Next, we have the GUI tab.

Here, you can change multiple colors found on the VitalPBX Web UI. Giving you more customization options for the Top Navigation Bar and Main Menu on the left-hand side.

Afterward, we have the Login Design tab.

Here, you can change various colors for elements on the Login Screen. As well as the Background Image and Logo used on the Login Screen. You can also disable the background image if you want to use a solid color instead. Finally, if you have a Carrier Plus Licensing Plan Subscription, you get the Branding Plus extended feature. This will add the AddOns tab. In this tab, you can change the Application Name and URL Prefix for the Sonata Suite and VitXi applications. This will also allow Sonata Suite and VitXi to use the same logos you uploaded on the general tab.

Once you are happy with your changes, you can click on Save in the lower right-hand corner. If you are not happy with the styles you have given to your VitalPBX, you can always click on Reset in the lower left-hand corner, reset all the values to their default, and start over.

With the Branding module, you can give your VitalPBX your personal touch and have it align with your company’s brand. Giving your customers a more professional look to the services you provide.

The Virtual Faxes add-on is a commercial add-on that requires a license to work to its full potential. You can acquire a license separately just for the Virtual Faxes add-on, or it also comes included with any of our licensing plan subscriptions.

To start using the Virtual Faxes add-on, you must install it through the add-ons module under Admin > Add-Ons > Add-Ons. Once the add-on is installed, refresh your browser and go to Admin > Add-Ons > Add-Ons. Once the add-on is installed, refresh your browser and go to PBX > Virtual Faxes > Fax Devices.

First, you must create a Fax Device. This is like having a fax machine inside of VitalPBX. This is a device we will use to send and receive faxes. You will need to add a Description to identify the device. Then, add the Associated Email(s), as these will be used when receiving a fax, so it is sent to the email addresses set here. You can enter as many email addresses as you need. You must have the Email Client set up to use the Fax to Email feature. You must set a Caller ID Name and Number, as this is the CID information that will be used when sending a Fax. Finally, set an appropriate Class of Service, so the device can send faxes to their destinations. With the fields configured, you can Save and then Apply Changes.

To Send a Fax from the VitalPBX Web Interface, you must go to PBX > Virtual Faxes > Fax Sending.

Here, you must enter the Recipients to whom you are sending the fax. You can enter multiple phone numbers in this field. Make sure that you enter the number exactly as you would dial it, including any prefixes if needed. Then, select the Fax Device you wish to use. Afterward, you will need to attach the file you wish to send. This must be a TIFF, TXT, or PDF file. You can select the Resolution in which you wish to send it. You can set the number of Max Retries to try and send the fax, as well as the Retry Time between each try. Once you have filled out the fields, click on Send in the bottom right-hand corner.

When you receive a fax, you will have it sent to the email addresses set on the Fax Device, but you can also view faxes from the VitalPBX Web Interface. Go to PBX > Virtual Faxes > Fax Viewer.

Here, you can see the faxes for a specific Fax Device, set the type to All Types, Incoming, or Outgoing, and set a Start and End Date to filter the faxes you wish to see. You can click the Search button in the lower right-hand corner to apply your filters.

Your faxes will be listed on the Faxes List, and you will see information on when they were sent or received, by whom, and the fax content information. Under the Actions column, you can download the Fax Content, and delete any faxes.

With this, you can now send and receive as many faxes as you need directly from your VitalPBX. Allowing you to digitize your faxing abilities.