Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Organization: SipXecs Forum In-Reply-To: <aanlktimrwx5+i0ydnuqyyvkq18o3j=_tvdxij5yfy...@mail.gmail.com> X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <53807> Message-ID: <d22f.4cc94...@forum.sipfoundry.org>
Hi Michael, Its not a requirement driven by throughput or resiliency... Its a common setup in enterprise environments for servers to be connected to a private network for management and admin (backups, updates, monitoring etc) and then have servers connected to a separate public or private network for applications. Maybe one of the redhat guy's can confirm this? Seems like we should have a config setting in the application to allow the admin to explicitly set the IP address of the box...which in fact we do with the initial setup script, so still not sure why the application would bind to the wrong address... If there is enough interest, maybe I'll give this a try and report back what breaks...! Abdul _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
