My Skype Room System v2 running version 3.0.16 are having join issues 50% of the time.
When you try to join a meeting, it will try and connect, after 5 seconds disconnects and sends me back to the main screen.
After collecting logs from the Front-End this was the only related error that I could I see:
USER-AGENT: UCCAPIMM/16.0.8315.3019 SkypeRoom/3.0.16.0 (Skype Room)
ms-client-diagnostics: 52095; reason="Media session terminated on internal client error
;UserType="Callee";MediaType="audio";MediaChanBlob="NetworkErr=no error,ErrTime=0,RTPSeq=0,SeqDelta=0,RTPTime=0,RTCPTime=3725374082120,TransptRecvErr=0x0,RecvErrTime=0,TransptSendErr=0x0,SendErrTime=0,InterfacesStall=0x0,InterfacesConnCheck=0x0,MediaTimeout=0,RtcpByeSent=0,RtcpByeRcvd=0,BlobVer=1";BaseAddress="10.81.6.69:24736";LocalAddress="10.81.6.69:31330";LocalSite="10.81.6.69:23250";RemoteAddress="10.1.255.15:51721";RemoteSite="10.1.255.15:51290";MediaEpBlob="ICEWarn=0x0,ICEWarnEx=0x0,LocalMR=198.90.11.49:54728,RemoteMR=198.90.11.49:50284,PortRange=1025:65000,LocalMRTCPPort=56794,RemoteMRTCPPort=50284,LocalLocation=2,RemoteLocation=2,FederationType=0,StunVer=2,CsntRqOut=0,CsntRqIn=0,CsntRspOut=0,CsntRspIn=0,Interfaces=0x2,BaseInterface=0x2,Protocol=0,LocalInterface=0x2,LocalAddrType=0,RemoteAddrType=0,IceRole=1,RtpRtcpMux=1,AllocationTimeInMs=226,FirstHopRTTInMs=3,TransportBytesSent=355,TransportPktsSent=11,IceConnCheckStatus=4,PrelimConnChecksSucceeded=0,IceInitTS=3725374081444,ContactSrvMs=166,AllocFinMs=226,FinalAnsRcvMs=483,ConnChksStartTimeMs=484,FirstPathMs=566,UseCndChksStartTimeMs=566,ReinviteSntMs=626,AckReinviteRcvMs=680,BlobGenTime=3725374082129,MediaDllVersion=6.0.8968.273,BlobVer=1";MediaMgrBlob="MrDnsE=avedge.domain.org,MrResE=0,MrErrE=11001,MrBgnE=37253740814345392,MrEndE=37253740814411520,MrDnsI=skypeedgepool.domain.org,MrResI=1,MrErrI=0,MrBgnI=37253740814345184,MrEndI=37253740814352504,MrDnsCacheReadAttempt=0,BlobVer=1"
I am able to replicate this issue after upgrading my other Skype Room System's to version 3.0.16
I have attempted to reboot the device without any luck. I have not seen anything from Microsoft recognizing this issue. Is anyone else experiencing this or have any advice?
