Solved

Cannot send to Office Communicator Client

Posted on 2009-05-12
3
2,117 Views
Last Modified: 2013-11-29
We are piloting Office Commincations Server 2007 R2, clients are using Office Communicator 2007 R2, all updates have been applied to both the client and server (as far as I can tell).  

I am having a problem with one user who cannot receive IMs intiated from other users, although they can initiate an IM conversation and recieve subsequent IMs back from the conversation participants.  A user trying to initiate a conversation with the problem user receives the message "<User> could not be reached and this message was not delivered: <message body>."  The user's status also goes from "Available" to "Presence Unknown" after 5-10 minutes of signing into the communicator client.

This is a single 2003 AD domain, no federation, and the user is connected to the LAN.  The user never has problems connecting to the OCS server or sending IMs to other users.

I have tried the following steps and tested each with the same results:
- Verified SIP Sign-in name
- Verified Enhanced Presence is enabled
- Tried different connection settings from Communicator client, including OCS server FQDN, OCS pool FQDN, TCP, and TLS
- Disabled user in Communications Server config, re-enabled
- Deleted user from Communications Server configuration, added back after AD replication takes place
- Had user sign in on a different workstation, which works fine for other users.

Thanks in advance!
0
Comment
Question by:ceaexperts
  • 2
3 Comments
 
LVL 15

Accepted Solution

by:
HayesJupe earned 500 total points
Comment Utility
best way to troubleshoot this is to create a debug log in the OCS 2007 R2 management console. Start logging, get the user to logon, try to send/recieve messages, then stop logging.
Then use the snooper.exe tool from the resource kit to help you sift through the logs and find the cause of your issue.
0
 

Author Comment

by:ceaexperts
Comment Utility
I was able to resolve this by turning on logging on my Communicator client, under the General options.
After enabling this, my Event Viewer showed the entry: "A SIP request made by Communicator failed in an unexpected manner (status code 80ef01f4)" when trying to send to the affected user. A quick web search found a few posts regarding invalid characters in the user's AD -> Telephones -> IP Phone field, which turned out to be my issue.
0
 

Author Closing Comment

by:ceaexperts
Comment Utility
Although I ended resolving this using the Communicator client logging, it looks like the Snooper tool is very helpful in tracking down these issues.  Thank you for the assistance.
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Suggested Solutions

Consider a situation when you deploy a seemingly harmless software package to your network without testing and therefore without fully knowing the implications of your actions. I was recently involved in just this situation when a corporate IT netwo…
The environment that this is running in is SCCM 2007 R2 running on a Windows 2008 R2 server. The PXE Distribution point is running on its own Windows 2008 R2 box. This is what Event viewer showed after trying to start the WDS service:  An erro…
Excel styles will make formatting consistent and let you apply and change formatting faster. In this tutorial, you'll learn how to use Excel's built-in styles, how to modify styles, and how to create your own. You'll also learn how to use your custo…
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now