Posts

Showing posts with the label skype for business

Understanding Cloud Connector Edition (CCE) Network Design

Image
Understanding Cloud Connector Edition (CCE) Network CCE virtual machines First I like to introduce the internal VM structure to CCE again. We will from here understand better the requirement for virtual networks. We require network connection to the internet, the SBC and the virtual machines themselves. PICTURE: CCE Network 00.png   The Cloud Connector Edition is built with 4 virtual machines, a subset from a typical on-premise deployment. Domain Controller: supporting the internal CCE PKI and the authentication for “CCE domain joint” machines. Single NIC (internal VM only) CMS: contains the subset for the Skype for Business relevant minimalistic Topology Single NIC (internal VM only) Mediation Server: Codec transcoding unit for the Session Boarder Controller, between the RTP data stream from Office 365 and Skype for Business Clients to the SBC. Single NIC (internal VM and SBC on same subnet only) NOTE: The Mediation likewise the on-premise setup...

Busy on Busy guide for Skype for Business

Image
Some general statements to Busy on Busy: It is only available for user homed on Skype for Business Pool (SE or EE) CU3 must be installed on all Pool Members Not working for user homed on Lync 2013 or SBA. Using Busy on Busy requires a Voice Policy in Skype for Business (Global, Sites or User) Setting Voice Policy in Control Panel: http://lyncuc.blogspot.de/2016/12/enabling-busy-on-busy-within-control.html IMPORTANT: The Busy On Busy feature has an timeout of 12min . If the user got disconnected for a call, e.g he was on disconnected from the network, which can be happened with a mobile phone or if you got connected via Wifi, the busy signal stay active for 12min before it will be reset. As well remember the Busy Options cannot be configured by any user themselves. This is only an administrative task. Busy on Busy supports only three different types: - BusyOnBusy: If the user is on an active call, the busy signal will be played to the caller. - VoiceMailOn...

500 - Internal Server Error - Skype for Business Mobility

500 - Internal Server Error - Skype for Business Mobility this is very common error, which can be related to some of the following issue: wrong internal/ external certificate firewall ports 4443-443 not assigned correctly firewall does a packet inspection and change (reverse proxy) load balancer issue, wrong persistence, wrong ticket validity period,... Direct Server Return (DRS) issue on load balancer I could continue with this list. But there is one issue not discussed on the blog side yet. if you see a Error 500 in the IIS LogFile, showing the /AUTH module, possibly the IIS has a wrong configuration and it is not related to any of the other common (caused) issues. /webticket/webticketservice.svc/auth - 4443 - 192.168.10.50 COP 500 0 0 3037 As we know, the client first receive the JSON WebService link information. Then try to access the WebTicketService and will receive an ERROR 401, because the authentication wasn't done yet. It now tries to connect to the w...

Skype for Business Topology Support with Office 365, Cloud Connector Edition, Cloud PBX and PSTN Calling

Topology support in Office 365 with Skype for Business A frequently asked question is the support for the different topologies. Later in this document I also provide a generic overview about a possible migration path towards one or the other topology. The rudimentary described supported topologies are the ONLY possible setups. There is not possible and supported way in combining any of those topologies! On-Premise without any Office 365 connectivity This is typically a solution, where you don’t own an Office 365 “E” Plan. Therefore, you are not entitled using any of the Office 365 features. Same is valid, if you own only an Exchange Online Plan, whereby none of the Skype for Business Online Services are subject to be used.   On-Premise with Office 365 connectivity (Federation to Office 365 and Cloud PBX and PSTN CALLING SERVICE) This is the only scenario, where users are hosted either in Office 365 and some users stay SfB enabled On-Premise. Meanin...

Changing Sales Cycle to long-term customer engagement with Office 365 E Plans

Understanding the end to end sales motion Office 365 with E plans (thomas poett) from Thomas Poett

Broadcast Meeting Web View and App View

Image
(v 1.0, 4th Nov 2015) Today I'm digging deeper into Skype for Business Broadcast Meeting. As its not all about video, the presentation side is important. how to make PowerPoint visible to the audience. Also it is easy to handle? How is the user experience when a user joins via a webbrowser? Simply said it is excellent. If you need to understand how setting up a meeting, please follow my last blog article: http://lyncuc.blogspot.com/2015/11/broadcast-meetings-in-skype-for-business.html   Have a look and I explain what to do and how to use it. If you join as an authenticated user and being part of the Presenter Team, the browser checks the Desktop App and will ask you for access permission.   As usual, if you click the "Monitor" button, it give you the option uploading a PowerPoint file and als manage the content. Once it is uploaded it is show in the preview windows, where you can also use the PowerPoint Tools e.g. the marker or others. ...

Wildcard Certificate Support in Skype for Business

Coming back to the most common question about certificates in Skype for Business and Lync Server. Can we use Wildcard Certificates in Skype for Business or Lync Server? Simple answer is: YESNO First lets have a look into a certificate: A Certificate has a Common Name (CN) and Subject Alternative Names (SAN) A classic wildcard certificate is a certificate where the CN look like: CN=*.domain.com In Skype for Business the main reason for certificate use is TLS/MTLS data encryption and the other point it the server authentication/ validation. Skype for Business is using the Common Name CN for authentication/ validation trusts. Only if a server with in the Topology or for Federation purposes presents a valid certificate with its matching Common Name (CN) the entire traffic can be used with TLS/MTLS. Therefor we understand a CN identifier as FQDN of the Server or the Pool is RECOMMENDED! A valid SAN Wildcard certificate could look like this: CN   = POOL01.DO...