The legacy asterisk.providers table is still created and populated even though SIP provider management uses the PJSIP provider tables. Remove the obsolete table from new installations and existing installations during upgrade.
Steps to reproduce
- On a fresh installation, verify that
asterisk.providers is not created and rest_pjsip_providers is available and populated.
- Create a PJSIP trunk using a provider template and verify it can be saved and applied correctly.
- On an existing installation before upgrade, verify that
asterisk.providers exists.
- Upgrade NethVoice to a version containing the change.
- Verify that
asterisk.providers has been removed while rest_pjsip_providers is still available and populated.
- Verify that existing PJSIP trunks are preserved and continue to work after the upgrade.
Expected behavior
The legacy asterisk.providers table is absent after both fresh installation and upgrade, without affecting PJSIP providers or existing trunks.
Actual behavior
The legacy asterisk.providers table is currently created, populated and refreshed even though it is no longer needed.
The legacy
asterisk.providerstable is still created and populated even though SIP provider management uses the PJSIP provider tables. Remove the obsolete table from new installations and existing installations during upgrade.Steps to reproduce
asterisk.providersis not created andrest_pjsip_providersis available and populated.asterisk.providersexists.asterisk.providershas been removed whilerest_pjsip_providersis still available and populated.Expected behavior
The legacy
asterisk.providerstable is absent after both fresh installation and upgrade, without affecting PJSIP providers or existing trunks.Actual behavior
The legacy
asterisk.providerstable is currently created, populated and refreshed even though it is no longer needed.