<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hi Anthony,</div><div><br></div><div>I dare say that the CUPS BU did not give user assignment much thought with regards to geographical regions. </div><div><br></div><div>What I would do in this instance (and may or may not be possible for you to re-design) is to have separate clusters for your East Coast and West Coast. This would be achieved by changing the LDAP to point 1 cluster to a more specific geographical OU. </div><div><br></div><div>For CUCM you can easily set up ILS/GDPR to exchange your extensions between cluster and EMCC (Extension Mobility Cross Cluster) is fairy trivial. This setup would also support centralised TFTP for phone registration and centralised Jabber login. Now when it comes to CUPS, you will of course be using Inter-cluster Peering. The downside to this for both CUCM and CUPS, there is no redundancy between East Coast and West Coast (between your DC's) but this can still be achieved with subscribers in each DC.</div><div><br><div>Sent from my iPhone</div></div><div><br>On 26 Apr 2016, at 04:51, Anthony Holloway <<a href="mailto:avholloway+cisco-voip@gmail.com">avholloway+cisco-voip@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">All,<div><br></div><div><b>My specific environment is</b></div><div>CUCM 11.0(1a)SU1</div><div>IM&P 11.0(1)</div><div>Jabber for Windows 11.5(2)</div><div><br></div><div>Clustering over the WAN with local failover</div><div>2x CUCM nodes and 2x IM&P nodes in DC1 (east coast)</div><div>2x CUCM nodes and 2x IM&P nodes in DC2 (west coast)<br></div><div><br></div><div><b>The Challenge</b></div><div>I need to *easily* assign users to the proper Presence Redundancy Group, based on geographic region of the user.</div><div><br></div><div><b>My Thoughts</b></div><div>First off, I needed to change the <b>CUCM > Enterprise Parameters > User Assignment Mode for Presence Server</b> setting to <b>None</b>, so that if someone clicks the <b>CUCM > User Management > Assign Presence Users > Rebalance Users</b> button, it doesn't destroy the geographic assignments I'll have worked so hard to maintain.</div><div><br></div><div>Second, I know that the <b>CUCM > User Management > Assign Presence Users </b>setting takes precedence over the <b>CUCM > User Management > User Settings > Service Profile > IM and Presence Profile</b>. Otherwise, I'd just assign users to <b>Service Profiles</b> by way of <b>Feature Group Templates</b> assigned to different <b>LDAP Directory</b> sync agreements.</div><div><br></div><div>Third, <b>BAT > Users > Update Users > Query</b> has very little fields to filter on. How hard would it be to add a few more fields in here Cisco? There's just no way this is useful. <b>BAT > Users > Update Users > Custom File</b> has promise, but because of its mandatory User Template usage, it'll need some careful testing with the Ignore Fields option. I'm not excited about that method, unless one of you calms my fears.</div><div><br></div><div>What I would like to ask the group is, how are you doing this, or how would you suggest doing this? I.e., Your process to assign users, both existing in the system today, and newly synced from LDAP, to their geographic IM&P nodes and therefore Presence Redundancy Groups? I'm not quite looking for a SQL query method, or an AXL method, something a operations person could manage through the GUI.</div><div><br></div><div>Thanks.</div><div></div></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>cisco-voip mailing list</span><br><span><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a></span><br><span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br><span></span><br></div></blockquote></body></html>