-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I cannot find anything on how sipX 4.2.1 handles (or doesn't) multiple Public IP's under Server -> NAT.
In a case where you have more than one sipX server front-ended by more than one SBC in a fully meshed network, is there any way to force sipX to ack and properly manage the n Public IP's? By meshed network, I mean: each SBC has a route to each internal sipX server, and the sipX boxes are a core + proxy(ies). Each SBC has an external IP, with external DNS SRV resolving to any SBC. Remote Workers can and will register through any SBC to any sipX. The goal here is geographical distribution and business continuity. - -- ================================================================== Joe Micciche jmicc...@redhat.com Red Hat, Inc. http://www.redhat.com Senior Communications Engineer X (81) 44554 +1.919.754.4554 Key: 65F90FE1 ================================================================== -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAk2/H8QACgkQJHjEUGX5D+GREgCeLBI7hBB+qw3qfzmbQKpBQile JJgAnRrjw+v65PcCqvM1bUzGv+Ib9hIl =DWf7 -----END PGP SIGNATURE----- _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
