Domain 2 configuration

Last Updated : Nov 22, 2018 |
Prolog information
Metadata
Keywords:
The Avaya Aura® system in domain 2 is configured to use Inter-PS federation to enable users and the Microsoft users to watch Avaya Aura® users in domain 1. Signaling for Microsoft users watching Avaya Aura® users in domain 1 is tandemed through the Presence Services in domain 2. All signaling is routing through Avaya Aura® Session Border Controller at the edges of each domain. Use of Avaya Aura® Session Border Controller is optional, since no message manipulation is required, but recommended to protect each domain from the public network
Following are the sets of routing configuration required:
  1. Inter-PS federation between the domain 1 and domain 2. For more information, see Checklist for configuring federation between two Presence Services clusters on different System Managers.
  2. Microsoft internal domain federation within domain 2 between the Avaya Aura® and Microsoft systems. For more information, see Microsoft Real Time Communication (RTC) Federation.
  3. Additional Session Manager routing configuration required to force Microsoft internal federation signaling into Presence Services in domain 2. For more information, see Configuring Microsoft Internal Domain Federation.
Related links
Microsoft federation with internal and external domains using inter-PS federation
Microsoft Real Time Communication (RTC) FederationChecklist for configuring federation between two Presence Services clusters on different System ManagersConfiguring Microsoft internal domain federation