MPOP and Auto Accept Feature for Skype for Business Application

%3CLINGO-SUB%20id%3D%22lingo-sub-54700%22%20slang%3D%22en-US%22%3EMPOP%20and%20Auto%20Accept%20Feature%20for%20Skype%20for%20Business%20Application%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54700%22%20slang%3D%22en-US%22%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3EAlways%20there%20has%20been%20a%20lot%20of%20confusion%20wherein%20we%20have%20the%20users%20signed-in%20to%20%3C%2FFONT%3E%3CFONT%20face%3D%22Calibri%22%3E%3CSTRONG%3EMPOP%20(Multiple%20Point%20of%20Presence)%3C%2FSTRONG%3E%3C%2FFONT%3E%3CFONT%20face%3D%22Calibri%22%3Ewhere%20would%20the%20IM%20Messages%20go%20and%20where%20would%20the%20IM%20Messages%20be%20automatically%20accepted.%20So%20please%20find%20the%20below%20table%20below%20based%20on%20my%20research%20with%20Skype%20for%20Business%20Desktop%20Client%20and%20Skype%20for%20Business%20Mobile%20Device.%20This%20remains%20the%20same%20irrespective%20of%20the%20Mobile%20Devices.%20%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FDIV%3E%3CTABLE%20border%3D%220%22%20cellspacing%3D%220%22%20cellpadding%3D%220%22%3E%3CTBODY%3E%3CTR%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3E%3CSTRONG%3EDesktop%20Client%20%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3E%3CSTRONG%3EMobile%20Client%20%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3E%3CSTRONG%3EPreferred%20End%20Point%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3EAvailable%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3EAvailable%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3E%3CSTRONG%3EDesktop%20Client%20%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3EInactive%20%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3EAvailable%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3E%3CSTRONG%3EMobile%20Client%20%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3EAvailable%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3EInactive%20%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3E%3CSTRONG%3EDesktop%20Client%20%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3EInactive%20%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3EInactive%20%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3E%3CSTRONG%3EDesktop%20Client%20%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3EAway%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3EInactive%20%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3E%3CSTRONG%3EMobile%20Client%20%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3EOffline%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3EInactive%20%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3CTD%3E%3CDIV%20align%3D%22center%22%3E%3CFONT%20color%3D%22black%22%20face%3D%22Calibri%22%3E%3CSTRONG%3EMobile%20Client%20%3C%2FSTRONG%3E%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3EAdditionally%20in%20case%20we%20are%20troubleshooting%20Lync%20or%20Skype%20for%20Business%20Mobile%20Feature%20issues%20we%20need%20to%20check%20if%20the%20Conversation%20History%20is%20not%20getting%20saved.%20We%20need%20to%20collect%20the%20following%20logging%20in%20the%20Skype%20for%20Business%202015%20Server.%20The%20logs%20are%20as%20follows%3A-%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3EComponents%3A-%20%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3EUCWA%20%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3ESIP%20Stack%20%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3ES4%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3EWeb%20Infrastructure%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3ECollaboration%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3ELevel%3A-%20All%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3EFlags%3A-%20All%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3EIn%20the%20MPOP%20Scenario%20from%20the%20logs%20we%20need%20to%20identify%20if%20the%20Invite%20is%20going%20to%20all%20the%20Mobile%20Device%20or%20the%20Desktop%20Client%20we%20can%20pull%20the%20information%20from%20the%20logs%20and%20differentiate%20using%20the%20port%20number.%20For%20the%20desktop%20client%20the%20Invite%20will%20always%20go%20on%20the%20Port%20Number%205088%20and%20in%20case%20of%20MPOP%20the%20Invite%20gets%20Forked%20to%20both%20the%20desktop%20client%20and%20the%20Mobile%20Client%20as%20well.%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3ETo%20confirm%20if%20the%20user%20account%20is%20logged%20into%20MPOP%20we%20can%20confirm%20the%20same%20from%20the%20above%20Skype%20for%20Business%202015%20Server%20logs%20and%20we%20need%20to%20look%20for%20error%20SIP%20error%20486%20Busy%20Here%20coming%20from%20the%20desktop%20client.%20In%20case%20if%20we%20need%20to%20search%20it%20from%20the%20Desktop%20Client%20Logs%20we%20need%20to%20understand%20the%20same%20from%20the%20invite%20being%20sent%20to%20the%20user%20account%20during%20an%20IM%20Conversation%20.%20In%20the%20invite%20in%20the%20Via%20Route%20we%20would%20get%20the%20IP%20Address%20of%20the%20Front%20End%20Server%20and%20Term%20Branch%20with%20the%20value%20set%20as%20True.%20In%20case%20the%20value%20for%20Branch%20is%20True%20then%20it%20means%20that%20the%20user%20account%20is%20signed-in%20to%20the%20MPOP.%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3ESince%20we%20have%20the%20Auto%20Accept%20Feature%20in%20the%20Skype%20for%20Business%202015%20Server%20and%20Exchange%20Server%202103%20and%20above%20this%20also%20means%20that%20after%2025%20seconds%20the%20Skype%20for%20Business%20Application%20whether%20on%20Mobile%20Device%20or%20Desktop%20Client.%20This%20also%20means%20that%20the%20Push%20Notification%20Feature%20would%20not%20be%20required%20for%20Skype%20for%20Business%20Mobile%20Devices%20as%20the%20messages%20are%20getting%20auto%20accepted.%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FDIV%3E%3CDIV%3E%3CFONT%20face%3D%22Calibri%22%3ELet%E2%80%99s%20take%20the%20most%20weird%20example%3A%20In%20case%20we%20have%20the%20User%20A%20signed%20in%20to%20both%20Skype%20for%20Business%20Desktop%20Client%20and%20Skype%20for%20Business%20Mobile%20Client%20with%20the%20latest%20update%20and%20the%20user%20being%20hosted%20on%20Skype%20for%20Business%202015%20and%20Exchange%202013%20or%20above.%20Now%20User%20B%20sends%20an%20IM%20message%20to%20User%20A%20and%20the%20user%20is%20not%20at%20his%20desk%20and%20also%20away%20from%20the%20Mobile%20Device.%20Now%20if%20the%20User%20B%20sent%20the%20IM%20to%20User%20A%20and%20before%20the%20IM%20gets%20Auto%20Accepted%20on%20the%20Mobile%20Device%20if%20the%20User%20A%20unlocks%20logs%20back%20into%20the%20Desktop%20system%20the%20IM%20Message%20would%20get%20accepted%20on%20the%20desktop%20client%20instead%20of%20the%20Mobile%20Device.%20%3C%2FFONT%3E%3CFONT%20face%3D%22Calibri%22%3E%26nbsp%3B%3C%2FFONT%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-54700%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EInstant%20Messaging%20%26amp%3B%20Presence%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-54803%22%20slang%3D%22en-US%22%3ERe%3A%20MPOP%20and%20Auto%20Accept%20Feature%20for%20Skype%20for%20Business%20Application%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-54803%22%20slang%3D%22en-US%22%3E%3CP%3ETL%3ADR%20version%20-%20it's%20overcomplicated%20and%20Microsoft%20needs%20to%20finally%20sort%20this%20out.%20Especially%20the%20conversation%20history%20issue.%20Borrow%20a%20thing%20or%20two%20from%20the%20commercial%20version%2C%20you%20borrowed%20the%20name%20after%20all%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20the%20detailed%20description!%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor
Always there has been a lot of confusion wherein we have the users signed-in to MPOP (Multiple Point of Presence) where would the IM Messages go and where would the IM Messages be automatically accepted. So please find the below table below based on my research with Skype for Business Desktop Client and Skype for Business Mobile Device. This remains the same irrespective of the Mobile Devices.
 
Desktop Client
Mobile Client
Preferred End Point
Available
Available
Desktop Client
Inactive
Available
Mobile Client
Available
Inactive
Desktop Client
Inactive
Inactive
Desktop Client
Away
Inactive
Mobile Client
Offline
Inactive
Mobile Client
 
 
Additionally in case we are troubleshooting Lync or Skype for Business Mobile Feature issues we need to check if the Conversation History is not getting saved. We need to collect the following logging in the Skype for Business 2015 Server. The logs are as follows:-
 
Components:-
UCWA
SIP Stack
S4
Web Infrastructure
Collaboration
 
Level:- All
Flags:- All
 
In the MPOP Scenario from the logs we need to identify if the Invite is going to all the Mobile Device or the Desktop Client we can pull the information from the logs and differentiate using the port number. For the desktop client the Invite will always go on the Port Number 5088 and in case of MPOP the Invite gets Forked to both the desktop client and the Mobile Client as well.
 
To confirm if the user account is logged into MPOP we can confirm the same from the above Skype for Business 2015 Server logs and we need to look for error SIP error 486 Busy Here coming from the desktop client. In case if we need to search it from the Desktop Client Logs we need to understand the same from the invite being sent to the user account during an IM Conversation . In the invite in the Via Route we would get the IP Address of the Front End Server and Term Branch with the value set as True. In case the value for Branch is True then it means that the user account is signed-in to the MPOP.
 
Since we have the Auto Accept Feature in the Skype for Business 2015 Server and Exchange Server 2103 and above this also means that after 25 seconds the Skype for Business Application whether on Mobile Device or Desktop Client. This also means that the Push Notification Feature would not be required for Skype for Business Mobile Devices as the messages are getting auto accepted.
 
Let’s take the most weird example: In case we have the User A signed in to both Skype for Business Desktop Client and Skype for Business Mobile Client with the latest update and the user being hosted on Skype for Business 2015 and Exchange 2013 or above. Now User B sends an IM message to User A and the user is not at his desk and also away from the Mobile Device. Now if the User B sent the IM to User A and before the IM gets Auto Accepted on the Mobile Device if the User A unlocks logs back into the Desktop system the IM Message would get accepted on the desktop client instead of the Mobile Device.  
1 Reply

TL:DR version - it's overcomplicated and Microsoft needs to finally sort this out. Especially the conversation history issue. Borrow a thing or two from the commercial version, you borrowed the name after all :)

 

Thank you for the detailed description! :)