Tancredi: Unify NPX5 provisioning scopes to avoid V1/V2 misconfiguration

[Stell0]

Tancredi currently provides two identical provisioning scopes for NethPhone NPX5 (nethesis-NPX5 and nethesis-NPX5v2) that only differ by firmware template. Users often don’t know whether they have NPX5 HW V1 or V2 and end up applying the V1 scope to V2 hardware (or vice-versa), causing incorrect firmware selection.

Steps to reproduce

1. In Tancredi, provision a NethPhone NPX5 device where the operator cannot reliably identify if the hardware is V1 or V2.
2. Select scope nethesis-NPX5 for a V2 device (common mistake).
3. Generate and serve the provisioning/firmware files.
4. Let the phone fetch the firmware file list and attempt to upgrade.

Expected behavior

• Only one NPX5 scope is available.

• Firmware selection is automatic and correct for both HW V1 and HW V2:

  • serve V2 firmware when requested file is nethesis_np_x5_hwv2_0.txt, or
  • when the phone is coming from a V1 firmware version.

Actual behavior

• Two scopes exist but are indistinguishable to users.
• V2 phones are frequently configured using the V1 scope, leading to wrong firmware template/selection.

See also

• NethVoice: Automatic Firmware Update for NethPhone X5 v2 #7478
• [nethesis/tancredi](https://github.com/nethesis/tancredi)