Right now label is based on the name this fixes the label. The label part of the array is not saved in the database yet so it can't be used at this time.
Go back to the original device/app_defaults.php. What I had in mind for this was a restore default button. When the administrator decides they want to update it. They may not want or need additional vendors.
Update all the time condition presets that used mweek (week of month) change to mday (day of month).
The week of the month starts according to the calendar even if its partial week on the calendar it counts as week one according to C language and the calendar in the United States. Example Labor day September 2016 1st week was Sept 1-3 2016. The second week is the first Monday.
We've had instances where special characters (other than +) are used in the caller_id_number field which prevents these calls from being detected using the call_block feature. We've resolved this by updating fusionpbx/resources/install/scripts/app/call_block/index.lua line 49 to match only numbers rather than using a gsub replace.
* Update extension.php
* Update user_dashboard.php
User dashboard fills the httpd error log with shell_exec errors. These changes add escapeshellcmd which eliminates these errors and adds 2>&1 to the df command which also generates an error when /home is not mounted
Added the rest of the aastra function key options to app_config. And to
my surprise the functions would not save to the database, found the
problem to be the app_defaults logic would only allow adding on a fresh
install. So I fixed it to work with a update also.
Raw data field was not being pulled so logic was broken, added derived
field raw_data_exists to sql statement, instead of pulling raw data with
query. Also added logic to hide the view extended data icon on the right
side of table.
FusionPBX
minotaur01
Len
Alexey Melnichuk
SJS87
Mafoo
nyfon
Joey