On 18 jun 2010, at 15.07, Saint, David (David) wrote: > I would have thought this could be configured as an HA cluster. > Once the two secondary servers (with "SIP Router" role selected) > were added in configuration and registered then the > "Primary SIP Router" role on the first server could be de-selected.
I tried this one out. Now, "Primary SIP Router" cannot be deactivated on the primary server in the GUI. However, by removing the appropriate SRV records in DNS I can make sure that no SIP signaling is sent to the primary server, only load balancing between the two "Redundant SIP Routers". Now my question is, am I missing something here that will break stuff? host1 (configuration only) -- Configuration/Management Primary SIP Router (shutdown) host2 (the "new" primary) -- Voicemail Conference Redundant SIP Router SIP Trunking host3 (redundant call router) -- Redundant SIP Router /Staffan -- Staffan Kerker mail/sip/xmpp: [email protected] "Don't get involved in politics man, just play the gig..." /Sgt Floyd, Electric Mayhem Band _______________________________________________ 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/
