Grandstream WP810 provisioning requires persistent MAC ranges and custom Tancredi patterns

[Stell0]

Grandstream WP810 phones cannot be provisioned reliably on NethVoice 8 because the required Grandstream MAC prefix is missing from freepbx/rest/lib/macAddressMap.json, and Tancredi does not load custom patterns from /var/lib/tancredi/data/patterns.d.

Steps to reproduce

1. Create a provisioning template for a Grandstream WP810.
2. Add a custom pattern file under /var/lib/tancredi/data/patterns.d.
3. Try to add a WP810 phone with MAC prefix C0-74-AD from the web interface.
4. Generate the provisioning file.

Expected behavior

Grandstream MAC ranges, including C0-74-AD, are recognized by the web interface, and Tancredi loads custom patterns from /var/lib/tancredi/data/patterns.d so they are preserved across updates.

Actual behavior

The web interface does not correctly recognize the Grandstream WP810 unless freepbx/rest/lib/macAddressMap.json is modified manually. Tancredi ignores patterns under /var/lib/tancredi/data/patterns.d; provisioning works only by copying the pattern to /usr/share/tancredi/data/patterns.d/, but both manual changes are lost after updates.

See also

• https://helpdesk.nethesis.it/a/solutions/articles/3000100535
• https://mattermost.nethesis.it/nethesis/pl/jyqodn47b3rktdokp13cn73z5y
• https://helpdesk.nethesis.it/a/tickets/202975

[Stell0]

Test cases for issue #8063: Grandstream WP810 provisioning MAC ranges and custom Tancredi patterns

Scope

Verify that:

1. Grandstream MAC addresses are recognized by the web interface.
2. Default shipped Tancredi patterns.d files still work.
3. Custom Tancredi patterns.d files under the writable data directory work.
4. Custom writable patterns.d files override shipped default files with the same basename.

Preconditions

• NethVoice 8 instance with the fix installed.

• Access to the NethVoice web interface.

• Shell access to the node/container where Tancredi pattern files are stored.

• A test extension available for phone provisioning.

• Grandstream WP810 provisioning template available, or a minimal test template/pattern suitable to generate a provisioning file.

• Paths:

  • Shipped patterns: /usr/share/tancredi/data/patterns.d/
  • Custom writable patterns: /var/lib/tancredi/data/patterns.d/

---

TC1 - Grandstream MAC addresses are recognized by the web interface

Objective

Verify that Grandstream MAC prefixes are mapped to vendor Grandstream and can be selected/handled from the provisioning UI without manually editing freepbx/rest/lib/macAddressMap.json.

Test data

Use Grandstream MAC addresses from the supported ranges, for example:

00-0B-82-12-34-56
C0-74-AD-12-34-56
EC-74-D7-12-34-56
14-4C-FF-12-34-56

Steps

1. Open the NethVoice web interface.
2. Go to the phone/provisioning section.
3. Add a new physical phone.
4. Insert a Grandstream test MAC address, starting with C0-74-AD.
5. Verify that the interface recognizes the vendor as Grandstream.
6. Complete the phone creation using a test extension.
7. Repeat the same check for the other Grandstream MAC prefixes listed above.

Expected result

• The web interface recognizes each tested MAC address as Grandstream.
• The phone can be added without manually modifying freepbx/rest/lib/macAddressMap.json.
• No validation error is shown for the tested Grandstream MAC addresses.

---

TC2 - Default shipped patterns.d files still work

Objective

Verify that the existing shipped Tancredi pattern files under /usr/share/tancredi/data/patterns.d/ are still loaded and used.

Steps

1. Ensure no custom override exists for the pattern being tested:

   podman exec tancredi rm -f /var/lib/tancredi/data/patterns.d/<default-pattern-name>

2. Use a phone model/template that is already supported by a shipped default pattern.

3. Add or update a test phone from the web interface.

4. Generate the provisioning file.

5. Download or inspect the generated provisioning file.

6. Verify that the generated file matches the expected shipped/default pattern behavior.

Expected result

• Tancredi loads the shipped default pattern from /usr/share/tancredi/data/patterns.d/.
• Provisioning generation succeeds.
• Generated provisioning content matches the expected default behavior.
• Existing supported phones are not broken by the change.

---

TC3 - Custom writable patterns.d files work

Objective

Verify that Tancredi loads additional custom pattern files from /var/lib/tancredi/data/patterns.d/.

Steps

1. Create the writable custom patterns directory if missing:

      podman exec tancredi mkdir -p /var/lib/tancredi/data/patterns.d

2. Add a new custom pattern file for the Grandstream WP810 under:

   podman exec -it tancredi vim /var/lib/tancredi/data/patterns.d/...
   

3. Ensure the custom file has a unique basename that does not exist in the shipped patterns directory.

4. Add a Grandstream WP810 phone from the web interface using a recognized Grandstream MAC address, for example:

   C0-74-AD-12-34-56
   

5. Associate the phone with a test extension.

6. Generate the provisioning file.

7. Inspect the generated provisioning output.

Expected result

• Tancredi loads the custom pattern from /var/lib/tancredi/data/patterns.d/.
• The provisioning file is generated successfully.
• The generated file uses the custom WP810 pattern.
• No manual copy to /usr/share/tancredi/data/patterns.d/ is required.

Persistence check

1. Restart the relevant service/container.
2. Regenerate the provisioning file.

Expected persistence result

• The custom pattern remains available.
• Provisioning generation still uses the custom file.
• The custom file is not lost after restart/update.

---

TC4 - Grandstream MAC auto-detection does not break the model selector

Test data

00-0B-82-12-34-56
C0-74-AD-12-34-56
EC-74-D7-12-34-56
14-4C-FF-12-34-56

Steps

1. Open the phone creation form.

2. Enter a Grandstream MAC address, for example:

   C0-74-AD-12-34-56
   

3. Verify the detected vendor.

4. Open the model selector.

5. Select an available Grandstream model.

6. Complete the phone creation using a test extension.

7. Repeat the same check with the other Grandstream MAC addresses listed above.

Expected result

• The interface detects the vendor as Grandstream.
• The model selector is populated with Grandstream models.
• A Grandstream model can be selected.
• The phone can be saved.
• No empty or broken model selector is shown.
• No JavaScript error is shown in the browser console.

---

TC5 - Existing non-Grandstream vendors still populate the model selector

Test data

Use one MAC address for each existing supported vendor, for example:

00-15-65-12-34-56  # Yealink/Dreamwave
00-A8-59-12-34-56  # Fanvil
7C-2F-80-12-34-56  # Gigaset
00-01-42-12-34-56  # Cisco/Linksys

Steps

1. Open the phone creation form.
2. Enter the test MAC address for one vendor.
3. Verify that the vendor is detected correctly.
4. Open the model selector.
5. Verify that models for the detected vendor are available.
6. Repeat for each vendor in the test data.

Expected result

• Existing vendors are still recognized.
• The model selector is populated for each detected vendor.
• The selected vendor/model pair can be saved.
• No regression is introduced for vendors already supported before the Grandstream fix.

[Stell0]

ghcr.io/nethesis/nethvoice:pr-878.269-1.6bed57d