locked
Communicator Issue -- Users not able to IM other specific users RRS feed

  • Question

  • We have an issue on our environment that has started recently where a few users are unable to IM other users.  This appears to be a random pattern of people, but always consistent for the users who have the trouble.  For example:

    User 1 unable to IM User 5 , User 5 works fine to IM everyone, User 2 Unable to IM user 4,  User 4 works fine Etc...

    Upon reviewing the Communicator-uccapi-0.uccapilog, we see the following:

    06/15/2010|08:23:48.720 A34:F58 INFO  :: Data Received - OCSPoolIP:5061 (To Local Address: User@Company.com:4118) 866 bytes:
    06/15/2010|08:23:48.720 A34:F58 INFO  :: SIP/2.0 481 Call Leg/Transaction Does Not Exist
    Proxy-Authentication-Info: Kerberos rspauth="602306092A864886F71201020201011100FFFFFFFF06DB56DAF8F1F5B43AE40A59909B469E", srand="5A695585", snum="265", opaque="54FF2E54", qop="auth", targetname="sip/Poolname", realm="SIP Communications Service"
    Via: SIP/2.0/TLS User@Company.com:4118;ms-received-port=4118;ms-received-cid=122300
    From: <sip:SendingUserSIP>;tag=e16a5bb5f2;epid=283aba661d
    To: <sip:RecipientUserSIP>;epid=aafa83773c;tag=7e5988d3fc
    Call-ID: 90187b7f00604c2985febf8e642f3ad8
    CSeq: 2 MESSAGE
    User-Agent: UCCAPI/3.5.6907.37 OC/3.5.6907.83 (Microsoft Office Communicator 2007 R2)
    Content-Length: 0
    ms-diagnostics: 1011;reason="Ms-Diagnostics header not provided by previous hop";source="poolname";Domain="domain.com";PeerServer=""
    06/15/2010|08:23:48.720 A34:F58 INFO  :: End of Data Received - OCSPoolIP:5061 (To Local Address: User@Company.com:4118) 866 bytes

    We have checked the IP Phone value on both the senders and the recipients, and it's not set.  There appears to be no commonality between the users that cannot receive, or those who cannot send.

    I have also reviewed the address book, and interestingly enough my primary pool is missing entries for these users(?).  I used the abserver dumpfile command to export the address book.

    Thanks!

    Tuesday, June 15, 2010 2:01 PM

Answers

  • We actually figured this out two days ago.  Apparently, the users in question had their email addresses placed on other active directory objects, groups.  This is what was causing the apparent routing issue.
    • Marked as answer by ScooterW Thursday, June 24, 2010 2:24 PM
    Thursday, June 24, 2010 2:24 PM

All replies

  • Can you check if there is anything that could drop the packet or not?
    Best Regards!
    Wednesday, June 16, 2010 6:47 AM
  • Hi, ScooterW ,updates?

    Would you also check whether the issues occurring on specific users or all users are experiencing this issue?


    Best Regards!
    Thursday, June 24, 2010 3:17 AM
  • We actually figured this out two days ago.  Apparently, the users in question had their email addresses placed on other active directory objects, groups.  This is what was causing the apparent routing issue.
    • Marked as answer by ScooterW Thursday, June 24, 2010 2:24 PM
    Thursday, June 24, 2010 2:24 PM
  • Can you clarify?
    Wednesday, January 5, 2011 11:23 PM