# \[BUG-9926\] Ignition Voice Notification Module: Address already in use **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [May 23, 2024, 1:06pm UTC](https://forum.inductiveautomation.com/t/bug-9926-ignition-voice-notification-module-address-already-in-use/90792 "2024-05-23T13:06:01Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![diamond](https://avatars.discourse-cdn.com/v4/letter/d/e79b87/32.png) [@diamond](https://forum.inductiveautomation.com/u/diamond)\ **Post date:** [May 23, 2024, 1:06pm UTC](https://forum.inductiveautomation.com/t/bug-9926-ignition-voice-notification-module-address-already-in-use/90792/1 "2024-05-23T13:06:01Z")
Hello, I have a clean **Ignition 8.1.40** install in a brand new Windows Server virtual machine. In another server, I have an **Ignition 8.1.31** instance under docker. In the docker instance, I can perform VOIP calls with AWS Chime without any issue. However, in the new server, with the **exact same** VOIP Voice Notification Profile, I get the following error: > **Error initializing user agent. Voice notification system will not be available.** > **Address already in use: bind** VOIP registration is performed with no issue at all. Is this an **ignition bug**? I tested changing the RTP Port from 8000 to others, but it makes no difference. This is the extended error message under **CallManager** : ```python java.net.BindException: Address already in use: bind at java.base/sun.nio.ch.Net.bind0(Native Method) at java.base/sun.nio.ch.Net.bind(Unknown Source) at java.base/sun.nio.ch.DatagramChannelImpl.bindInternal(Unknown Source) at java.base/sun.nio.ch.DatagramChannelImpl.bind(Unknown Source) at java.base/sun.nio.ch.DatagramSocketAdaptor.bind(Unknown Source) at java.base/java.net.DatagramSocket.createDelegate(Unknown Source) at java.base/java.net.DatagramSocket.(Unknown Source) at java.base/java.net.DatagramSocket.(Unknown Source) at net.sourceforge.peers.sip.transport.TransportManager.createMessageReceiver(TransportManager.java:349) at net.sourceforge.peers.sip.transport.TransportManager.createServerTransport(TransportManager.java:168) at net.sourceforge.peers.sip.core.useragent.UAS.(UAS.java:72) at net.sourceforge.peers.sip.core.useragent.UserAgent.(UserAgent.java:135) at com.inductiveautomation.alarming.notification.sip.call.CallManager.(CallManager.java:65) at com.inductiveautomation.alarming.notification.sip.profile.SipNotificationProfile.startupInternal(SipNotificationProfile.java:141) at com.inductiveautomation.alarming.notification.sip.profile.SipNotificationProfile.onStartup(SipNotificationProfile.java:165) at com.inductiveautomation.ignition.alarming.notification.AlarmNotificationManagerImpl.loadProfile(AlarmNotificationManagerImpl.java:140) at com.inductiveautomation.ignition.alarming.notification.AlarmNotificationManagerImpl$1.recordUpdated(AlarmNotificationManagerImpl.java:88) at com.inductiveautomation.ignition.alarming.notification.AlarmNotificationManagerImpl$1.recordUpdated(AlarmNotificationManagerImpl.java:84) at com.inductiveautomation.ignition.gateway.localdb.PersistenceInterfaceImpl.notifyRecordUpdated(PersistenceInterfaceImpl.java:177) at com.inductiveautomation.ignition.gateway.redundancy.RedundantPersistenceInterfaceImpl.doNotifyRecordUpdated(RedundantPersistenceInterfaceImpl.java:111) at com.inductiveautomation.ignition.gateway.redundancy.RedundantPersistenceInterfaceImpl$RecordUpdateListener.recordUpdated(RedundantPersistenceInterfaceImpl.java:407) at com.inductiveautomation.ignition.gateway.redundancy.RedundantPersistenceInterfaceImpl$RecordUpdateMessage.notify(RedundantPersistenceInterfaceImpl.java:457) at com.inductiveautomation.ignition.gateway.redundancy.RedundantPersistenceInterfaceImpl$RecordUpdateListener.receiveCall(RedundantPersistenceInterfaceImpl.java:390) at com.inductiveautomation.ignition.gateway.redundancy.QueueableMessageReceiver.receiveCall(QueueableMessageReceiver.java:47) at com.inductiveautomation.ignition.gateway.redundancy.RedundancyManagerImpl.dispatchMessage(RedundancyManagerImpl.java:1042) at com.inductiveautomation.ignition.gateway.redundancy.RedundancyManagerImpl$ExecuteTask.run(RedundancyManagerImpl.java:1110) at com.inductiveautomation.ignition.common.execution.impl.BasicExecutionEngine$ThrowableCatchingRunnable.run(BasicExecutionEngine.java:550) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.base/java.util.concurrent.FutureTask.run(Unknown Source) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) ``` Note that AWS Chime testing was performed first on the new server and then on the old server. Following the official Ignition AWS Chime documentation. Thanks!!!! ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 23, 2024, 1:16pm UTC](https://forum.inductiveautomation.com/t/bug-9926-ignition-voice-notification-module-address-already-in-use/90792/2 "2024-05-23T13:16:48Z")
There's also a SIP port that has to be unique, IIRC. ---
**Author:** ![dmalan](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dmalan/32/10600_2.png) [@dmalan](https://forum.inductiveautomation.com/u/dmalan)\ **Post date:** [May 23, 2024, 2:37pm UTC](https://forum.inductiveautomation.com/t/bug-9926-ignition-voice-notification-module-address-already-in-use/90792/3 "2024-05-23T14:37:24Z")
Out of curiosity, are there any other Voice Notification profiles setup on the "new server"? And if so, are they enabled? ---
**Author:** ![dmalan](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dmalan/32/10600_2.png) [@dmalan](https://forum.inductiveautomation.com/u/dmalan)\ **Post date:** [May 24, 2024, 4:31pm UTC](https://forum.inductiveautomation.com/t/bug-9926-ignition-voice-notification-module-address-already-in-use/90792/4 "2024-05-24T16:31:28Z")
This issue is under investigation, and we are working to resolve it. ---
**Author:** ![diamond](https://avatars.discourse-cdn.com/v4/letter/d/e79b87/32.png) [@diamond](https://forum.inductiveautomation.com/u/diamond)\ **Post date:** [May 24, 2024, 5:05pm UTC](https://forum.inductiveautomation.com/t/bug-9926-ignition-voice-notification-module-address-already-in-use/90792/5 "2024-05-24T17:05:53Z")
Hello, With the hint of @pturmel, we managed to solve it by changing the SIP Port from the default 5060 to 5061. For some reason, this (5060) port seems to be busy in this Ignition version. Answering you question, we do not have any other profile configured. Thanks ---
**Author:** ![ggross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ggross/32/12668_2.png) [@ggross](https://forum.inductiveautomation.com/u/ggross)\ **Post date:** [May 24, 2024, 5:25pm UTC](https://forum.inductiveautomation.com/t/bug-9926-ignition-voice-notification-module-address-already-in-use/90792/6 "2024-05-24T17:25:51Z")
For anyone following along, the issue that is occurring is based on a change made in 8.1.40; `Independent` gateways are attempting to initialize the VOIP connection twice on startup. While what was suggested will work temporarily, it won't work long term and the issue will come back the next time the Gateway is restarted. The only "permanent" work around until we get a fix is to change `Independent` Gateways to be `Master` gateways on the `Config > Redundancy` screen within Ignition. ![Screenshot 2024-05-24 at 10.24.05 AM](https://us1.discourse-cdn.com/inductiveautomation/original/3X/f/1/f12a3651d489438ca094490757255e61c36cb50f.png) This issue has been escalated internally for fix in the next release. We apologize for any issues this is causing. Garth ---
**Author:** ![diamond](https://avatars.discourse-cdn.com/v4/letter/d/e79b87/32.png) [@diamond](https://forum.inductiveautomation.com/u/diamond)\ **Post date:** [May 24, 2024, 5:48pm UTC](https://forum.inductiveautomation.com/t/bug-9926-ignition-voice-notification-module-address-already-in-use/90792/7 "2024-05-24T17:48:46Z")
Very interesting, thank you. It certainly feels good to find a bug, hehe. I think I found another one this afternoon related to another topic, I will report that on Monday. ---
**Author:** ![ggross](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ggross/32/12668_2.png) [@ggross](https://forum.inductiveautomation.com/u/ggross)\ **Post date:** [May 24, 2024, 8:02pm UTC](https://forum.inductiveautomation.com/t/bug-9926-ignition-voice-notification-module-address-already-in-use/90792/8 "2024-05-24T20:02:16Z")
The 8.1.40 release has been pulled because of this issue. See the following thread for more information: [https://forum.inductiveautomation.com/t/8-1-40-pulled-8-1-41-emergency-release](https://forum.inductiveautomation.com/t/8-1-40-pulled-8-1-41-emergency-release)