NethVoice: Add UI management for LLDP configuration parameter

[andrea-marchionni]

Description

Add a dedicated setting in the NethVoice interface to manage the LLDP parameter for phones that support it (Yealink, Snom, Gigaset for sure, check Fanvil and NethPohone).

The parameter must be handled carefully to avoid changing the behavior of phones that are already configured and in production.

Requirements

• Add a UI option to enable/disable LLDP for phones.
• The default behavior must preserve the current configuration and must not automatically enable LLDP on existing phones.
• The parameter should only be included in the phone configuration when it has been explicitly configured by the administrator.
• Updating NethVoice or the phone provisioning templates must not unexpectedly modify the LLDP configuration of already deployed phones.
• The setting must be applied consistently during provisioning/reprovisioning.
• The behavior should be documented, including the impact on existing phones and newly provisioned phones.

Backward compatibility

Particular attention must be paid to existing installations.

A newly introduced default value must not overwrite an existing phone configuration. The absence of the parameter should therefore be distinguishable from an explicitly configured enabled or disabled value.

Acceptance criteria

• An administrator can manage the LLDP parameter from the NethVoice UI.
• Existing phones are not affected by the introduction of the new setting.
• LLDP is enabled only when explicitly requested.
• Reprovisioning an existing phone applies the configured value consistently.
• Upgrading NethVoice does not unexpectedly change LLDP behavior on existing phones.

[Stell0]

Test case

Use Yealink phones without an explicit LLDP override so the test exercises the default and migration behavior.

Upgrade an existing installation

1. Install a NethVoice version released before this change.
2. Add and provision a Yealink phone.
3. Verify that the generated phone configuration contains static.network.lldp.enable = 0.
4. Upgrade NethVoice to the version containing this change.
5. Reprovision the existing phone and verify that LLDP keeps the old default: the UI shows Disabled and the generated configuration still contains static.network.lldp.enable = 0.
6. Add another Yealink phone without setting an LLDP override.
7. Provision it and verify that it inherits the migrated old default: the UI shows Disabled and the generated configuration contains static.network.lldp.enable = 0.
8. Check LLDP settings is shown on provisioning default and model settings (empty cache and reload after update)

Install a new instance

1. Install the NethVoice version containing this change on a clean system.
2. Open the provisioning defaults and verify that LLDP has the new default, Enabled.
3. Add a Yealink phone without setting an LLDP override.
4. Provision it and verify that it inherits the new default: the UI shows Enabled and the generated configuration contains static.network.lldp.enable = 1.
5. Add and provision a second Yealink phone without an LLDP override.
6. Verify that it also inherits Enabled and its generated configuration contains static.network.lldp.enable = 1.
7. Check LLDP settings is shown on provisioning default and model settings

[Stell0]

🔨 PR testing image: ghcr.io/nethesis/nethvoice:pr-970.793-1.beb48e2