codesalot.com

Here are the service records needed to use the Tandberg VCS:

_h323ls._udp.company.com      srv     1 0 1719 vcs-e.company.com.
_h323cs._tcp.company.com      srv     1 0 1720 vcs-e.company.com.
_sip._udp.company.com              srv     0 0 5060 vcs-e.company.com.
_sip._tcp.company.com               srv     0 0 5060 vcs-e.company.com.
_sip._tls.company.com                 srv     0 0 5061 vcs-e.company.com.
_sips._tls.company.com               srv     0 0 5061 vcs-e.company.com.
_sips._tcp.company.com             srv     0 0 5061 vcs-e.company.com.

There should also be an a-record pointing to the vcs express. (in this example, vcs-e.company.com)

Also, should anyone ever need it, here are the ports that an endpoint needs opened outbound if it is registering directly to a VCS express:

TCP/2776 (Q931/H245 for external traversal endpoints)
UDP/2776 (RTP Media from external traversal endpoints)
UDP/2777 (RTCP Media control traffic from external traversal endpoints)
UDP/1719 (H323 RAS signaling from gatekeepers/VCSes and traversal endpoints)
TCP/1720 (Q931/H.225 call connect signaling)

UDP/5060 (SIP signaling)
TCP/5060 (SIP signaling)
TLS/5061 (Encrypted SIP signaling)

The OCS 2007 R2 Web scheduler is now available

http://www.microsoft.com/downloads/details.aspx?FamilyID=6d6848ec-e7d6-41f4-82d9-5bed3526fcbd&displaylang=en

“Web Scheduler is a 64-bit tool for Microsoft Office Communications Server 2007 R2. It provides a Web-based alternative to the add-in for the Microsoft Outlook messaging and collaboration client for the purpose of scheduling a meeting using Office Communications Server 2007 R2. It also provides a browser-based conference management experience that includes operations such as:

• Scheduling a new Live Meeting conference or conference call.
• Viewing and modifying details of an existing conference.
• Listing all existing user schedules of a Microsoft Office conference.
• Deleting an existing conference.
• Sending an e-mail invitation to conference participants by using a configured SMTP mail server.
• Joining an existing conference.”

I need to lab it before I can say anything about it, but it seems like a great addition to the family! Needs to be installed on the same IIS server as the OCS 2007 R2 web components.

The @DrRez Twitter team (http://twitter.com/DrRez) is compiling a list of all OCS/UC blogs on the net, and are publising it on the Communications Server Team blog! Great work guys!

http://communicationsserverteam.com/archive/2009/08/11/550.aspx

To be able to add Movi2 endpoints to phonebooks on systems registered in TMS, TMS should automagically create an external source and a provisioning phonebook when the provisioning key is installed on the system. If this for some reason does not happen, here’s how to add one: (or to verify that the phonebook was installed correctly)

In TMS, go to: Phone Book > Manage External Source

If there is an external source there that is called “Provisioning Source”, chances are that the phone book was installed correctly. If not, add a new external source and select “TANDBERG Provisioning Directory” as source type.

The rest of the fields should be like this:

With this setup, movi users are added to the phone book on the format “<firstname> <lastname> <provisioningprofile>”. I will try some different settings to see if I can filter and change the format in the phonebook. I will add this in a later post.

After this, create a new phonebook and connect it to the new external source.

Source: Tandberg Deployment guide: Provisioning. february 2009

This post was not written by me, but by my excellent colleague Ståle. Kudos! Pay his blog a visit ^^

TI

—

Commands to install the necessary prerequisites for OCS 2007 R2 on Windows Server 2008

Front End on Windows Server 2008
Servermanagercmd.exe -install web-windows-auth web-mgmt-compat web-mgmt-console web-http-logging msmq-server msmq-directory powershell was-process-model was-config-apis rsat-addc

Installs the following components:

• [Web-Windows-Auth] – Windows Authentication
• [Web-Mgmt-Compat] – IIS 6 Management Compatibility
• [MSMQ-Server] – Message Queuing Server
• [MSMQ-Directory] – Directory Service Integration
• [RSAT-ADDC] – Active Directory Domain Controller Tools
• [WAS-Process-Model] – Process Model
• [WAS-Config-APIs] – Configuration APIs
• [Web-Mgmt-Console] – IIS Management Console
• [Web-Http-Logging] – HTTP Logging
• [PowerShell] – Windows PowerShell

The last 3 in the list are not required, but they are highly recommended. IIS 7.0 Management Console is IMHO much easier to use than the IIS 6.0 version. The logging tools often come in handy when troubleshooting OCS IIS issues and PowerShell makes working with OCS WMI values a piece of cake.

Monitoring Server on Windows Server 2008
Servermanagercmd.exe -install msmq-server msmq-directory

Installs the following components:

• [MSMQ-Server] – Message Queuing Server
• [MSMQ-Directory] – Directory Service Integration

CWA Server on Windows Server 2008
Servermanagercmd.exe -install web-windows-auth web-mgmt-compat web-mgmt-console web-http-logging

Installs the following components:

• [Web-Windows-Auth] – Windows Authentication
• [Web-Mgmt-Compat] – IIS 6 Management Compatibility
• [Web-Mgmt-Console] – IIS Management Console
• [Web-Http-Logging] – HTTP Logging

Mediation Server on Windows Server 2008
Servermanagercmd.exe -install rsat-addc

Installs the following components:

• [RSAT-ADDC] – Active Directory Domain Controller Tools

Post used as a reference for this post

http://waveformation.com/2009/06/02/installing-ocs-2007-r2-prerequisites-on-windows-server-2008/

I just upgraded the server from 256 MB RAM to 512Mb. Hopefully that will solve the swap issues that has made the site be very slow.

I’ve been off on vacation for the last few weeks, and I haven’t exactly updated during that time

But now I’m back and hopefully we’ll see regular updates with UC goodies in the time coming.