Changing the Security Module IP address

Last Updated : Dec 11, 2012 |

About this task

You must have web login access to the System Manager that is managing the Session Manager server.

Procedure

  1. Make the appropriate changes to the DHCP server if needed.
  2. Make the appropriate changes to the 96xxsettings.txt file on the network file server that is used for SIP phone registration settings using the new Security Module address.
    Note:

    The 96xxsettings.txt parameter ENABLE_PPM_SOURCED_SIPPROXYSRVR should be set to 0 to prevent the phone from retaining the previous address downloaded from the Session Manager instance.

  3. Change the state of the Session Manager instance to Deny New Service:
    1. On the System Manager Web Console, under Elements, select Session Manager.
    2. On the Session Manager Dashboard page, select the appropriate Session Manager name from the table.
    3. Click Service State.
    4. From the drop-down menu, select Deny New Service.
    5. On the Confirmation page, click Confirm.
  4. If the server is to be relocated:
    1. Power down the server.
    2. Relocate the server.
    3. Power up the server.
  5. Change the Security Module address of Session Manager:
    1. On System Manager Web Console, select Elements > Routing  > SIP Entities.
    2. Select the appropriate Session Manager and click Edit.
    3. In the FQDN or IP Address field, enter the new IP address for the Security Module. This is not the management IP address.
    4. Click Commit.
  6. Update any associated Security Module information:
    1. On System Manager Web Console, select Elements, select Session Manager > Session Manager Administration
    2. Select the appropriate Session Manager instance and click Edit.
    3. Change any necessary information such as the default gateway and QoS parameters for the Security Module.
    4. Click Commit.
  7. Change the provisioning for all SIP entities with links to the changed Session Manager Security Module address using the entity’s administration.

    For example, if Communication Manager communicates with the Session Manager, the Communication Manager signaling groups need to be updated in order to connect to the Session Manager at its new address.

  8. After all provisioning has been changed, check the status of the Security Module:
    1. On System Manager Web Console, select Elements > System Status > Security Module Status.
    2. Ensure the Status for the Session Manager instance is Up and the IP address is correct.
  9. Test the Session Manager instance:
    1. On the System Manager Web Console, under Elements, select Session Manager > System Tools  > Maintenance Tests.
    2. In the Select Target field, select the Session Manager instance from the drop-down menu.
    3. Click Execute All Tests.
  10. Change the state of the Session Manager to Accept New Service:
    1. On the System Manager Web Console, under Elements, select Session Manager.
    2. On the Session Manager Dashboard page, select the appropriate Session Manager name from the table.
    3. Click Service State.
    4. From the drop-down menu, select Accept New Service.
    5. On the Confirmation page, click Confirm.
  11. Perform a PPM reload to tell the phones where the Session Manager instance has moved:
    1. On System Manager Web Console, select Elements > Session Manager  > System Status  > Registration Summary.
    2. Select the appropriate Session Manager.
    3. Click Reload and select Reload Complete from the drop-down menu to reload the phone with all of its data in order to use the new Session Manager IP address.
    4. Click Confirm.
    5. On the status page, verify that all SIP endpoints have registered.