Posts

Showing posts from August, 2016

Multiple Phone Numbers for Skype for Business Users

Image
As we know, Skype for Business only supports a maximum 2 phone numbers per user. The LineURI and the PrivateLineURI. Note: At point of writing this article, this option is on available for On-Premise users (09. Aug. 2016) While the PrivateLineURI is not aware of the current user status. If you are calling the Private Number while you are "do not disturb" the phone call will ring at your endpoint.   How do we work around this typical PBX feature with Skype for Business? This is proposed solution is a little bit a hassle to configure, but works perfectly. Skype for Business has two services/ features: Unassigned Number Announcements if we combine those services in a manner supporting a multi number concept for users, we have the same feature available like every traditional PBX. The process workflow explains what we need to configure. You can create multiple Unassigned Number with the same Announcement. This will give you the option have beside the LineU

Remove Server from Topology Error EventID 1034

Image
Once more I ran into the issue with the say EventID 1034. Source : LS File Transfer Agent Service EventID: 1034 General: Skype for Business Server 2015, File Transfer Agent service encountered an error while accessing a file share and will continuously attempt to access this file share until this issue is resolved. While this condition persists, replication to replica machines might not occur. Can't watch SfBFrontEnd.domain.local Cause: Possible issues with file share permission.   This issue while removing a Server from the Topology is not related to any permission issues, rather it is related to DeleteReplicas. This occurs, if anything with the server removal was not working as expected, even if the removal and the bootstrapper process ran well. You should verify first the: Get-CsManagementStoreReplicationStatus As you see the replication is working fine and we only have a Polycom RMX which did have the do not replication option set in the topology. Next

Skype for Business Cloud Connector with Sonus @MicrosoftDE und @Westcon

Hallo zusammen, mit Microsoft, Westcon und Sonus veranstalten wir eine super Event zu Office 365 E5 Skype for Business Online und Cloud Connector. Bitte fleißig anmelden. http://de.ucc.westcon.com/content/events/sonus-microsoft-365-e5-cloudpbx-roadshow Wann?   Wo ? 13.09.2016   Microsoft Hamburg, Gassstraße 6a, Gebäude M, 22761 Hamburg 14.09.2016   Microsoft Berlin, Unter den Linden 17, 10117 Berlin 20.09.2016   Microsoft Köln, Holzmarkt 2a, 50676 Köln 21.09.2016   Microsoft München, Walter-Gropius-Straße 1-3:,  80807 München Programm 11:30 – 12:15 Registrierung und Lunch 12:15 – 12:25 Begrüßung durch Sonus 12:25 – 12:55 Microsoft: Office 365 E5, CloudPBX 12:55 – 13:10 Sonus: SBC und Cloud Link Lösungen  13:10 – 13:30 Westcon: MVP über Cloud Connector Edition mit Sonus Appliance 13:30 – 13:45 Pause 13:45 – 14:15 Sonus: Migration PBX nach CloudPBX 14:15 – 14:45 Westcon: End-2-End Sales Motion (mit Skype for Business ECO System) und Sonus Partner Programm 14:

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