* Add iphone style toggle for destinations in ring groups
* Add iphone style toggle for destinations in ring groups
* only select enabled destination when make ring group calls
* add destination_enable filed in table v_ring_group_destinations schema
* Change destination_enabled value on to true.
* Update app_config.php
* Change destination_enabled from on to true
* Change destination_enabled to boolean
* Delete fix.css
* Will style this
* Update template.php
Co-authored-by: flagman <flagman@flagman.com>
Co-authored-by: FusionPBX <markjcrane@gmail.com>
Co-authored-by: K-flagman <43560934+kapetrosyan@users.noreply.github.com>
The fs_path setting from config.conf is picked up from the config as a string. The directory.lua code expects the value as boolean so we are converting it to a boolean so it can be used in that way.
This is needed so that if going back to an old time condition see the year it previously had. This provides opportunity to update or remove the old time condition. This provides time to remove the old setting and not confuse it with new years.
The reason for this is the default behaviour for 'return' or 'enter' is to delete the device entirely. This makes using a barcode scanner impossible, or user error resulting in a lot of lost time.
I was having an issue where my T41P phones were getting provisioned with IPv4 & IPv6 - even though I specified in default settings yealink_ip_address_mode=0 for IPv4 only. Checked the y000000000036.cfg, which was setting it correctly. The issue was that {$mac}.cfg was overriding the correct setting. There were several instances of "network.ip_address_mode = 2" in this file, which specifies ipv4&ipv6. I changed all 5 of those entries in this file to pull from the default setting {$yealink_ip_address_mode} rather than just setting a static value of 2. I don't know why it has this listed in this file 5 times. But, this change resolved my issue and will force the T41P provisioning to follow FusionPBX default settings.