Under normal HA failover circumstances, the users should not lose the association they already have. Granted, new users will not be able to be assigned when HA is broken. So, this seems like a defect to me. Or, quite possibly a change in behavior from what I am used to, in which case, that's terrible to have to re-assign all users upon failover, especially if you've chosen manually as opposed to automatic assignment, because you need users on certain pairs, in a multi-pair environment.
If you think it's a matter of distance, you need to check that the network characteristics are meeting the requirements for clustering over the wan <https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab12/collab12/models.html#pgfId-1043996>. E.g., There is a steady 1.5Mbps required between sites, and then you must factor in: additional sites, users and activity on top of that. QoS plays an important role to ensure the network performs the way you designed it to under no congestion/load. On Mon, Sep 14, 2020 at 1:16 AM naresh rathore <[email protected]> wrote: > hi > > > I currently have cucm 12.5.1.11900-146, primary cucm and im and presence > is installed in Sydney and secondary is installed in Newzealand. often i > see user disassociated with presence server and user are not able to login > to jabber. i have to to again assign all user to presence server. also > sometime see following presence redudancy status. is it because of these > devices are installed far away > > > > > > Regards > > > Nareh > _______________________________________________ > cisco-voip mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/cisco-voip >
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
