# VOIP Local Bind Address & Redundancy **URL:** \ **Category:** Ignition\ **Created:** [January 12, 2015, 7:36pm UTC](https://forum.inductiveautomation.com/t/voip-local-bind-address-redundancy/9532 "2015-01-12T19:36:00Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![jmartell](https://avatars.discourse-cdn.com/v4/letter/j/779978/32.png) [@jmartell](https://forum.inductiveautomation.com/u/jmartell)\ **Post date:** [January 12, 2015, 7:36pm UTC](https://forum.inductiveautomation.com/t/voip-local-bind-address-redundancy/9532/1 "2015-01-12T19:36:00Z")
I have a pair of redundant Gateways (version 7.7.0) configured to use VOIP for their alarm notification. This past weekend we had an issue that caused the system to fail over to the secondary gateway. When this happened all of the alarm callouts stopped. There was an error message that pointed me to the Local Bind Address and Public Bind Address settings to check for the problem and that is when I discovered that these settings are replicated between gateways, but they are gateway specific. My understanding is that there is no way for the secondary gateway to bind to the same IP address as the primary. Is there a way to set these that will allow the call fail over to work correctly? How am I supposed to use these settings in a redundant system? ---
**Author:** ![jmartell](https://avatars.discourse-cdn.com/v4/letter/j/779978/32.png) [@jmartell](https://forum.inductiveautomation.com/u/jmartell)\ **Post date:** [January 20, 2015, 11:54pm UTC](https://forum.inductiveautomation.com/t/voip-local-bind-address-redundancy/9532/2 "2015-01-20T23:54:10Z")
I could really use a little insight on these settings. Right now we have a redundant system that is not redundant. Anyone know anything about this or how to work with these settings so redundancy will actually function? ---
**Author:** ![Duffanator](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/duffanator/32/3560_2.png) [@Duffanator](https://forum.inductiveautomation.com/u/Duffanator)\ **Post date:** [January 21, 2015, 9:09pm UTC](https://forum.inductiveautomation.com/t/voip-local-bind-address-redundancy/9532/3 "2015-01-21T21:09:56Z")
I may be wrong, because I usually am, but I thought I remember that the Voice Notification module was one of the modules that only worked on the master gateway. I remember reading that when 7.6 initially came out but I can’t find that document anymore. I don’t remember reading anything in the change logs that changed that. ---
**Author:** ![jmartell](https://avatars.discourse-cdn.com/v4/letter/j/779978/32.png) [@jmartell](https://forum.inductiveautomation.com/u/jmartell)\ **Post date:** [January 21, 2015, 10:32pm UTC](https://forum.inductiveautomation.com/t/voip-local-bind-address-redundancy/9532/4 "2015-01-21T22:32:34Z")
I would love to see some definitive confirmation or denial on this from someone at IA or in some documentation (I couldn’t find anything). As it stands this is an issue. If it is not a redundant module then the module description needs to say so and I need to be able to have independent control over the settings. Also, this raises a lot of questions about how the module functions if I have it installed in two machines that are set up as a redundant pair. ---
**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\ **Post date:** [January 22, 2015, 4:34pm UTC](https://forum.inductiveautomation.com/t/voip-local-bind-address-redundancy/9532/5 "2015-01-22T16:34:56Z")
Hi, The voice module can and should work in a redundant pair, except for the issue with setting the bind address that you’ve noticed. This issue was recognized by another customer a few weeks ago, and we’ve come up with a work around, which I can get to you if you want (otherwise we’ll get it in for 7.7.3, I believe). We are looking at a more comprehensive way for handling this type of issue. We have a few places where bind addresses are specified, and all of these (besides those on the actual redundancy settings page), would suffer from this problem. Regards, ---
**Author:** ![jmartell](https://avatars.discourse-cdn.com/v4/letter/j/779978/32.png) [@jmartell](https://forum.inductiveautomation.com/u/jmartell)\ **Post date:** [February 18, 2015, 6:05pm UTC](https://forum.inductiveautomation.com/t/voip-local-bind-address-redundancy/9532/6 "2015-02-18T18:05:47Z")
Thanks Colby. If you wouldn’t mind sending me the workaround I would appreciate it. ---
**Author:** ![camatt3](https://avatars.discourse-cdn.com/v4/letter/c/22d042/32.png) [@camatt3](https://forum.inductiveautomation.com/u/camatt3)\ **Post date:** [September 5, 2019, 1:05am UTC](https://forum.inductiveautomation.com/t/voip-local-bind-address-redundancy/9532/8 "2019-09-05T01:05:03Z")
What is the current status of this? We are running 7.9.10 and facing the same issue. ---
**Author:** ![jmartell](https://avatars.discourse-cdn.com/v4/letter/j/779978/32.png) [@jmartell](https://forum.inductiveautomation.com/u/jmartell)\ **Post date:** [September 5, 2019, 1:40am UTC](https://forum.inductiveautomation.com/t/voip-local-bind-address-redundancy/9532/9 "2019-09-05T01:40:43Z")
The latest advice I’ve received (as of about 2 months ago) is to setup 2 different notification profiles. On the first you would setup the bind addresses for the primary gateway. On the second profile you would setup the bind addresses for the backup gateway. This results in each gateway having a valid configuration for their local IP address and 1 invalid one. I hope that makes sense. It is a bit of a messy workaround. ---
**Author:** ![camatt3](https://avatars.discourse-cdn.com/v4/letter/c/22d042/32.png) [@camatt3](https://forum.inductiveautomation.com/u/camatt3)\ **Post date:** [September 5, 2019, 1:48am UTC](https://forum.inductiveautomation.com/t/voip-local-bind-address-redundancy/9532/10 "2019-09-05T01:48:07Z")
Thanks, I was wondering if it was going to be something like that. ---
**Author:** ![Eskil\_Holum](https://avatars.discourse-cdn.com/v4/letter/e/cdc98d/32.png) [@Eskil\_Holum](https://forum.inductiveautomation.com/u/Eskil_Holum)\ **Post date:** [January 26, 2024, 1:47pm UTC](https://forum.inductiveautomation.com/t/voip-local-bind-address-redundancy/9532/11 "2024-01-26T13:47:41Z")
I ended up having to do the same now in 2024, i guess it works, but there shuold be a more elegant solution available. ---
**Author:** ![alex.beaty](https://avatars.discourse-cdn.com/v4/letter/a/34f0e0/32.png) [@alex.beaty](https://forum.inductiveautomation.com/u/alex.beaty)\ **Post date:** [March 4, 2025, 7:47pm UTC](https://forum.inductiveautomation.com/t/voip-local-bind-address-redundancy/9532/12 "2025-03-04T19:47:49Z")
Curious if anyone has tried the Backup Local Bind Address field in the Voice Notification Profile Advanced Settings introduced with 8.1.40. I assume that field can be populated with your backup gateway address to avoid the two profile workaround? ---
**Author:** ![Ross\_McCormick](https://avatars.discourse-cdn.com/v4/letter/r/c4cdca/32.png) [@Ross\_McCormick](https://forum.inductiveautomation.com/u/Ross_McCormick)\ **Post date:** [October 17, 2025, 8:44pm UTC](https://forum.inductiveautomation.com/t/voip-local-bind-address-redundancy/9532/13 "2025-10-17T20:44:28Z")
It appears that I am experiencing this same issue with 8.3.0 in 2025. If the Master Gateway Profile binds to the Gateway’s “main” IP address, the backup translates it to the backup IP. However, I have multiple Profiles on the master, each having it’s own IP, not the main IP. These do not translate, and show “Address Already In Use” after the Backup Gateway has been synced.