[cisco-voip] CRS 3.5.1

[Kevin Thorngren]

What you are configuring is redundancy only in the event of CTI Manager  
service failure.  There are some things you will need to configure in  
CallManager to complete this portion of the configuration.  I would  
suggest reading the high availability section of the IPCC Express SRND,  
found here: http://www.cisco.com/go/srnd

The SRND also describes how redundancy works and the limitations  There  
is a section that describes what you need to do for CRS server  
redundancy as it is not automatic in 3.5.  Basically you will create a  
mirror image of the CRS server to use in an offline server in case of  
failure.  The expectation for this option is that the CRS server is  
running on a standalone server.

There are also some limitations if the Publisher goes down DC Directory  
is being used.  This URL provides steps to configure redundant LDAP  
URL.
http://www.cisco.com/en/US/products/sw/custcosw/ps1846/ 
products_tech_note09186a00804b4982.shtml

Kevin

On Feb 27, 2006, at 1:52 AM, Robin H wrote:

> I have ICD application based on CRA 3.5.1 and installed it in
> Pubslisher server. I read a documentation that we need to put both
> publisher and subscriber IP to provide redundancy. With this info, i
> have put both publisher and subscriber ip in the JTAPI and RMJTAPI
> setup page. But I only installed and setup the application on
> Publisher server (coresident) and nothing at Subscriber server. When
> the Publisher server down, the ICD application was also failed. Anyway
> to prevent this? Should I install and setup CRA application on
> Subscriber server as well? Please send me reference page if any.Thanks
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>