Organization Identification - Polycom realpresence 1800 Administrator's Manual

Organization Identification

In multiple tenant scenarios, the DMA maintains a prefix table, in which each Federated organization is
allocated a unique prefix, mapped to the respective organization initiating the meeting by its CAA's SIP URI.
In single tenant scenarios, since the conference ID, is unique only within the Lync server which allocated it,
a prefix is added to the conference ID to enable the DMA to identify remote RealConnect Lync conferences.
The Lync service administrator of an organization hosting Lync meetings, can add the respective
organization prefix into the Outlook meeting invites sent by meeting organizers. This insertion requires the
Lync service administrator to configure the added text only once, via the Lync conference template, at the
point of the RealConnect service deployment.
For more information on CAA SIP URI and Organization Prefix, see
Process Guidelines
● To overcome the absence of a Trusted Application Relationship, the DMA utilizes the Microsoft CAA
service.
● Lync Meeting invites include the Lync conference ID, and at the bottom, the prefix of the federated
organization.
● The RealConnect connection is established within 7 seconds, at the most.
● The audio/video of non-Lync participants is muted/suspended during the process, so as to keep the
RealConnect process hidden.
Once RealConnect of Collaboration Server and AVMCU conferences is complete, non-Lync
participants may receive audio/video depending on conference configuration (i.e., if dependent on
chairperson presence).
Polycom®, Inc.
Appendix H - Deployment Into Microsoft Environments
Polycom Microsoft Deployment Guide.
995