On Sun, 2008-08-17 at 20:16 -0400, John Buswell wrote: > I have sipx running quite happily bound to a specific IP for its first > instance. I used a fedora core 8 "image" that I chroot'd into, and > installed sipx via the fedora core 8 instructions on the site (via > yum). There are a couple of processes though that are ignoring the > hardcoded IP (in config.def) and I was wondering if anyone knew how to > force them to bind to the specific IP, the processes in question are: > > sipxacd which is bound to 0.0.0.0:8110 > sipxpresence which is bound to 0.0.0.0:8111 > watchdog which is bound to 0.0.0.0:8092
Could you file a bug report on that? The sipX components are supposed to bind only to the IP interface specified in /etc/sipxpbx/config.defs MY_IP_ADDR, which is carried into the components' configuration files. Dale _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
