Correct, synchronization of information is not there.
In the case of ACD you can definitely have it running on a different server but it isn't going to fail over. Mike From: [email protected] [mailto:[email protected]] On Behalf Of Vikas Sharma Sent: Wednesday, December 17, 2008 12:24 AM To: Scott Lawrence Cc: sipxusers Subject: Re: [sipx-users] High Availability -- features supported by slave,if master server fails Thanks Scott i got you point. i have tested them as well. Hunt is fine. and ACD, voicemail, praking not works when master fails as their services are not running if master fails and such services are not available on slave. cdr is fine if master fails. Calls are written in master cdrs when master is up after a failure. Hence no call lost. Thnaks for you support. What if start ACD server, config, parking server on slave as well? Will this work? or syncronization of information is not there in these services. On Tue, Dec 16, 2008 at 8:57 PM, Scott Lawrence <[email protected]> wrote: On Tue, 2008-12-16 at 11:12 +0530, Vikas Sharma wrote: > hi, > > What are the various features supported by the slave server, if master > server fails. > > For example > 1) voicemail will not work if master server fails. > 2) call forwarding (set from interface) feature is working if master > fails > > > i want to know about other features like > call parking > ACD > Hunt group > other features etc. > > Please somebody tell me about list features supported by slave if > master server fails. > or any link specifying about this. The distributed server will do anything that just involves routing the call, and will support any services that are not on the system that's down. I know that doesn't help too much... you have to know which services are where. Any feature that involves media (eg. park, ACD, conference, voicemail, auto-attendant) is implemented as a service process that handles some part of a call. These services can be instantiated on some server (in 4.0 this is easier to configure) and will not work if the service process or the server system fail. The call routing is done by sipXproxy and sipXregistrar; HA is the replication of those two services on multiple systems (normally two, but it can be more). Features like hunt groups are just routing, so they'll continue to work as long as any one system running the routing processes is up. Does that help? -- vikas sharma
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
