On Premise
3 TopicsSDN Interface Setup/Configuration Recommendations
First published on TECHNET on Nov 28, 2017 Author: Steve SchiemannIntroduction and Background:This writing is intended for customers currently implementing or planning for the Software Defined Networking Interface (SDN) implementation for Lync/Skype for Business on-premise servers.2.2KViews0likes0CommentsMigrate Hybrid to Online with no on-premise environment
I've ran into an issue whilst migrating to Office 365, specifically Skype. There was previously an on-premise Skype setup, Office 365 was procured and the migration started. A number of pilot users were moved across who now show as 'Online' whilst everyone else shows as 'Online (hybrid)'. Through miscommunication and a complete misunderstanding, the on-premise Skype environment was fully decommissioned, including all DNS changes etc. within a week whilst i wasn't in the office. This means we have a bunch of users still showing as 'Online (hybrid)' and every subsequent new user also has a status of hybrid. Is there a way to force the existing users and any future new user to be 'Online' only?743Views0likes0CommentsCCE ON-Premise users voicemail fails after the outage yesterday
I created a ticket with Microsoft already but I figured maybe someone can help in the meantime as Microsoft doesn't appear to be responding very quickly on this matter. After yesterday's widespread outage for our Skype for Business Online users, we are now having issues with our S4B-CCE On-Prem users and voicemail. When someone calls an On-Prem user they can reach the user but they never make it to their voicemail greeting. I grabbed some of the sip messages and this is a snippet from what I'm seeing. ms-diagnostics: 23;source="MedServer.domain.local";reason="Call failed to establish due to a media connectivity failure when one endpoint is internal and the other is remote";component="MediationServer";Exception="Proxy side ICE connectivity check failed.";ICEWarningFlags="BaseAddress="{localipaddress1}:54784";LocalSite="{localipaddress1}:50070";RemoteSite="{remoteipaddress1}:5446";MediaEpBlob="ICEWarn=0x412a,ICEWarnEx=0x0,LocalMR={localipaddress2}:3478,RemoteMR={remoteipaddress1}:51816,PortRange=49152:57500,RemoteMRTCPPort=51816,LocalLocation=2,RemoteLocation=1,FederationType=0,StunVer=0,CsntRqOut=0,CsntRqIn=0,CsntRspOut=0,CsntRspIn=0,Interfaces=0x2,BaseInterface=0x2,IceRole=1,RtpRtcpMux=0,AllocationTimeInMs=210,FirstHopRTTInMs=0,TransportBytesSent=6387,TransportPktsSent=219,IceConnCheckStatus=5,PrelimConnChecksSucceeded=0,IceInitTS=3728302164984,ContactSrvMs=204,AllocFinMs=254,FinalAnsRcvMs=4422,ReinviteSntMs=14925,BlobGenTime=3728302179909,MediaDllVersion=6.0.8953.265,BlobVer=1"" ms-diagnostics-public: 23;reason="Call failed to establish due to a media connectivity failure when one endpoint is internal and the other is remote";component="MediationServer";Exception="Proxy side ICE connectivity check failed." ms-endpoint-location-data: NetworkScope;ms-media-location-type=intranet IP addresses have been removed for security reasons.1KViews0likes0Comments