As a follow-up to my post on Installing OCS 2007 R2 Prerequisites on Windows Server 2008 I will in this post describe how you can. Mediation Server on Windows. Learn how to set up an Office Communications Server 2007 R2. This Step-By-Step guide will walk you through the entire deployment process!
OCS 2. 00. 7 Installation - Part 1 . In the examples that follow the internal domain name is ptown.
SIP domain, or my external facing address will be confusedamused. Domain Controller for ptown. DNS Server for ptown. Certificate Authority named P- Town Certificate Authority Domain in 2.
In my preceding post, I have covered step by step deployment process of Front End server pool. This post covers the step by step process to deploy mediation server pool. Why Location Profile on OCS 2007 Mediation Server? Use this page to find technical documentation to help you understand, plan, deploy, and operate Microsoft Office Communications Server 2007 R2 servers. Sonus Documentation Portal: Skip to content; Skip to breadcrumbs; Skip to header menu. Sonus Networks Technical Publications.
Native Mode IP Configuration: 1. Gateway: 1. 92. 1. DNS: 1. 27. 0. 0. Blank Windows 2. 00.
Server joined to the ptown. IIS Installed with ASP. Adminpak. exe installed IP Configuration: 1. Gateway: 1. 92. 1.
DNS: 1. 92. 1. 68. Schema Preparation. On tap- ocs- 2k. 7. You’ll see a message that the Visual C++ 2.
Click Yes. On the main setup screen click Deploy Standard Edition Server. Now click Prepare Active Directory. Press the Run button under Prep Schema. The Schema Preparation Wizard starts. Click Next. Assuming the installation media has not been modified, the schema files should be in the same directory as setup so press Next. Press Next again to start the schema preparation.
A success dialog will appear when it finishes. Check the box to view the log if desired, but press Finish to continue. At this point you should wait and then verify the schema has replicated to all domain controllers in the forest before continuing. Forest Preparation. Press the Run button under Prep Forest.
The Forest Preparation Wizard starts. Press Next. Leave the default selection of System container in the root domain and press Next.
Select forest root domain, ptown. Next. Select the external SIP domain, confusedamused. Next. Confirm the forest preparation settings and press Next. A success dialog will appear when it finishes. Check the box to view the log if desired, but press Finish to continue. Again, wait for the changes to be replicated to the entire forest before continuing. Domain Preparation.
Press the Run button under Prep Domain. The Domain Preparation Wizard starts. Press Next. Press Next to acknowledge the warning about group creation. Confirm the domain preparation settings and press Next. Check the box to view the log if desired, but press Finish to continue. This time wait for the changes to be replicated to the entire domain OCS is being deployed within.
Run the domain preparation wizard for any other domains hosting OCS. At this point OCS admin rights can be delegated to users and groups.
- Communications Server 2007, Mediation Server and a third-party basic media gateway function as a single logical unit to enable communication between the.
- So I'm experiencing a very strange issue. I am working on an OCS load balanced pool. One mediation server and then a load balancer for the two front end.
- The Mediation Server role sits under the radar in most organizations running Microsoft Lync Server 2013, but it could be considered one of the most.
- It might be useful in a Cisco direct SIP environment to automatically strip the + from all outgoing SIP communication from an OCS Mediation server.
This can also be accomplished later by running the wizard again. Press the Deploy Standard Edition link at the top to go back and deploy the Standard Edition Server. Deploy Server. Click the Run button under Deploy Server to start the installation process. The Deploy Server Wizard starts. Press Next. Accept the license terms and press Next. Choose an installation location and press Next. Enter a password for the RTCService account and press Next.
Enter a password for the RTCComponent account and press Next. Accept the default blank external web farm FQDN’s for now.
The external address will adjusted later. Press Next. Select a location for the database and transaction logs. Ideally, these should be on separate disk controllers.
Press Next. Review the configuration settings and press Next to start the installation. A success dialog will appear when it finishes.
Check the box to view the log if desired, but press Finish to continue. Configure Server. The Deploy Server section should now have a green checkmark next to it. Click the Run button under Configure Server to continue. The Configure Pool/Server Wizard should start. Press Next to continue.
Press Next to accept the only server installed so far, tap- ocs- 2k. The SIP domain was already entered earlier, but additional SIP domains can be added here. Press Next to continue. Choose the option Some or all clients will use DNS SRV records for automatic logon and check the box Use this server or pool to authenticate and redirect automatic client logon requests.
Press Next. Choose the SIP domain for automatic logon, confusedamused. Next. Select Do not configure for external access now and press Next. Review the configuration settings and press Next to begin the configuration. A success dialog will appear when it finishes. Check the box to view the log if desired, but press Finish to continue. That concludes Part 1 of this series.
Not very interesting yet, or hard to screw up either. The other parts should be much more interesting.
Microsoft Office Communications Server 2. R2 - Part IIIn my previous article I explained about OCS in general and we started with installing the OCS Front- end server. Now we will continue with the OCS Mediation Server and the OCS Edge Server to create connectivity to the Internet. Below an overview of the environment: Figure 1 Overview of environment. In the previous article we added the OCS 2. Standard Edition to the current environment so now we have: OCSDC, which is the domain controller for the ocs.
OCSIS, the ISA server which protects the corporate network; OCSSTD, the Front End server of OCS. Keep in mind that when you would like to use OCS on the internet your the domain must be public and not an internal domain such as . OCS Mediation server. The next server which we are going to install is the mediation server. The installation is not very hard but the configuration which needs to be done after the installation is a lot of work. So let’s start the setup on our mediation server called OCSMED. Once the setup is started select the “deploy other server roles” option which will give you some additional options.
As said earlier the setup is not that difficult because you don’t have to specify anything besides the directory where to install the files. When the setup is completed, activate the mediation server. During activation a service account and AD objects are created. The service account will be created only if necessary, in most cases it will exist because you already created it during the installation of the Front End server. In that case, provide the password which is used for the account and click next continue the setup. After a few minutes the setup is finished and will let you know if it succeeded or not.
The third step is to configure the mediation server. You can find the MMC snap- in in the administrative tools section on the Front End server. Figure 2 OCS Administrative tools. As you can see, both the Standard Edition Server and the Mediation server are listed in the administrative tools. You might experience problems getting the status of the services running on the mediation server. In this case you can modify the firewall settings and set exceptions for the Remote Event log and WMI application. Adding these acceptions can be done via the Networking and Sharing Center and then select the option Windows Firewall.
This will open a new Window which gives you the option to Allow a program or feature through Windows Firewall. In the list of programs and features you will find both the Remote Event log and Windows management Instrumentation (WMI) option, add an exception for these to only for the domain column. Refresh the view in the administrative tools and you will be able to see the correct status.
You may think you’re ready now, but when you have a look at the status of the Office Communications Mediation service you will see that it hasn’t started yet. This is normal behavior as we didn’t have configured the mediation server. Configuration needs to be performed before you can start the service. Configuring is divided in two parts: the Forest voice properties and the mediation server. We will start with the Forest voice part because some things we configure here are needed to configure the mediation server. Let’s start with an overview of what we need to configure: Location profiles; Phone Usage; Policy; Routes. Location profiles.
Each location profile contains a set of normalization rules. These rules are used to translate regular phone numbers to the E.
It’s recommended to create a location profile per geographic location. So for Thunderbirds Inc. The first three digits are the city you are calling to and always will start with a 0.
Since we need to dial a 0 to get an external line, it means that when we call to for example someone in Utrecht we need to dial 0. What all numbers have in common is that they will start with 0. OCS that it needs to apply the rule Amsterdam national when a user dials a number starting with 0. After the 0. 0 there are 9 numbers left, 2.
Using the $ sign we tell OCS that this is the end of the pattern. As told earlier all numbers need to be converted to the E. So in this example we need to add +3. After the country number simply add $1, this tells OCS to paste the number dialed after the country number and will make it E. Microsoft has a very useful site which explains how you can create these rules complete with some examples. Phone usages and Policy. The Phone usages and policy are related to each other.
Using phone usages and policies you can restrict users dialing specific numbers or limit calls to numbers outside your country, configuring them is mandatory. The default phone usage and the default policy which will be assigned to all users contains no restrictions. Policies can be set on Forest level or per user, depending on the rules of a company. Before you can create a policy you must create phone usages, once created phone usages can be added to the policies. Below an example of how you can configure them: Routing. Using routes you define how numbers are routed and which phone usages may use this route. With this tool you can test your complete configuration before bringing it in production.
The routehelper utility is installed in the Reskit directory below the Microsoft OCS directory. When opened, you will see the configuration which the utility retrieves from the Front End server.
Here you will find the location profile(s), normalization rules, policy/policies and phone usage(s) just configured. There are multiple options in these tools which can be divided in two parts: ad- hoc testing; testing using test cases.
Using the adhoc testing method you have three options: manual, can be used to test a policy works as you planned; user, can be used to test if the settings for a specific user are correct; gateway, can be used to test a specific gateway. For all these methods you will need to provide the information which you would like to test, for example, you would like to know how a call is routed when a user dials 0. So we fill this in in the dialed number field. The user is working in Amsterdam so we select the Amsterdam. We fill in the information on the custom tab and press the test button to start the simulation. Figure 3 Output Routehelper using ad- hoc testing.
Above you will see the result of the just performed test: the number will be normalized using the national normalization rule; the number will be routed to the PSTN via OCSMED which is our mediation server. The ad- hoc method is nice when you would like to test just a single number. But in test environments it can be very useful if you can run a bunch of tests which will test every possibility, for example: dial local numbers; dial national numbers; dial international numbers; dial the emergency number. These four options can be tested with different policies so you can also test if calls are blocked if a user is not permitted to call a number. If a call is blocked you will see the following message in the results box: Unable to route. Response code 4. 03 will be returned.
Before you can start testing using the test cases you will need to specify the following information: dialed number, the number which you like to dial; CN, client side normalization performs normalization on the client side before submitting it to the server; location profile, which location profile should be used; policy, which policy would you like to apply; expected translation, how is the number being normalized; expected phone usage, which phone usage will be used to place the call; expected route, which route is being used to route the call to their destination. In the example below we used the phone numbers: 0. As you can see the first line has only the local policy assigned to it, this should prevent the caller to dial a number outside of Amsterdam. That’s why the expected phone usage and expected route both are empty. Figure 4 Output Routehelper using test cases. When your testing is done and the tests have passed you can continue configuring the OCS Standard Edition server.
This can be done by getting the Front- end properties of the Standard Edition server and selecting the voice tab. Here you will need to select the default location profile which is used by the server. OK now everything is configured for voice we can return to the mediation server as it was not configured yet. Just get the properties of the mediation server and you will see this: Figure 5 Properties of mediation server. Ensure that you fill in the following field: communications server listening IP address, gateway listening IP address, default location profile. The A/V Edge Server can’t be configured yet because we don’t have one.
To finish the configuration using the administrative tools click the next hop connections. On this tab you will configure what the mediation server has to do when a call is placed to a number outside the OCS environment and which gateway handles incoming calls.
As we only have one mediation server this will be the gateway for incoming calls and when your press the arrow from the drop down menu you will only see one. Since R2 this can also be a Sip trunk delivered by a provider. Figure 6 OCS environment with direct SIP trunk. When everything is configured press the apply button to close the window and go back to the mediation server where we will perform the last step of configuring the mediation server. The last step is to create the certificate request and assigning it to the server.
The steps are exactly the same as for the Front- end so a quick recap: generate a . CSR file using the create new certificate task; send the . CSR file to the Certificate Authority; once the certificate is received from the Certificate Authority install the certificate using the “process an offline certificate request and import the certificate” option; ensure you get the message that the certificate is installed correctly. And now the time has come to start the mediation server services.