A Unified Communication Blog
Get Adobe Flash player

Monthly Archives: January 2008

When running the validation wizard on the Access Edge server, you get this error:

Problem:

DNS Resolution failure: No DNS SRV records corresponding to _sipfederationtls._tcp.domain.com were found for this domainSuggested Resolution: Verify that the domain name is correct and that the DNS SRV record _sipfederationtls._tcp.domain.com exists for this domain.

Warning[0x43FC200C] Not all checks were successful

Solution:

Verify the external DNS settings (http://it-proknowledge.blogspot.com/2008/01/troubleshooting-ocs-federation.html)

If you are using internal DNS servers on the Access Edge server, the problem might be that the public DNS zone (Domain) is also owned by the internal DNS servers, and therefore the DNS lookup is done against the Internal DNS zone. Use the SRVLOOKUP tool (explained in the article in the link above) from a computer outside the network.

UPDATE:

Heres some steps to do when troubleshooting this problem.

1. From the Access Edge server, ping your external sip domain name (sip.domain.com). You should be able to resolve the name to an IP address. (ping response is not needed)

2. From the Access Edge server, use the SRVLOOKUP tool, explained in item 1, in the above linked articel. The response from the SRVLOOKUP tool, should be you sip domain (sip.domain.com)

Both these test shoul be positive. If not, there is a DNS issue.

I have found that best practise for DNS on Access Edge servers, is to build a seperate DNS server:

  1. Install DNS Server from Add- Remove Windows Components
  2. Configure the DNS server to use root hints (this should be default)
  3. Configure the firewall protecting the Access Edge server from the Internet, to allow DNS outbound
  4. Verify connectivity by using the tool in the DNS Server MMC snap-in
  5. Configure the servers NIC to use the new DNS server as primary DNS

This way, you should be able to have clean DNS resolution on the Access Edge server.

Please let me know if you have any relevant issues

Regards,
Rasmus

When running the validation wizard on the Access Edge server, you get this error:

Problem:

DNS Resolution failure: No DNS SRV records corresponding to _sipfederationtls._tcp.domain.com were found for this domainSuggested Resolution: Verify that the domain name is correct and that the DNS SRV record _sipfederationtls._tcp.domain.com exists for this domain.

Warning[0x43FC200C] Not all checks were successful

Solution:

Verify the external DNS settings (http://it-proknowledge.blogspot.com/2008/01/troubleshooting-ocs-federation.html)

If you are using internal DNS servers on the Access Edge server, the problem might be that the public DNS zone (Domain) is also owned by the internal DNS servers, and therefore the DNS lookup is done against the Internal DNS zone. Use the SRVLOOKUP tool (explained in the article in the link above) from a computer outside the network.

UPDATE:

Heres some steps to do when troubleshooting this problem.

1. From the Access Edge server, ping your external sip domain name (sip.domain.com). You should be able to resolve the name to an IP address. (ping response is not needed)

2. From the Access Edge server, use the SRVLOOKUP tool, explained in item 1, in the above linked articel. The response from the SRVLOOKUP tool, should be you sip domain (sip.domain.com)

Both these test shoul be positive. If not, there is a DNS issue.

I have found that best practise for DNS on Access Edge servers, is to build a seperate DNS server:

  1. Install DNS Server from Add- Remove Windows Components
  2. Configure the DNS server to use root hints (this should be default)
  3. Configure the firewall protecting the Access Edge server from the Internet, to allow DNS outbound
  4. Verify connectivity by using the tool in the DNS Server MMC snap-in
  5. Configure the servers NIC to use the new DNS server as primary DNS

This way, you should be able to have clean DNS resolution on the Access Edge server.

Please let me know if you have any relevant issues

Regards,
Rasmus

Here are some steps for Troubleshooting OCS federation:

1. Verify DNS SRV records
Use the ResKit tool srvlookup to test your DNS SRV records. Use the command “srvlookup domain.com -v
The output should point to you SIP record (example: sip.domain.com)

2. OCS validation
Use the Validate Edge Server tool, on the Access Edge server, to locate any errors in the configuration

3. Verify certificate
Validate and verify the sip certificate on the Access Edge server. This must be a public and valid certificate for Federation to work. If you know your federation partner, you can exchange certificates, but this should only be done in test.

4. Verify connectivity
Test your firewall configuration by accessing port 5061. This can be done by telnet to your server from the Internet. (example: “telnet sip.domain.com 5061″) This should result in a blank screen (connection)

5. Contact your federation partner
Make sure that your federation partner has Open Federation, or that your domain is allowed to federate to them. This is probably the most common cause of problems

Q: Is Office Communicator 2007 a licensed product?

A: Yes, unlike Exchange CAL that gives you access to Outlook, Office Communicator i a separate product, not covered by the Office Communications Server 2007 CAL license.

This means that you have to purchase these license separate. If you already have one of these Office Suites, the software license is included in the suite:

Microsoft Office Pro Plus 2007
Office Enterprise 2007

The QoE server is a monitoring tool that watches you Enterprise Voice deployment, and generates reports in stad-alone console or to Operations Manager. Its a complicated product, that takes just as much time deploying as the OCS itself. Nevertheless, if you plan a voice deployment in an enterprise enviroment, you should consider this server together with Operations Manager 2007

MS Wrote:

Monitoring Server
The QoE Monitoring Server provides the information that you need in order to better understand the media quality that your users are experiencing in your Office Communications Server 2007 deployment. The QoE Monitoring Server focuses on the media quality at the endpoints and provides a near real-time alerting and health model and includes standard reports that you can use as soon as you are up and running. With the QoE Monitoring Server in your deployment, you can do the following:

  • Gather statistics on media quality at individual locations or based on a grouping of subnets.
  • Proactively monitor and troubleshoot media quality of experience issues.
  • Perform diagnostics in response to VoIP user complaints.
  • View trends that can help you with post-deployment growth and measure results against the service level agreement.

Get it here:

Doc: http://www.microsoft.com/downloads/details.aspx?familyid=9ED29D74-3391-4902-BF2C-6757410F3335&displaylang=en

Doc:http://www.microsoft.com/downloads/details.aspx?familyid=AAFEA9A7-EBF0-4171-B33F-4D9F0C135334&displaylang=en

Software: http://www.microsoft.com/downloads/details.aspx?FamilyID=09115944-625f-460b-b09c-51e3c96e9f7e&displaylang=en

Have Fun!

Language Availability

OCS 2007 Server will be available in the following language offerings:

English, French, Italian, German, Spanish, Japanese, Chinese Simplified, Chinese Traditional, Korean, Brazilian Portuguese

Office Communicator will be available in the OCS Server languages and also in the following localized languages:

Chinese Hong Kong, Arabic, Danish, Dutch, Finnish, Hebrew, Hindi, Norwegian, Polish, Russian, Swedish, Bulgarian, Czech, Croatian, Estonian, Greek, Hungarian, Latvian, Lithuanian, Portuguese (port), Romanian, Serbian, Slovak, Slovenian, Thai, Turkish, Ukrainian

Here is a list of vendors offering antivirus for Office communications Server 2007:

-
-
-

Well, in fact i have spent some time on this, and i didn’t find anyone yet offering this solution.

But,

There is a Antigen product called Antigen for Instant Messaging, but there is only support for LCS 2003 & 2005. Microsoft i currently branding Antigen for IM to match the Forefront product family but does not yet support OCS, but there should be plans for a release sometime in 2009. The new product will be called Microsoft Forefront Security for Office Communications Server, but we will have to wait
(More: http://www.microsoft.com/forefront/prodinfo/roadmap/default.mspx)

Trend Micro also have products for the LCS versions, and i´m waiting for them to get back to me about when they will support OCS (i’ll update later)

Symantec is the same story, only support for old versions.

Update:

Trend Micro reports back that there will be support for OCS 2007 in there “Instant Messaging Security” product, that will be released in Q3 2008.

Update (July 2008):
http://it-proknowledge.blogspot.com/2008/07/forefront-security-for-office.html

Office Communications Server 2007 VoIP Test Set

Microsoft Office Communications Server 2007 VoIP Test Set enables you to simulate a SIP endpoint to test connectivity.

Its actually i very cool tool for testing the setup of your Enterprise Voice solution. Its easy to use, and to logfiles generated i usefull for troubleshooting you configuration.

Heres some info from MS:

Overview
VoIP Test Set for Office Communications Server 2007 supports emulation of a SIP endpoint to test connectivity. Emulation options include the following:
Client emulation – To emulate a Microsoft Office Communicator client, you specify a SIP-enabled user account to register with Office Communications Server. This can be useful for troubleshooting problems with incoming or outgoing Enterprise Voice calls. For example, an Office Communications Server engineer can use the tool in client emulation mode to quickly change user location profile information and validate that outbound routing is properly configured.
Server emulation – You can use VoIP Test Set to emulate a Mediation Server or a gateway. To emulate a server, you specify the IP address, port number, and other settings of the server to be emulated. This can be useful for emulating components during the setup of the Office Communications Server 2007 infrastructure to verify the functionality of components that have already been deployed. For example, you might use the tool to receive and make calls directly from an IP/PSTN gateway to ensure that it is completely functional before deploying the complete Office Communications Server 2007 infrastructure.

http://www.microsoft.com/downloads/details.aspx?FamilyID=7b6ab4f3-2949-4e97-856e-9c4ae323c75a&displaylang=en

Here’s a list of the “missing” features, bugs and more, found in the Mobile Communicator (MoCo) 2007 edition. The list will be updated as i find issues, and MS releases fixes.

Bugs and Errors:

  • IM conversations are cut off when you place or receive a phone call. (This might be Windows Mobile “feature”)

Missing features:

  • No presence information for “on the phone” when using GSM phone for Voice conversation.
  • No Outlook integration to Contacts.
  • No “conversation history” log in Outlook for IM conversations.
Search

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 75 other subscribers

Follow me on Twitter