[cisco-voip] CCM Cross WAN Clustering

[Davis, Michael]

In larger, high volume, or IPCC (Ent) or (Express) environments,  there can also be serious issues with CTI Manager as well as call processing synchronization across a slower or unreliable links.  Situations where there are devices controlled by a subscriber on one side of the link are talking to devices controlled by different subscribers on the other side of the "slow" link.
 
I think for this reason, Cisco sets forth the 40ms RTT rule. I've seen situations where a functioning split custer link became over subscribed, resulting in the need for CCM and/or CTIM restarts,  Random or all Route Points unregistering,  JTAPI failures, etc.
 
________________________________

From: cisco-voip-bounces at puck.nether.net on behalf of Alan Su
Sent: Wed 6/14/2006 12:14 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] CCM Cross WAN Clustering


Dear All,
 
>From cisco document, the clustered CCM servers should meet the requirement of 40ms round-trip time for database replication. In my case, the 2 sites connected by IPLC with about 50ms. So I did some lab test to make sure it will be working in my environment. But I found out that even in 200ms round-trip time lab, the replication is still working!! I'm wondering that is it a normal case or I misconfigure something. Does anybody have any clue about this? 
 
Thanks.
 
Regards,
 
Alan