Presence 7 Multi-Node, SRV, and CUPC

[joshproano]

In looking at the deployment guide for CUPS7 there are several deployment models for balancing users within subclusters and references to the use of SRV records to facilitate seemless failover between failed nodes for subscribe and message requests. While this makes sense for server to server communications there seems to be a gap in the end user experience where the subcluster name would not be used for a similar load balanced or active standby login process via the CUPC client.

The initial testing with the SRV records indicate a correct list of system however the CUPC client doesnt seem to utilize them for initial login.

Anyone have any insight on the CUPC interaction on a multinode deployment and the underlying DNS framework to support it.

[htluo]

SRV record is only utilized by Cisco for SIP redundancy.

CUPC logon does not use SIP protocol.  It uses SOAP to communicate with CUPS server.  After logon, CUPC will use SIP for presence and IM.

If you'd like CUPC use SRV for logon redundancy, you may submit a feature request through a Cisco account manager.

Michael

http://htluo.blogspot.com

[Aaron Harrison]

Hi Michael

So there is no redundancy for logon traffic from CUPS to CCM (i.e. it uses the defined Publisher, and no others)?

What about resilience for the initial logon traffic from CUPC to CUPS?

Thanks

Aaron

[htluo · Accepted solution]

1) There's no logon traffic from CUPS to CCM.  All logon request was handled by CUPS alone.  (if LDAP authentication was used, it's CUPS+LDAP).

2) After 1st-time logon, CUPC retrieves a list of servers from CUPS and store it locally on the PC.  On next time logon, if the "home server" was unavailable, CUPC will look at its local file and try the next one.

More details can be found in http://www.lulu.com/content/5552336

Thanks!

Michael

[joshproano]

Hi Mike,

Thanks for the reply.. Based on the deployment guide the SubCluster SRV is then merely a mechanism for inter-

subcluster communiction resilliency and or publish resilliency for CUCM<->CUPS

JP