This uses the new setting category call_recordings name record_name. The record_name is used as a template
Call recording download template.
Options: ${uuid}, ${caller_id_name}, ${caller_id_number}, ${caller_destination}, ${destination_number}, ${destination_number}, ${date}, ${call_direction}, ${year}, ${month_name}, ${month_number}, ${day}, ${time}
* Update system_status.php
Adjust column width to make some overflowing multi-line values into one-line view.
* Enhanced dashboard system_status card with more useful system info
- Added OS version detection
- Fixed not working memory usage with format (60% (1G/2G))
- Replaced memory available with swap usage
- Improved disk usage display format (57% (12G/20G))
- Added DB max connections display (Current/Max)
* Added style colors based on thresholds
* Update app_languages.php
Additional languages for new system_status items
When the directory name set the extension is two characters such as DJ or Yu, the lookup will fail to match the name. This will adjust the script so that the first and last name will match on the number of characters in the directory.
* Add a deleted messages option to voicemail.
Messages are only deleted after a certain amount of time instead of immediately.
The queue can be turned off or on with default setting "use_deletion_queue" in the "voicemail" category.
Changed deleted phrase and add a deleted messages count phrase
Added a program to delete messages that are due for deletion. Also small changes to phrases.
* Added a remove_deleted_messages function that runs on voicemail main menu login. With this method the deletion queue is handled per mailbox vs system wide as in the cron triggered script. It also allows to adjust the retention hours on a per domain basis.
* Fix bug in remove_deleted_messages SQL that caused it too fail.
* Update app_config.php
* Update remove_deleted_messages.lua
* Fix a bug that hangs the call on vm login if there is a deleted message to remove.
This pull request fixes the code for adding extensions and a device is added to the extension.
These device fields are populated if they are defined and enabled in default setttings. This works if the data types = text (the default) and it works if the data types = array (very useful for server clusters)
- Check the outbound_proxy_primary and outbound_proxy_secondary default value for an array value so the drop-down field on the device edit page can be filled.
- Use a variable to get the value from the settings class for server_address_primary and server_address_secondary instead of calling the settings class three times for each value.
