■ version and the deployment of OCS
OCS version of the Standard Edition and the deployment of OCS, Enterprise Edition yireoge two versions. Therefore, the number of users it off let's look at what constituted deployment.
□ Standard Edition: supports up to 5,000 users
□ Enterprise Edition: How to deploy two offers.
** Back-end database must be installed on a separate physical machine. Any machine that is installed in the same role and OCS will not support it. Add a small server applications and OCS are not shared with other instances of SQL is required.
-- Enterprise Edition (Consolidated):
Up to 25,000 user support, all of the features you insert one server deployment. So, one of the largest, distributing simple
- Enterprise Edition(Extended) : -- Enterprise Edition (Extended):
■ OCS functional server role
Back in the previous LCS-end, front-end, Access Proxy, Director, Proxy, the same functional category, which was present at the logical server roles we remember. Here counterparts, the role of OCS, the new name of the server line. Conferencing capabilities because of the addition of multiple servers has been added to this role, especially in the sectors that are to be distributed DMZ Access Proxy server roles are now multiple granular xxxEdge name changed. That is what is what Edge server distributed to all sectors DMZ server role as a support for external users of the things that exist.
Below is a feature to provide additional information about the distribution server role. Of course, back-end, front-end, the base should be deployed.
Provide capabilities
Add to the server role.
Client
Provides status information for internal users and IM
No additional server roles required. No additional server roles required.
Communicator 2005 or 2007 Communicator 2007 is required for enhanced presence Communicator 2005 or 2007 Communicator 2007 is required for enhanced presence
On-premise Web Conferencing On-premise Web Conferencing
Standard Edition: No additional server roles required. Standard Edition: No additional server roles required. Enterprise Edition: Web Conferencing Server and Web Components Server Enterprise Edition: Web Conferencing Server and Web Server Components
Communicator 2007 Live Meeting 2007 client Outlook add-in for scheduled conferences Live Meeting 2007 Communicator 2007 client add-in for Outlook conferences scheduled
Address Book Server Address Book Server
No additional server roles required. No additional server roles required. Enterprise Edition: Web Components Server Enterprise Edition: Web Server Components
No requirement No requirement
Archiving and Call Detail Records Archiving and Call Detail Records
Archiving and CDR Service Archiving and CDR Service
Access to external users
Access Edge Server * Edge Access Server * HTTP reverse proxy* HTTP reverse proxy *
Communicator 2005 or 2007 Communicator 2005 or 2007
(Federation) Union (Federation)
Public IM Connectivity(PIC) Public IM Connectivity (PIC)
Web conferencing External users with Web conferencing
Web Conferencing Edge Server* Edge Server * Web Conferencing HTTP reverse proxy* HTTP reverse proxy *
Communicator 2007 Live Meeting 2007 client Live Meeting 2007 Communicator 2007 client
Audio/Video Conferencing External users with the Audio / Video Conferencing
A/V Conferencing Edge Server* A / V * Conferencing Server Edge
Web browser-based client that provides information about the status and IM
Communicator Web Access Server Communicator Web Access Server
Communicator Web Access Communicator Web Access
Enterprise Voice Enterprise Voice
Mediation Server and basic media gateway Mediation Server and basic media gateway OR basic-hybrid media gateway (Mediation Server is collocated with basic media gateway) Basic-hybrid media gateway (Mediation Server is collocated with basic media gateway) OR advanced media gateway (Mediation server logic incorporated in gateway design; available soon) Advanced media gateway (Mediation server logic incorporated in gateway design; Available soon) A/V Edge Server (on which the A/V Authentication Service is collocated) A / V Edge Server (on which the A / V Authentication Service is collocated)
Communicator 2007 OR Office Communicator 2007 Phone Experience Office Communicator 2007 OR 2007 Communicator Phone Experience
Director: Director server roles are still present in the user authentication process can be adapted Pool in front. . Specifically, the role of the external server, user support and deployment scenarios, which are recommended. This old host users, but it is not, as a domain member server to access the AD user authentication process to carry them outside, but also within the Pool appropriate front-end server, which acts as a traffic routing.
Server Server
Required to Support Required to Support
Corresponding Internal Server Required Corresponding Internal Server Required
Protocol Protocol
Access Edge Server Edge Access Server
Public IM, Federation,Conference, Voice Public IM, Federation, support for internal users remote access, externally or internally by the Conference, features Voice Link for support
Office Communications Server 2007 server or pool and, optionally, a Director Office Communications Server 2007 server or pool and, optionally, a Director
Session Initiation Protocol (SIP) Session Initiation Protocol (SIP)
Web Conferencing Edge Server Edge Web Conferencing Server
External Web conferencing External Web conferencing
Web Conferencing Server Web Conferencing Server
Persistent Shared Object Model (PSOM) Persistent Shared Object Model (PSOM)
A/V Edge Server A / V Server Edge
A/V conferences with external users Point-to-point A/V calls with external users A / V Point-to-point conferences users with external A / V calls with external users
A/V Conferencing Server A / V Conferencing Server
RTP/RTCP, Simple Traversal of UDP through NAT (STUN)/ RTP / RTCP, Simple Traversal of UDP through NAT (STUN) /
Reverse Proxy Reverse Proxy
Group Expansion(. Expansion Group (extended deployment group) and the address book file downloads required.(ppt) Web conferencing for meeting the need for access to materials (ppt)
Web server (IIS) Web server (IIS)
HTTP(s) HTTP (s)
Ports and Protocols Used by Office Communications Server and Clients
Topology Topology
Server Role Server Role
Recommended CA Recommended CA
Subject Name/ Subject Name / Common Name Common Name
SAN SAN
Comments Comments
Standard Edition server Standard Edition server
All server roles (which are collocated) All server roles (which are collocated)
Enterprise CA.
FQDN of the Standard Edition Server FQDN of the Standard Edition Server
If you have multiple SIP domains and have enabled automatic client configuration, the certificate wizard detects and adds each supported SIP domain FQDNs. If you have multiple SIP domains and have enabled automatic client configuration, the certificate wizard detects and adds each supported SIP domain FQDNs. (The wizard detects any SIP domains you specified during setup and automatically adds them to the SAN) (The wizard detects any SIP domains you specified during setup and automatically adds them to the SAN)
Additionally, you must use the IIS administrative snap-in to assign the certificate used by the Web Component Server Additionally, you must use the IIS administrative snap-in to assign the certificate used by the Web Component Server
Enterprise pool: consolidated Enterprise pool: consultants
All server roles. All server roles. Certificate configured on each Enterprise Edition Server Certificate configured on each Enterprise Edition Server
Enterprise Enterprise CA.
FQDN of the pool FQDN of the pool
For the Web Components Server role, the certificate must have the URL of the internal Web farm in the SN or SAN. For the Web Components Server role, the certificate must have the URL of the internal Web farm in the SN or SAN.
If you have multiple SIP domains and have enabled automatic client configuration, the wizard detects the SIP domains, adds them to the SAN, and then adds each supported SIP domain FQDN. If you have multiple domains and SIP have enabled automatic client configuration, the wizard detects the SIP domains, adds them to the SAN, and then adds the SIP supported each domain FQDN.
(The wizard detects any SIP domains you specified during setup and automatically adds them to the SAN) (The wizard detects any SIP domains you specified during setup and automatically adds them to the SAN)
For the Web Components Server role, the certificate must have the URL of the internal Web farm in the SAN (if the FQDN is different from the pool FQDN). For the Web Server Components role, the certificate must have the URL of the Web farm in the internal SAN (FQDN if the pool is different from the FQDN).
Certificate must be installed on each server in the pool. Certificate must be installed on each server in the pool.
Additionally, you must use the IIS administrative snap-in to assign the certificate used by the Web Component Server. Additionally, you must use the IIS administrative snap-in to assign the certificate used by the Web Component Server.
Enterprise pool: expanded Enterprise pool: expanded
Front End Front End
Enterprise CA
If you have multiple SIP domains and have enabled automatic client configuration, add each supported SIP domain FQDN. If you have multiple SIP domains and have enabled automatic client configuration, add each supported SIP domain FQDN.
Certificate must be installed on each server in the pool Certificate must be installed on each server in the pool
Web Conferencing Web Conferencing
A/V Conferencing A / V Conferencing
Web Components Web Components
FQDN of the VIP (virtual IP) of the load balancer used by the Web Components Server FQDN of the VIP (virtual IP) of the load balancer used by the Web Components Server
SAN must contain the URL of the internal Web farm in the SAN (if the FQDN is different from the pool FQDN) SAN must contain the URL of the internal Web farm in the SAN (if the FQDN is different from the pool FQDN)
A certificate has to be configured in IIS on the all servers that are running the Web Component Services A certificate has to be configured in IIS on the all servers that are running the Web Component Services
Director, Director, Standard Edition Standard Edition
Director
FQDN of Standard Edition Server FQDN of Standard Edition Server
If you have multiple SIP domains and have enabled automatic client configuration and all clients use this Director for logon, add each supported SIP domain FQDN. If you have multiple SIP domains and have enabled automatic client configuration and all clients use this Director for logon, add each supported SIP domain FQDN.
Director, Director, Enterprise pool Pool Enterprise
.
Array of Standard Edition Directors Array Standard Edition of Directors
FQDN of the Director Server Director of the FQDN Server
FQDN of Director Server and the FQDN of the virtual IP ( FQDN Director of Server and the FQDN of the virtual IP ( VIP) used by the array VIP) used by the array.
If you have multiple SIP domains and have enabled automatic client configuration and all clients use this Director for logon, add each supported SIP domain FQDNs. If you have multiple SIP domains and have enabled automatic client configuration and all clients use this Director for logon, add each supported SIP domain FQDNs.
FQDN of the server is in the SUBJECT field FQDN of the server is in the SUBJECT field
FQDN of the Director Director of the FQDN VIP and the FQDN of the server must be in the SUBJECT_ VIP and the FQDN of the server must be in the SUBJECT_ ALT_NAME as DNS values ALT_NAME as DNS values
Component (Server role or client) Component (Server role or client)
Port Port
Notes Notes
Front End Servers Front End Servers
5060/5061
TCP
MTLS
Used by Standard Edition Servers and Used by Standard Edition and Servers Enterprise pools for all internal SIP communications between servers and between servers and Office Communicator Enterprise pools for all internal SIP communications between servers and between servers and Office Communicator
443
HTTPS
Communication from front-end servers to the Web farm FQDNs (the URLs used by Web Components) Communication from front-end servers to the Web farm FQDNs (the URLs used by Web Components)
444
Communication between the focus (Office Communications Server component that manages conference state) and the conferencing servers Communication between the focus (Office Communications Server component that manages conference state) and the conferencing servers
135
DCOM and RPC DCOM and RPC
Used when a load balancer is deployed, port 135 is used by the Front End Servers for WMI operations and moving users (a remote DCOM-based database operation) Used when a load balancer is deployed, port 135 is used by the Front End Servers for WMI operations and moving users (a remote DCOM-based database operation)
HTTPS traffic to the pool URLs HTTPS traffic to the pool URLs
TLS
HTTPS communications to Web Components Servers Components HTTPS communications to Web Servers
HTTPS between the Web Conferencing Server and the Front End Server HTTPS between the Web Conferencing Server and the Front End Server
8057
Used to listen to direct PSOM connections from Live Meeting client Used to listen to PSOM direct connections from client Live Meeting
5063
Used for incoming SIP listening requests Used for incoming SIP listening requests
49152 – 65535 media port range 49152 - 65535 media port range
UDP
Port range used for media requests sent. Port range used for media requests sent.
Used for SIP/TLS communications from external users on both the internal and external firewalls for external user access Used for SIP / TLS communications from external users on both the internal and external firewalls for external user access
5061
Used for SIP/MTLS communication for remote user access or federation. Used for SIP / MTLS communication for remote user access or federation.
Used for SIP/TLS communication for remote user access Used for SIP / TLS communication for remote user access
Used to listen for PSOM/MTLS communications from the Web Conferencing Server on the internal interface of the Web Conferencing Edge Server Used to listen for PSOM / MTLS communications from the Web Conferencing Server on the internal interface of the Web Conferencing Edge Server
Used for inbound communications for access of remote, anonymous and federated users to access internal Web conferences Used for inbound communications for access of remote, anonymous and federated users to access internal Web conferences
Used for STUN/TCP inbound and outbound media communications to allow external users to access media and A/V sessions Used for STUN / TCP inbound and outbound media communications to allow external users to access media and A / V sessions
5062
Used for SIP/MTLS authentication of A/V users. Used for SIP / MTLS authentication of A / V users. Communications flow outbound through the internal firewall. Communications flow outbound through the internal firewall.
3478
Used for STUN/UDP inbound and outbound media communications Used for STUN / UDP inbound and outbound media communications
50,000-59,999 50000-59999
RTP/TCP RTP / TCP
Used for inbound and outbound media transfer through the external firewall. Used for inbound and outbound media transfer through the external firewall.
Office Communicator Office Communicator
5060
TCP (SIP) TCP (SIP)
Used by Office Communicator for SIP communications internally Used by the Office Communicator for SIP communications internally
Used by Office Communicator for SIP communications internally and for SIP/MTLS authentication of A/V users. Used by the Office Communicator for SIP communications internally and for SIP / MTLS authentication of A / V users. Communications flow outbound through the internal firewall Communications flow outbound through the internal firewall
TCP (HTTP) TCP (HTTP)
Used by Communicator clients connecting from outside the intranet for SIP communications Used by Communicator clients connecting from outside the intranet for SIP communications
1024-65535
UDP/TCP UDP / TCP
Port range used for inbound and outbound media transfer through the external firewall. Port range used for inbound and outbound media transfer through the external firewall.
6891-6901
Port ranged used by Office Communicator for file transfer. Port ranged used by Office Communicator for file transfer.
Live Meeting 2007 client Live Meeting 2007 client
Used by Live Meeting 2007 clients connecting from outside the intranet for: Used by Live Meeting 2007 clients connecting from outside the intranet for:
SIP traffic sent to the Access Edge Server SIP traffic sent to the Access Edge Server
PSOM traffic sent to the Web Conferencing Edge Server PSOM traffic sent to the Web Conferencing Edge Server
Used for outgoing PSOM traffic sent to the Web Conferencing Server Used for outgoing PSOM traffic sent to the Web Conferencing Server
Used for SIP/TLS communication between Live Meeting and the Front End Servers or the Access Edge Server and for SIP/MTLS authentication of A/V users. Used for SIP / TLS communication between Live Meeting and the Front End Servers or the Access Edge Server and for SIP / MTLS authentication of A / V users. Communications flow outbound through the internal firewall Communications flow outbound through the internal firewall
Port range used for inbound and outbound media transfer through the external firewall Port range used for inbound and outbound media transfer through the external firewall
Port ranged used by Live Meeting for file transfer Port ranged used by Live Meeting for file transfer
Maximum Supported Users for each Topology
Servers Required Required Servers
Maximum Users Supported Maximum Users Supported
Standard Edition Server Standard Edition Server
1 Standard Edition server A Standard Edition server (Optional) Archiving Server collocated (Optional) Archiving Server collocated
5,000
Enterprise pool: Consolidated Configuration Enterprise pool: Consolidated Configuration
4 Enterprise Edition Front-End servers running all server roles 4 Enterprise Edition Front-End servers running all server roles 1 Backend 1 Backend SQL Server SQL Server (Optional) 1 Archiving Server Archiving Server (Optional) 1
30,000
Enterprise pool: Expanded configuration Enterprise pool: Expanded configuration
With Mid-Range Performance SQL Backend With Mid-Range Performance SQL Backend
4 Front-End Servers 4 Front-End Servers 2 Web Conferencing Servers 2 Web Conferencing Servers 2 A/V Conferencing Servers 2 A / V Conferencing Servers 2 IIS Servers 2 IIS Servers 1 Backend SQL Server A SQL Server Backend (Optional) 1 Archiving Server Archiving Server (Optional) 1
50,000
With High Performance SQL Backend With High Performance SQL Backend
8 Front-End Servers 8 Front-End Servers 4 Web Conferencing Servers 4 Web Conferencing Servers 4 A/V Conferencing Servers 4 A / V Conferencing Servers 2 IIS Servers 2 IIS Servers 1 Backend SQL Server A SQL Server Backend (Optional)2 Archiving Servers (Optional) 2 Archiving Servers
125,000
Edge server topologies assume 10 percent of the total user base will be connected from outside the intranet Edge server topologies assume 10% of the total user base will be connected from outside the intranet
Supported Performance Supported Performance
Stand-alone Access Edge Server Stand-alone Edge Access Server
15,000 client connections 15,000 client connections
Stand-alone Web Conferencing Edge Server Stand-alone Web Conferencing Server Edge
3,000 client connections 3,000 client connections
Stand-alone A/V Edge Server Stand-alone A / V Server Edge
1,500 concurrent audio/video sessions 1,500 concurrent audio / video sessions
Collocated Access Edge & Web Conferencing Edge Server Edge Access Server & Web Conferencing Collocated Edge
Access Edge Server: 5,000 client connections Edge Access Server: 5,000 client connections
Web Conferencing Edge Server: 1,500 client connections Web Conferencing Server Edge: 1,500 client connections
Collocated Access Edge, Web Conferencing Edge & A/V Edge Servers (Consolidated Edge Topology) Collocated Access Edge, Edge Web Conferencing & A / V Edge Servers (Consolidated Edge Topology)
Access Edge Server: 5,000 client connections Edge Access Server: 5,000 client connections Web Conferencing Edge Server: 1,000 client connections Web Conferencing Server Edge: 1,000 client connections A/V Edge Server 500 concurrent audio/video sessions A / V Edge Server 500 concurrent audio / video sessions Note A/V experience may be degraded if sessions approach the maximum limit. Note A / V experience may be degraded if sessions approach the maximum limit. We recommend that you deploy a separate A/V Edge Server for the optimal A/V experience We recommend that you deploy a separate A / V Edge Server for the optimal A / V experience