Managing and Updating IP Addresses in EngageIP or SQL Server

Owned by Mahnoor Khan (Deactivated)
Last updated: Sept 24, 2021 by Greg Walsh
1 min read

Summary

This article describes the basic configurable locations where; IP address or hostname are set within EngageIP Billing and where connection information is stored.

Note: Many of the locations as listed below have encrypted connection strings and will need to be updated manually by your LogiSense Customer Care Representative. For any major IP address changes, please contact LogiSense for correct planning recommendations.

Locations Where Connection String Information May Be

The following lists locations where connection string information may be located depending on the breadth of the deployment.

  • EngageIP Billing Folder AdminPortal web.config - Encrypted connection strings

  • Registry: HKEY_LOCAL_MACHINESOFTWAREEngageIPParameters - Encrypted connection strings

  • Telecom Specific Configuration:

    • Registry: (Specific to Telecom deployment) HKEY_LOCAL_MACHINESOFTWAREHawki4Parameters - IP, Username and password information

    • EngageIP Billing Folder AdminPortal Rating VoIP web.config - Encrypted Connection Strings

Once the changes have been completed, restart MSSQL, then IIS, then the EngageIP specific services (EngageIP Billing, EngageIP Event Service). This is required so that they are not using old connection addresses.

 Tips

  • Rather then assigning IPs, use Hostnames so that if the IP changes, the connection string will still function once DNS is configured for the new IP address

  • In clustered environments, check the registry on both SQL servers as well