NS7 migration leaves FreePBX modules with incompatible versions

[Stell0]

After migrating NethVoice from NethServer 7 to NethServer 8, FreePBX dependencies are not upgraded consistently. Several modules remain disabled, broken, or unavailable, preventing configuration changes from being applied.

Steps to reproduce

1. Migrate a NethVoice installation from NethServer 7 to NethServer 8.
2. Run fwconsole ma list.
3. Check the installed versions and statuses of the FreePBX modules.
4. Run fwconsole reload or apply the NethVoice configuration.

Expected behavior

All required FreePBX modules are installed and enabled at compatible versions, and the configuration reload completes successfully.

Actual behavior

filestore requires framework version 16.0.40.12, but version 16.0.40.3 is installed. The dependency chain also requires core version 16.0.68.40.

Several modules are left as Disabled; Pending upgrade or Broken. On affected installations, configuration reload can also fail with errors such as:

Unable to locate the FreePBX BMO Class 'Sipsettings'

Unable to locate the FreePBX BMO Class 'Core'

The missing modules must be installed manually with fwconsole ma install -f <module> before configuration can be applied.

See also

• [Support discussion](https://mattermost.nethesis.it/nethesis/pl/t5dmozxf6p8omq4s34dcx9f3fa)
• [ns8-nethvoice repository](https://github.com/nethesis/ns8-nethvoice)

[Stell0]

1. Migrate NS7 with compatible FreePBX module versions

Steps

1. Migrate the prepared NethVoice installation from NS7 to NS8.

2. Wait for the restore and module configuration tasks to complete.

3. Enter the FreePBX container.

4. Run:

   fwconsole ma list

5. Check at least the following modules:

   framework
   core
   filestore
   sipsettings
   backup
   restore
   

Expected result

• framework is installed at version 16.0.40.21 or newer.

• core is installed at version 16.0.68.40 or newer.

• Every required module is enabled.

• No required module is:

  • Broken
  • Disabled
  • Pending upgrade

• No unresolved module dependency is reported.

---

2. FreePBX reload after migration

Steps

1. Complete the migration.

2. Run:

   fwconsole reload

3. Apply a harmless configuration change from the NethVoice UI, such as changing an extension display name.

4. Save and apply the configuration.

Expected result

• fwconsole reload exits successfully.

• Configuration changes are applied.

• The output does not contain errors such as:

  Unable to locate the FreePBX BMO Class 'Sipsettings'
  Unable to locate the FreePBX BMO Class 'Core'
  

• No manual fwconsole ma install -f command is required.

---

3. Existing extensions and devices survive migration

Core changes include endpoint, device, user, and PJSIP generation logic.

Steps

1. Migrate the prepared NS7 installation.

2. Open every migrated extension from the FreePBX or NethVoice interface.

3. Verify:

   • Extension number
   • Display name
   • SIP secret
   • Caller ID
   • Voicemail association
   • Assigned device

4. Run:

   fwconsole reload
   asterisk -rx 'pjsip show endpoints'

5. Register two migrated devices.

6. Place a call between the two extensions.

Expected result

• All extensions and devices are present.
• PJSIP configuration is generated without errors.
• Both devices register.
• The call rings, answers, has bidirectional audio, and terminates normally.

---

4. PJSIP trunk survives migration

Core changes include PJSIP trunk generation and trunk restore handling.

Steps

1. Migrate an installation containing a PJSIP trunk.

2. Verify the migrated trunk parameters:

   • Authentication username
   • Secret
   • SIP server
   • Port
   • Transport
   • From domain
   • Registration mode
   • Codecs

3. Run:

   fwconsole reload
   asterisk -rx 'pjsip show endpoints'
   asterisk -rx 'pjsip show registrations'

4. Place an outbound call through the trunk.

5. Place an inbound call through the trunk.

Expected result

• The trunk is present and enabled.
• Generated PJSIP configuration is valid.
• Registration succeeds when required.
• Inbound and outbound calls complete with bidirectional audio.

---

5. Inbound and outbound routes survive migration

Core changes include routing backup and restore logic.

Steps

1. Before migration, record:

   • Inbound DID and destination
   • Outbound route name
   • Route order
   • Dial patterns
   • Selected trunks and sequence

2. Migrate the installation.

3. Compare the restored route configuration.

4. Place:

   • An inbound call to the configured DID
   • An outbound call matching the configured dial pattern

Expected result

• Inbound and outbound routes are restored.
• Route ordering is preserved.
• Dial patterns are unchanged.
• The correct trunk is selected.
• Calls reach the expected destinations.

---

6. Extension and ring-group call recording

Core changes include dial logic and call-recording handling.

Steps

1. Configure one extension with forced call recording.
2. Add that extension to a ring group.
3. Place a direct call to the extension.
4. Place a call to the ring group and answer from that extension.
5. Hang up both calls.
6. Check the CDR and recording storage.

Expected result

• The direct call is recorded.
• The ring-group call is recorded according to the extension recording policy.
• Each CDR references the correct recording.
• The recordings contain both audio directions.

---

7. FreePBX login and administration pages

Framework changes include login, header, footer, JavaScript, and AJAX handling.

Steps

1. Open the FreePBX administration interface.

2. Log in with valid credentials.

3. Navigate through:

   • Dashboard
   • Extensions
   • Trunks
   • Inbound Routes
   • Outbound Routes
   • Module Administration
   • Advanced Settings

4. Save a harmless change.

5. Log out and log in again.

Expected result

• Login and logout work.
• Pages load without HTTP 500 or JavaScript errors.
• AJAX requests complete successfully.
• Forms can be opened and saved.
• No session, permission, or BMO-class error is displayed.

---

8. Media conversion regression

Framework changes include FFmpeg media handling.

Steps

1. Upload or create a supported system recording.
2. Use it in an announcement or IVR.
3. Apply the configuration.
4. Call the destination and listen to the recording.

Expected result

• Media upload or conversion completes.
• The generated audio file is readable by Asterisk.
• Playback is clear and complete.
• No FFmpeg command or permission error is logged.

---

9. Upgrade an existing NS8 NethVoice instance

Steps

1. Start from an NS8 NethVoice version containing:

   • framework-16.0.40.3
   • core-16.0.68.9

2. Configure extensions, a trunk, inbound and outbound routes.

3. Upgrade NethVoice to the fixed version.

4. Run:

   fwconsole ma list
   fwconsole reload

5. Repeat internal, inbound, and outbound calls.

Expected result

• Upgrade completes without manual intervention.
• framework and core are upgraded.
• Existing configuration is preserved.
• No module is broken, disabled, or pending upgrade.
• All tested call flows continue to work.