Ignition 8.1.40 has been removed from our website and will be replaced with 8.1.41 as soon as possible.
8.1.40 included an issue that caused Voice Notification profiles to stop functioning after a Gateway restart. This issue only applies to Gateways not utilizing redundancy. If your redundancy Mode is set to Independent, your Voice Notification profile will be impacted.
Details
While affected, alarm notifications will not be sent via Voice Notification profiles. Impacted systems will display a status of “Address already in use: bind”, as shown below.
In addition, the following message may appear in log files:
Error initializing user agent. Voice notification system will not be available. alarm-notification-profile=XXXXX
java.net.BindException: Address already in use: bind
Patch
Ignition 8.1.41 will be made available once the issue is fixed and tested. This version will be unchanged from 8.1.40 except for the fix. The update is expected to be available early next week.
Workaround
Voice Notification profiles can temporarily be made functional again by setting the redundancy Mode setting to Master and restarting the Gateway.
In cases where the Gateway cannot be restarted, Voice Notification profiles can temporarily be made functional again by editing the profile to change the SIP Port, then saving. This will make the Notification profile functional again, but only until the Gateway is restarted. Note that there may be firewall implications as part of changing the SIP Port.
Recommendations
If you’ve installed 8.1.40 and are affected by this issue, you have a couple of options:
- Revert to a prior version of Ignition and upgrade once 8.1.41 is released in a few days time.
- Remain on 8.1.40 temporarily until 8.1.41 is released and apply one of the two workarounds referenced above.
Comments
0 comments
Please sign in to leave a comment.