It doesn’t matter how many of these you send, nor how often, the conversation still times out after 15 minutes. However, the problem with this is that these INFO messages are seemingly not evaluated by the Lync client when determining active state. The initial idea was to periodically send the “user is typing” INFO message back to the client, to trick it into staying alive, as documented here. I need to look into this more, and work out why it’s not working for me when it does for everyone else ? Any feedback gratefully received! Mostly, BeginSendMessage is a protected method, so I can’t just call it on a new, accepted, conversations. ImCall.BeginSendMessage(.Info, contentType, messageBody, headers, OnMessageSent, imCall) If you search around on the internet you’ll find a method for keeping the conversation alive that involves sending a SIP INFO message to the client using this format: However, that’s not always possible or practical in all cases, which is why I’m suggesting this approach here. In an ideal world, UCMA bots would keep their own conversation tracking state, and would therefore be able to match up a new conversation with an existing, inactive, one by SIP address. If you do, then you will be responsible for terminating the conversation if it’s appropriate to do so before the client closes their chat window. You should think long and hard about deciding to override it like this. The Lync client terminating inactive conversations is a Good Thing, which will reduce server load and maintain performance. In this scenario, we need a way to keep the conversation alive – to trick the client into not terminating the conversation.Īside: before you break the rules you should what they are, and why they’re important. If the conversation has timed out before you reply then the bot may think that your reply is actually the start of a new conversation (as the ConversationID will be different) and respond unexpectedly. This can be a problem if the conversation you’re having is with a UCMA bot. If you then type another message it’ll still be sent, but under the hood, it’s being sent on a new conversation, with a different ConversationID. The conversation window doesn’t close, but the conversation is punctuated with a message telling you that the conversation has been stored in history. The Microsoft Lync client will automatically terminate instant message conversations if there has been no activity for 15 minutes. Warning: strpos(): Empty needle in D:\home\site\wwwroot\wp-includes\media.php on line 1608
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |