Howdy,

We recently rolled out Lync to a new department and found an issue (option?) where missed conference emails are blank. I have some here in IT, that when they are invited to a conference, the conference invite is accepted automatically, and any missed conversation is included in the missed conference email. The behavior in this new area is that a conference invite appears in the toast notification, but if the invite is not accepted, the recepient is not included in the conversation, however, the intended recipient will eventually receive the "missed conference" email, but the body will be blank.

I'm trying to narrow down if this is an issue with the installation, or if it's a combination of options that includes something like privacy relationship.

Has anyone come across this?

(Please note that I'm referencing conference (group conversation). Missed conversation emails are working as they should.)

Hi,

As my understanding, all miss conference calls would go to Conversation History folder.  Conversations are represented as missed conversations only after they are written in the Conversation History folder stored in the Microsoft Exchange mailbox of the Lync user.  All missed IM and conference calls are written in the Conversation History folder by a Lync active end point, while the missed call logs are written by the Front End Server.  Missed conversations roam, and they are displayed on all Lync end points.

Please make sure EWS is working properly and the option with personal information manager in lync client->Personal has been selected correctly.

Thanks for your reply. I found I am confusing my terminology. When I said "conference", I believe I mean "group conversation." Am I correct in understanding that a conference is an audio/video meeting, whereas a group conversation is three or more people exchanging text-only messages?

If so, I may need to do more testing with our users having the trouble. I suspect one or more of them is using the conference feature to start group conversations which may be causing the trouble I described.

Okay,  I was finally able to witness an event.

A Lync 2010 Windows client user sends an instant message (group conversation) to several other Lync 2010 users (all using the Windows client). Some, not all, of the intended recipients see the toast notification appear for a brief moment, then disappear (no nice fade out after ~10-15 seconds). The group conversation does not appear in the Windows task bar. A "missed conversation" email is immediately written to their Outlook inbox. The email is blank.

We're having the same issue using Lync 2010.  I'm not sure if it's because the sending user closes their message before it has been fully sent to all users, but we have seen cases where recipients do not receive a notification at all because the sender does not wait until the message is sent to all endpoints before leaving the conversation.

We used to use XMPP for our internal messaging and since all messages were handled by the server, our users got used to sending out group IMs without having to wait for everyone to receive the message before closing the window, esspecially in cases of quick announcements that didn't require a response.  The other feature they were used to is the ability for IMs to be stored on the server until an endpoint for that user was available for delivery.  With Lync, if the user isn't online the message is lost.  We've had to retrain our staff on both of these concepts and some haven't grasped the concept yet so this may be our problem.

It seems to me like Lync should keep track of delivery at the server level and send conversation messages to exchange in the case of delivery failure, but for now that's just wishfull thinking.