> or maybe both at priority 1 and see if the registrations balance. There's > been a lot of talk on how to do this kind of thing on the list lately. > Your two sipx installs perhaps need to be in HA so that if one fails, it > will continue to allow registrations and calls.
This is the part I'm not clear on yet. I thought HA was adding servers to the first one, but they would all be part of the same single install, and NAT IP. Or, is there an HA setup where I could run more than one sipx instance and keep them synchronized so that users could hit either WAN to register/make calls? I very badly need to use multiple WANs to raise the level of availability and reliability. > I think because the initial registration time needs to expire. Even though > it might register upon startup and deregister when shutdown on the PC, the > "state" has a ttl (time to live) involved that has not expired at the > firewall. I don't think it should matter. I was wondering if there might be a setting which I could lower or if it might be best to keep it a bit higher, as it is. I suspect this is a good thing so that idle phones don't think they have lost connection if something goes away for very short periods of time. Mike _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
