Backup restore doesn't set correct transport ports

[Stell0]

Steps to reproduce

• Migrate a NethVoice instance from a cluster to another one
• Make sure that the 2nd cluster has different number of instances installed (for example if you are migrating 3rd nethvoice on cluster 1, on cluster 2 the bug appears if you are installing 1st, 2nd, 4th... but not the third!
• check where asterisk transport is listening

Expected behavior

• transport should listen at the port defined in ASTERISK_SIP_PORT envrionment variable

Actual behavior

• transport listens at old instance port

Components

ns8-nethvoice

[Stell0]

Also test module clone, looking at the code, same issue should be present

[Stell0]

Workaround: in FreePBX interface -> Asterisk sip settings -> chan_pjsip set transport ports to the ones defined in ASTERISK_SIP_PORT and ASTERIS_SIPS_PORT environment variables

[Amygos]

Testing release nethesis/ns8-nethvoice 1.1.2-testing.4

[Amygos]

Feature Title: NethVoice Module Backup and Restore

Test Case 1: Backup and Restore NethVoice Instance and Verify Asterisk Transport Port

• Objective: To verify that the Asterisk transport port is correctly restored after backing up and restoring a NethVoice instance.
• Preconditions:
  • A two-node NethServer 8 cluster with a NethVoice instance installed on one of the nodes.
  • The ASTERISK_SIP_PORT environment variable is set to a specific port number.
• Steps:
  1. Backup the NethVoice instance on the first node of the cluster.
  2. Restore the backup on the second node of the cluster.
  3. Verify that the restore is successful and the NethVoice instance is functional on the second node.
  4. Check the Asterisk transport configuration on both nodes to determine which port it is listening on.
• Expected Results:
  • The Asterisk transport should be listening on the port defined in the ASTERISK_SIP_PORT environment variable on both nodes.
  • The port number should be the same as the original port number used by the source instance on the first node.

Test Case 2: Backup and Restore NethVoice Instance with Different Instance Numbers and Verify Asterisk Transport Port

• Objective: To verify that the Asterisk transport port is correctly restored after backing up and restoring a NethVoice instance with different instance numbers.
• Preconditions:
  • A two-node NethServer 8 cluster with a NethVoice instance installed on one of the nodes.
  • The ASTERISK_SIP_PORT environment variable is set to a specific port number.
  • The restore instance number is different from the source instance number.
• Steps:
  1. Backup the NethVoice instance on the first node of the cluster.
  2. Restore the backup on the second node of the cluster with a different instance number.
  3. Verify that the restore is successful and the NethVoice instance is functional on the second node.
  4. Check the Asterisk transport configuration on both nodes to determine which port it is listening on.
• Expected Results:
  • The Asterisk transport should be listening on the port defined in the ASTERISK_SIP_PORT environment variable on both nodes.
  • The port number should be the same as the original port number used by the source instance on the first node.

Test Case 3: Backup and Restore NethVoice Instance with Same Instance Number and Verify Asterisk Transport Port

• Objective: To verify that the Asterisk transport port is correctly restored after backing up and restoring a NethVoice instance with the same instance number.

• Preconditions:

  • A two-node NethServer 8 cluster with a NethVoice instance installed on one of the nodes.
  • The ASTERISK_SIP_PORT environment variable is set to a specific port number.
  • The restore instance number is the same as the source instance number.

• Steps:

  1. Backup the NethVoice instance on the first node of the cluster.
  2. Restore the backup on the second node of the cluster with the same instance number.
  3. Verify that the restore is successful and the NethVoice instance is functional on the second node.
  4. Check the Asterisk transport configuration on both nodes to determine which port it is listening on.

• Expected Results:

  • The Asterisk transport should be listening on the port defined in the ASTERISK_SIP_PORT environment variable on both nodes.
  • The port number should be the same as the original port number used by the source instance on the first node.

  Here are the same tests, but with the added detail that the clone procedure is performed on a cluster with two nodes:

Feature Title: NethVoice Module Clone

Test Case 1: Clone NethVoice Instance and Verify Asterisk Transport Port

• Objective: To verify that the Asterisk transport port is correctly updated after cloning a NethVoice instance on a two-node cluster.
• Preconditions:
  • A two-node NethServer 8 cluster with a NethVoice instance installed on one of the nodes.
  • The ASTERISK_SIP_PORT environment variable is set to a specific port number.
• Steps:
  1. Clone the NethVoice instance on the second node of the cluster.
  2. Verify that the cloning is successful and the new NethVoice instance is functional on the second node.
  3. Check the Asterisk transport configuration on both nodes to determine which port it is listening on.
• Expected Results:
  • The Asterisk transport should be listening on the port defined in the ASTERISK_SIP_PORT environment variable on both nodes.
  • The port number should be different from the original port number used by the source instance on the first node.

Test Case 2: Clone NethVoice Instance with Different Instance Numbers and Verify Asterisk Transport Port

• Objective: To verify that the Asterisk transport port is correctly updated after cloning a NethVoice instance with different instance numbers on a two-node cluster.
• Preconditions:
  • A two-node NethServer 8 cluster with a NethVoice instance installed on one of the nodes.
  • The ASTERISK_SIP_PORT environment variable is set to a specific port number.
  • The clone instance number is different from the source instance number.
• Steps:
  1. Clone the NethVoice instance on the second node of the cluster with a different instance number.
  2. Verify that the cloning is successful and the new NethVoice instance is functional on the second node.
  3. Check the Asterisk transport configuration on both nodes to determine which port it is listening on.
• Expected Results:
  • The Asterisk transport should be listening on the port defined in the ASTERISK_SIP_PORT environment variable on both nodes.
  • The port number should be different from the original port number used by the source instance on the first node.

Test Case 3: Clone NethVoice Instance with Same Instance Number and Verify Asterisk Transport Port

• Objective: To verify that the Asterisk transport port is correctly updated after cloning a NethVoice instance with the same instance number on a two-node cluster.
• Preconditions:
  • A two-node NethServer 8 cluster with a NethVoice instance installed on one of the nodes.
  • The ASTERISK_SIP_PORT environment variable is set to a specific port number.
  • The clone instance number is the same as the source instance number.
• Steps:
  1. Clone the NethVoice instance on the second node of the cluster with the same instance number.
  2. Verify that the cloning is successful and the new NethVoice instance is functional on the second node.
  3. Check the Asterisk transport configuration on both nodes to determine which port it is listening on.
• Expected Results:
  • The Asterisk transport should be listening on the port defined in the ASTERISK_SIP_PORT environment variable on both nodes.
  • The port number should be different from the original port number used by the source instance on the first node.

[Amygos]

Release nethesis/ns8-nethvoice 1.1.2