How to Deploy with Microsoft Office Communications Server

This article refers to firmware 3.1 and higher, running on model 340 or higher, and Microsoft Office Communications Server 2007 R2 Enterprise Edition.

This article assumes you are connected to the Barracuda Load Balancer web interface and have an activated subscription.
The deployment tasks in this article are based on the example described in the article Microsoft^® Office Communications Server Deployment Example.
For a description of supported deployment options, refer to Understanding Microsoft Office Communications Server Deployment.

If your Barracuda Load Balancers are clustered, the configuration between the active and passive systems is synchronized; there is no need to modify any passive Barracuda Load Balancers.

To deploy the Barracuda Load Balancer in an Office Communications Server environment, complete the following tasks:

Deployment Task	Where
Task 1. Modify TCP and UDP Connections Settings.	Do this on all active Barracuda Load Balancers, both internal and external. If your systems are clustered, the passive systems do not need to be configured separately.
Task 2. Configure Enterprise Pool Services.	Do this on the internal-facing Barracuda Load Balancers.
If you have an edge deployment, you must also complete the following tasks:
Task 3. Configure Internal Edge Services.	Do this on the internal-facing Barracuda Load Balancers.
Task 4. Configure External Edge Services.	Do this on the external-facing Barracuda Load Balancers.
Task 5. Confirm the Configure Edge Server Wizard Setting.	Check this on all Edge Servers.
If you have deployed Director Servers, you must also do the following task:
Task 6. Configure Director Services.	Do this on the Director Barracuda Load Balancers.
If you have deployed Communicator Web Access, you must also complete the following task:
Task 7. Configure Communicator Web Access Services.	Do this on the CWA Barracuda Load Balancers.

Task 1. Modify the TCP and UDP Connections Settings

The Barracuda Load Balancer comes configured with default settings that work with most applications. Office Communications Server requires changes to the default advanced IP settings on the Barracuda Load Balancer to ensure it complies with Microsoft’s specifications.

To modify the TCP and UDP Connections settings on the System Settings page:

Go to the ADVANCED > System Settings tab in the web interface.
In the TCP Connections Timeout box, enter 1800 (30 minutes).
In the UDP Connections Timeout box, enter 1800 (30 minutes).

Task 2. Configure Enterprise Pool Services

To configure all Services needed for an internal OCS deployment:

Go to the BASIC > Services page in the web interface.
Add each Service listed in the table using the steps that follow; all of these Services are required :
For the DCOM WMI Front Service only, edit each Real Server associated with the Service by clicking the Edit icon next to each Real Server entry in the table. On the Real Server Detail page that appears:
1. In the Server Monitor section, set the Testing Method to TCP Port Check.
2. In the Port field, enter the value 5061. It is better to test port 5061 for this Service because port 135 always passes the TCP port check even if OCS Services are not responding.

To add a Service:

In the Service Name box, enter the name for the Service.
In the Virtual IP Address box, enter the IP address for the FQDN of your Internal OCS Pool.
Select the protocol and in the Port box, enter the port for the Service in the table.
In the Real Servers box, enter the IP address for every Front-End server in your OCS Pool.

The following Services are optional ; add each Service only if you have deployed that feature.

Service Name	Virtual IP Address	Protocol	Port	Real Servers
Application Sharing (optional)	IP for FQDN of Internal enterprise OCS Pool	TCP	5065	IP addresses of your Front-End Servers (K and L from the example)
QoE Agent (optional)	IP for FQDN of Internal Enterprise OCS Pool	TCP	5069	IP addresses of your Front-End Servers (K and L from the example)
Response Group Service (optional)	IP for FQDN of Internal Enterprise OCS Pool	TCP	5071	IP addresses of your Front-End Servers (K and L from the example)
Conferencing Attendant (optional)	IP for FQDN of Internal Enterprise OCS Pool	TCP	5072	IP addresses of your Front-End Servers (K and L from the example)
Conferencing Announcement (optional)	IP for FQDN of Internal Enterprise OCS Pool	TCP	5073	IP addresses of your Front-End Servers (K and L from the example)
Outside Voice Control (optional)	IP for FQDN of Internal Enterprise OCS Pool	TCP	5074	IP addresses of your Front-End Servers (K and L from the example)

For each Service created, edit the Service by clicking the Edit icon next to the Service entry in the table. On the Service Detail page that appears:

In the General section, set Service Type to TCP Proxy.
In the Advanced Options section, set Session Timeout to 0 (session never times out).