DirectAccess and Communications Server 2007 R2
Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.
The direct scoop about DirectAccess and Office Communications Server 2007 R2-read on to find out.
Author: Rob Pittfield
Publication date: March 2010
Product version: Office Communications Server 2007 R2
We’ve recently seen some questions on Twitter and a few other sources regarding support for Office Communications Server 2007 R2 working via DirectAccess. (For details about DirectAccess, see https://go.microsoft.com/fwlink/?LinkId=147551.) DirectAccess works only with IPv6. For details, see the section "Overview of Direct Access" in the Windows Server 2008 R2 Technical Overview at https://go.microsoft.com/fwlink/?LinkId=152315. Communications Server 2007 R2 and Communicator 2007 R2 support only IPv4. For details, see Networking Protocols Support at https://go.microsoft.com/fwlink/?LinkId=184539.
For Communications Server 2007 R2, we generally recommend the use of an Access Edge Server for remote users. We use TLS and SRTP for encryption of the SIP and media traffic respectively.
For details about how we use TLS in Office Communications Server, see https://go.microsoft.com/fwlink/?LinkId=184537.
For details about our SRTP implementation, see https://go.microsoft.com/fwlink/?LinkId=184540.
Microsoft recommends using an Access Edge Server instead of DirectAccess or other remote VPN-like technologies because of the network traffic overhead and processing latency that these technologies create. Audio/video and other media traffic are incredibly sensitive to any latency, and adding additional encryption (IPSec in DirectAccess) can cause delays in sending and receiving media traffic. There can also be delays due to the additional processing on the client side that is required for encrypting and decrypting the traffic that travels through the DirectAccess network path. For the best possible performance, we recommend that you add as little additional overhead as possible.
For details about IPSec and Communications Server 2007 R2, see the Microsoft Office Communications Server 2007 R2 Troubleshooting guide at https://go.microsoft.com/fwlink/?LinkID=154163.
If you are still interested in DirectAccess and Communications Server 2007 R2, see UAG and DirectAccess at https://go.microsoft.com/fwlink/?LinkId=159955. This information explains how to extend the DirectAccess functionality to allow the use of IPv4 applications.
Additional Information
To learn more, check out the following:
DirectAccess, https://go.microsoft.com/fwlink/?LinkId=147551
Microsoft Office Communications Server 2007 R2 Troubleshooting guide, https://go.microsoft.com/fwlink/?LinkID=154163
UAG and DirectAccess, https://go.microsoft.com/fwlink/?LinkId=159955
Communications Server Resources
Visit the Communications Server main page at https://go.microsoft.com/fwlink/?LinkId=132607.
View the complete Communications Server documentation library at https://go.microsoft.com/fwlink/?LinkId=132106.
Download the Communications Server content as Word documents at https://go.microsoft.com/fwlink/?LinkId=133609.
Download the Communications Server documentation as a compiled help file at https://go.microsoft.com/fwlink/?LinkId=160355. (Scroll down to the Additional Information section and download OCSDocumentation.chm.)
Read weekly articles for Communications Server IT professionals on NextHop at https://go.microsoft.com/fwlink/?LinkId=181907.
Read weekly articles for Communications Server developers on UCode at https://go.microsoft.com/fwlink/?LinkId=177892.
Follow tweets from the Communications Server team at https://go.microsoft.com/fwlink/?LinkId=167909.
We Want to Hear from You
To give us feedback about this article or to propose a topic for an article, e-mail us at NextHop@microsoft.com.
You can also send us a tweet at https://www.twitter.com/DrRez.