Support Local Server Priority for Users While Maintaining Global Community Connection Merged

When a customer has two physical offices (Office A and Office B), users in Office A require priority access to the Sametime server deployed in Office A, while users in Office B require priority access to the Sametime server deployed in Office B. Users from Office A must still be able to chat with users in Office B, which requires inter‑server communication between the Sametime servers in both offices.

This capability is available and documented for Domino‑based Sametime deployments, as referenced here:

https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0024731

However, this local‑server priority functionality is not currently supported in either containerized or non‑containerized deployments of Sametime 12.0.3.

Accordingly, need Sametime 12.0.3 (both containerized and non‑containerized editions) be enhanced to support user‑based local server prioritization while maintaining full connectivity to the global Sametime community.