Monday, December 19, 2011

Exchange OWA and Lync Integration Issue: Multiple SIP ProxyAddresses

I was recently troubleshooting a pesky Lync-OWA integration issue where some users could see the integration and some couldn’t.  I was getting the dreaded:

“Instant Messaging isn’t available right now.  The Contact List will appear when the service becomes available.”

Lync-OWA - OWA error - markup

First thoughts were that because it was only happening to a subset of users, maybe the Exchange CAS server that they were accessing through was having issues.  I was able to force a working connection through that same CAS server without issue for other users, so I knew that the CAS was healthy.

Next step was to investigate the user mailbox since it was very consistent as to whether a user worked or didn’t work.  After comparing two users (one working, one not working), I noticed that the non-working user had multiple SIP addresses defined in the Email Addresses Tab:

Lync-OWA - Exch properties dual SIP - markup

Turns out that in this particular implementation, a Resource Forest model was being used for both Exchange and Lync.  The tools used for user synchronization were copying the current user’s SIP proxy addresses to the new Resource Forest and when the users were getting enabled for Lync, multiple SIP addresses were being applied to the “proxyAddresses” AD attribute:

Lync-OWA - Proxy Addresses

After removing the extra SIP proxy addresses from the resource forest proxyAddresses AD attribute, Lync-OWA integration was restored:

Lync-OWA - OWA working

The SIP entries in the proxyAddresses AD attribute should only contain the SIP address that matches the SIP address that Lync is using.

31 comments:

  1. We should be so lucky as to have proxy SIP addresses. :-)

    ReplyDelete
  2. Great job. I was wondering for a while.

    ReplyDelete
  3. Thanks for this article. I know it's a little old at this point, but I need a way to enforce the sip: entry in the proxyAddresses attribute. Do you know if it should "always be the same as the value of the msRTCSIP-PrimaryUserAddress attribute? Let me know what you think. Thanks.

    ReplyDelete
  4. Hello! This post couldn't have been better! Reading this post reminded me of my good old roommate! He always talked about it. I will forward this page to him. I'm pretty sure he'll read it well. Thanks for sharing!Textile Mill

    ReplyDelete
  5. I haven't checked in here for a while because I thought it was getting boring, but the last few posts are good quality so i guess I'll add you back to my daily bloglist. บาคาร่า

    ReplyDelete
  6. http://howdouc.blogspot.com/2011/07/lync-topology-validator.html

    ReplyDelete
  7. Hi.....
    There is only one exception, this is the CWA integration for Exchange OWA. ... the Lync SIP Domain identically with the default Exchange EMail Domain.
    You are also read more Business Loan Interest Rates

    ReplyDelete
  8. If you are into the field of graphic designing, you are probably aware of the two most common techniques professionals use: Image Masking and Clipping Path. The demand for these two services is on the rise in the outsourcing industry. Which one of the two is more valuable? In our experience, image masking has more value than clipping path. Let us find out how. Clipping Path

    ReplyDelete
  9. UFAC4, a website giving away 200 free credits, just apply, no need to invest a lot, apply for free with UEFA C4, the number 1 website in Thailand.

    ReplyDelete
  10. You make so many great points here that I read your article a couple of times. Your views are in accordance with my own for the most part. This is great content for your readers. 안전놀이터


    ReplyDelete
  11. Pgslot แหล่งรวมสล็อตสุดฮิต โบนัสแตกง่าย 100 % แจก free เครดิต PG เพียงแค่สมัครสมาชิก สามารถเข้าเล่นได้ตลอด 24 ชั่วโมง เล่นง่าย ได้เงินจริง ฝากถอนด้วยระบบออโต้

    ReplyDelete
  12. Thank you for being a source of positivity and wisdom. For more inspiration, check out this profile Emotional Intelligence Test. It also has information on the Emotional Intelligence Test.

    ReplyDelete