Hi Mikael, GnuGk indeed listens to individual IPs and not 0.0.0.0. This gives us a more fine grained control over the IP routing, but the downside is that it doesn't automatically listen on IPs that weren't present when GnuGk started. One solution would be to re-scan the IPs when we re-load the config, so you could just do a "kill -HUP" whenever you add new IPs, but thats not implemented, yet. Regards, Jan Mikael Grehn wrote: > Hi! > > We use gnugk in a clustered environment where gnugk is running on both sides (all the time) but only one side have the cluster IP where the incoming/outgoing H323 is going. > If we start gnugk on the running node(with cluste IP) gnugk receives incoming H323 signals without problems. > > But if we switch side, the (already running) gnugk on the new cluster node (where we have set the cluster IP after fail-over) does not get any incoming H323 signals?? > It seems like gnugk does not bind on 0.0.0.0 but only on the IP's that it can find when starting? After restarting gnugk on the running node everything is working again. > > Or have I missed a configuration setting? > > Best Regards, > Mikael -- Jan Willamowius, jan@xxxxxxxxxxxxxx, http://www.gnugk.org/ ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________________ Posting: mailto:Openh323gk-users@xxxxxxxxxxxxxxxxxxxxx Archive: http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk-users Unsubscribe: http://lists.sourceforge.net/lists/listinfo/openh323gk-users Homepage: http://www.gnugk.org/
