Martin Gibney - Microsoft Teams

We came across an issue with a segmented network with multiple VLANs separated by numerous firewalls. Each VLAN was considered a separate LAN. Rules must be opened on the firewalls to allow video and audio traffic to work inter-VLAN. By default ports 1024-65535 TCP/UDP are used which is pretty much all of them bar 1023 ports - this is a big hole. So instead we can limit the ports used from the client and then on the firewall just open up these ports - minimum 20 ports. Media Port Range This section describes the minimum media port allocation requirements for the client and server. The default UDP/TCP port range used by the Office Communicator 2007 client is 1024-65535. The Real Time Media Communications stack in Office Communicator 2007 allocates the media port dynamically in this range. In order to maintain an adequate level of performance, you can specify a smaller port range for Office Communications Server to use. To control the specific range of ports that need to be open on

Server installation media: Office Communications Server 2007 R2 Trial  Office Communications Server 2007 R2 Group Chat server Office Communications Server 2007 R2 UCMA 2.0 Speech Language Packs Office Communications Server 2007 R2 Resource Kit Tools Server post-RTM updates: Communications Server 2007 Audio Video Conferencing Server: February 2009 (contains KB 961563 and KB 961564) KB 961564: The state in the conference is inconsistent with the state in the roster in the Audio Video Multipoint Conferencing Unit in Communications Server 2007 KB 961563: Participants who use Communicator 2007 R2 or Live Meeting 2007 hear short noise spurts through the Audio Video Multipoint Conferencing Unit in multipoint calls Desktop client installation media: Office Communicator 2007 R2 Trial Office Communications Server 2007 R2 Attendant Office Communications Server 2007 R2 Group Chat client Messenger for Mac 7.0.2 Mobile client installation media: Office Communicator Mobile 2007 R2 (SmartPh

Microsoft has release a line of updates for its Office Communications Server 2007 R2 server roles. The updates are called "April 2009" but is just relased to Microsoft Update today. It is recomended to update all your OCS 2007 R2 servers asap. The recomended way of updating is to use Microsoft Update Update for Application Host 967832  ( http://support.microsoft.com/kb/967832/ ) Description of the update package for Communications Server 2007 R2 Application Host: April 2009 Update for Application Sharing Server 967833  ( http://support.microsoft.com/kb/967833/ ) Description of the update package for Communications Server 2007 R2, Application Sharing Server: April 2009 Update for Administration Tools 968280  ( http://support.microsoft.com/kb/968280/ ) Description of the update package for Communications Server 2007 R2, Administration Tools: April 2009 Update for Core Components 967827  ( http://support.microsoft.com/kb/967827/ ) Description of the update package for Co

So…. Microsoft released a document covering virtualization support for the specified roles:   Role Supported Supported features Unsupported features Enterprise front-end server Yes Presence, IM Enterprise Voice, audio/video Standard Edition Server No     IM Conferencing Server Yes IM Conferencing   Access Edge Server Yes Remote Access Federation, Public IM Connectivity   SQL Server back-end server Yes Office Communications Server Backend   Group Chat Channel Server Yes Channel Server   Group Chat Look-up Server Yes Channel and Load balancing management   Group Chat back-end server Yes Group Chat database   Group Chat Compliance Server Yes Compliance   Group Chat Compliance back-end server Yes Compliance database   Director No     Audio/Video Conferencing Server No     Application Sharing Conferenc

Dial In conferencing On the R2 Console, from a forest level, Right click >> Properties >> Conferencing Attendant Properties Under Access Phone Numbers Click ADD Select the following details:   Click Ok then under Regions click ADD and select location profile from list which we set up earlier. Press Select under assigned numbers and move the number we have across to the configured side. Click OK and we are done. Now we need to set up our own conferencing ID and PIN numbers, we do this by going to our CWA server with /dialin after it: https://mgocscwa/dialin Enter new pin Our example PIN: 14789 And that's it from the OCS side, a number obviously has to be provisioned on the PBX to accpet incoming calls and to pass them off to the OCS Dial In conferencing server.

Set up user settings on OCS Under the pool name , right click on the users folder (to do all users or on each one for individual settings) and configure users: For Voice we hit next four (4) times, then on the following screen: Enable enterprise voice as above and click Next . Next for each individual user we need to configure the following details, simply right click on the user and configure user (This can be done in AD or through scripting either) The Sign-in name should be SIP: followed by SAMaccount name. Also hit Configure (Telephony Settings:) and set up as follows – Line URI will be tel: then the full phone number with +xxx Server URI will be simply sip: Location profile we can select from the list which we created in a previous step. Now restart all services including mediation server and front end services and log in to the clients: In this setup we log in using:- 3013@mgdomain.ie User: mgdomain\user1 Password: Passw0rd

Section 3: Deploy Other Server Roles Mediation server Instal l Let’s install the Mediation server now on MGOCSMED01 Click on Deploy Other Servers In here click on Deploy Mediation Server. Step 1: Install Files For Mediation Server. In step 1 click on Install . Accept the license agreement and click OK . Select location for install files and click OK. Step 2: Activate Mediation Server Click Run beside step 2. Click Next on splash screen. Use RTCComponentService for service account and click Next. Review settings and click Next. These warnings OK as we have not enabled logging: Review Log and click Finish . STEP 3: Manual configuration of mediation serve r We now need to configure the settings for the mediation server. On the R2 console software (Admin tools): Now at the forest level >> Right Click >> Properties >> Voice Properties In Location Profiles we ADD Now we name our location and give it a description: Now we need to ADD N