SfB On-Prem
5 TopicsSkype for Business Server with Teams for Collaboration
Hi community, A client will deploy Sfb Server on premises soon, but only wants collaboration features from Teams. I would like to know if there is a way to have Skype for Business Server (on-prem) and use Teams ONLY for collaboration, a sort of SfB with Teams collaboration coexistence mode, where SfB is hosted on prem. Regards,2KViews0likes4CommentsGeneral Skype user's IM message does not appear for SFB user
Hi All, We have enabled consumer Skype federation via PIC provisioning for our on premise SFB server 2015 standard deployment. I am able to search a general Skype user from my SFB client and able to add the contact. Also, the general Skype user is able to receive the request and accept it. When having an IM session, the messages sent by SFB user is received by the general Skype user. But when the general Skype user sends or replies back to the SFB user, the message is not received by the SFB user. Also another thing noticed is that the general Skype user's presence shows as still updating in the SFB client. Any thoughts??780Views0likes1CommentSFB for Mac unable to initiate chat when external
SFB for Mac unable to initiate chat when external This only happens on the Mac client. Mobile clients can initiate chat just fine Tested on 16.16.91 and 16.16.102, both on OSX 10.13.3 High Sierra TMG 2010 SP2 as Reverse Proxy. (Does not happen on F5 LTM Reverse Proxy) 2015 Server March 2018 CU enterprise pool with HLB FE and no directors 2018-04-05 00:34:17.112 0000700008ecd000 INFO TRANSPORT TransportUtilityFunctions.cpp:1109 <ReceivedResponse> POST https://pubdnswebsvchostname.pubdnssipdomain.com/ucwa/v1/applications/414177410848/communication/messagingInvitations?continueContext=%257b%2522Subject%2522%253a%2522 Conversation%2bwith%2bfirst%2blast%2522%252c%2522RemoteParticipantUri%2522%253a%2522sip%253afirstlast%2540pubdnssipdomain.com%2522%252c%2522ThreadId%2522%253a%2522 AdOxgmD0pQLvOpJAR5WGZetrbWrbPA%253d%253d%2522%252c%2522Importance%2522%253a0%252c%2522ExchangeItemId%2522%253a%2522AAMkADI4NmRiMTIyLWI0MDYtNGZiMi1 hNmQzLWNlOTIyYWEyNjFiMQBGAAAAAADVEcEtCRAhQKE5JW5nz8w7BwBxiLxEbDAZT7M5zOieUBQ8AAACw1yXAABxiLxEbDAZT7M5zOieUBQ8AABX%252fj0HAAA%253d%2522%257d Request Id: 0x7f835b483d70 HttpHeader:Cache-Control no-cache HttpHeader:Connection close HttpHeader:Content-Length 2033 HttpHeader:Content-Type text/html HttpHeader:Pragma no-cache HttpHeader:StatusCode 500 HttpHeader:User-Agent SfBForMac/16.16.91.0000 (Mac OSX 10.13.3) <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML dir=ltr><HEAD><TITLE>The page cannot be displayed</TITLE> <STYLE id=L_defaultr_1>A:link { FONT: 8pt/11pt verdana; COLOR: #ff0000 } A:visited { FONT: 8pt/11pt verdana; COLOR: #4e4e4e } </STYLE> <META content=NOINDEX name=ROBOTS> <META http-equiv=Content-Type content="text-html; charset=UTF-8"> <META content="MSHTML 5.50.4522.1800" name=GENERATOR></HEAD> <BODY bgColor=#ffffff> <TABLE cellSpacing=5 cellPadding=3 width=410> <TBODY> <TR> <TD id=L_defaultr_0 valign=middle align=left width=360> <H1 id=L_defaultr_2 style="FONT: 13pt/15pt verdana; COLOR: #000000"><ID id=L_defaultr_3><!--Problem-->The page cannot be displayed </ID></H1></TD></TR> <TR> <TD width=400 colSpan=2><FONT id=L_defaultr_4 style="FONT: 8pt/11pt verdana; COLOR: #000000"><ID id=L_defaultr_5><B>Explanation: </B>There is a problem with the page you are trying to reach and it cannot be displayed.</ID></FONT></TD></TR> <TR> <TD width=400 colSpan=2><FONT id=L_defaultr_6 style="FONT: 8pt/11pt verdana; COLOR: #000000"> <HR color=#c0c0c0 noShade> <P id=L_defaultr_7><B>Try the following:</B></P> <UL> <LI id=L_defaultr_8><B>Refresh page:</B> Search for the page again by clicking the Refresh button. The timeout may have occurred due to Internet congestion. <LI id=L_defaultr_9><B>Check spelling:</B> Check that you typed the Web page address correctly. The address may have been mistyped. <LI id=L_defaultr_10><B>Access from a link:</B> If there is a link to the page you are looking for, try accessing the page from that link. </UL> <HR color=#c0c0c0 noShade> <P id=L_defaultr_11>Technical Information (for support personnel)</P> <UL> <LI id=L_defaultr_12>Error Code: 500 Internal Server Error. The request was rejected by the HTTP filter. Contact the server administrator. (12217) </UL></FONT></TD></TR></TBODY></TABLE></BODY></HTML> </ReceivedResponse> 2018-04-05 00:34:17.112 0000700008ecd000 INFO TRANSPORT CUcwaRequestBase.cpp:227 Got a failed status code in the http header. Error = E_InternalServerError (E2-3-13), Request = 2018-04-05 00:34:17.113 0000700008ecd000 INFO TRANSPORT CUcwaRequestBase.cpp:411 Re-mapping non-UCWA error code E_InternalServerError (E2-3-13) to E_UcwaUnavailable 2018-04-05 00:34:17.113 0000700008ecd000 INFO TRANSPORT CHttpRequestProcessor.cpp:240 Sending event to main thread for request(0x0x7f835b483d70)SolvedBRK2004 - Learn from large scale Skype for Business Voice deployments
It was clear, from the packed room at the “Learn from large scale Skype for Business Enterprise Voice deployments” session, that a lot of Microsoft Ignite attendees were interested in catching a glimpse into how different companies were tackling their Skype for Business Enterprise Voice deployments. Francois then discussed how Microsoft turned Skype for Business into a proven, mature, complete and comprehensive PBX replacement solution: “I am confident that we can succeed at any PBX replacement project; PBX replacement projects are complex and can be difficult, but I have yet to encounter a solution where the combination of Microsoft and our ecosystem was not able to meet the customer’s needs”. In support of that claim, Francois asked four companies to describe their Large Enterprise Voice Deployments. It was clear when these companies shared the details, that they were all convinced they had made the right choice with Skype for Business Server. Still, these customers presented complex use cases, much beyond the basic and simple “white collar” use case; these deployments were far from straightforward. Tremendous work and dedication were all a part of each of these deployments, and each was unique in its own way.