Share Conductor between two CUCM Cluster

[carlo alberto michelotti]

Hi,

a my customer have two separate cucm cluster.

the first cluster is dedicated to phones and jabbers, the second cluster is dedicated to the telepresence endpoints.

both cluster are connected via sip trunk.

now he want to implement a dedicated telepresence server (TPS) for jabber users for instant meeting and another TPS dedicated Telepresence  scheduled meetings.

my idea is to install one conductor that manage both  TPS and trunk it with the 2 cucm. 

based on your experience this is a supported scenario? 

thanks,

C.

[Patrick Sparkman]

I've never done such a thing, but it should work, but most likely not supported.

[Jaime Valencia]

Actually I believe that's supported, you would just need to keep adding IPs as required, and binding them to a new ad-hoc or rendezvous config for each cluster.