Not a valid setup at all. Centralized CallManagers can't fall over to a remote CallManager. In fact, a remote CM can't even be clustered over the WAN (unless it's faster than 10MB link). For remote site fail over, you need SRST off of a router to PSTN. It's a temp solution until you get the WAN link or CallManager back up.
For PSTN fallback in CallManager you need to create 2 route lists in CM. First choice would be WAN. 2nd choice would be PSTN. Add both to a route group. wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Dear All, > > Need some advice on the redundancy features of CallManager. One of my > customers is asking about the redundancy features of CM - he is thinking of > putting 2 CM servers at a main site providing local server redundancy, > however, there will be a third CM server at a remote site which provide > site redundancy. In case the main site fails, he wants the remote CM to > take over the CM function of the main site without downtime. Please note > that there are about 400 phone users at the main site and about 50 phone > users at the remote site. Please advise how it can be done. > > Also this customer intend to have a leased line between the main site and > the remote site to support voice and data requirements. However, the > customer want to make sure that stable voice communication between the two > sites is always available, hence when the leased line is not stable (for > instance there were a lot of hits on the link) or down, the voice should be > rerouted to the PSTN. Please advice how to configure the CM/router such > that the call can be routed to the PSTN when the leased line is not stable. > Can I use policy routing to achieve this? > > Thanks in advance! > > Maurice Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=28055&t=28043 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
