Skype Room System v2 Meeting Join Fail

%3CLINGO-SUB%20id%3D%22lingo-sub-151024%22%20slang%3D%22en-US%22%3ESkype%20Room%20System%20v2%20Meeting%20Join%20Fail%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-151024%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20Skype%20Room%20System%20v2%20running%20version%203.0.16%20are%20having%20join%20issues%2050%25%20of%20the%20time.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhen%20you%20try%20to%20join%20a%20meeting%2C%20it%20will%20try%20and%20connect%2C%20after%205%20seconds%20disconnects%20and%20sends%20me%20back%20to%20the%20main%20screen.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAfter%20collecting%20logs%20from%20the%20Front-End%20this%20was%20the%20only%20related%20error%20that%20I%20could%20I%20see%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EUSER-AGENT%3A%26nbsp%3B%3C%2FSTRONG%3EUCCAPIMM%2F16.0.8315.3019%20SkypeRoom%2F3.0.16.0%20(Skype%20Room)%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3Ems-client-diagnostics%3A%2052095%3B%20reason%3D%22Media%20session%20terminated%20on%20internal%20client%20error%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3BUserType%3D%22Callee%22%3BMediaType%3D%22audio%22%3BMediaChanBlob%3D%22NetworkErr%3Dno%20error%2CErrTime%3D0%2CRTPSeq%3D0%2CSeqDelta%3D0%2CRTPTime%3D0%2CRTCPTime%3D3725374082120%2CTransptRecvErr%3D0x0%2CRecvErrTime%3D0%2CTransptSendErr%3D0x0%2CSendErrTime%3D0%2CInterfacesStall%3D0x0%2CInterfacesConnCheck%3D0x0%2CMediaTimeout%3D0%2CRtcpByeSent%3D0%2CRtcpByeRcvd%3D0%2CBlobVer%3D1%22%3BBaseAddress%3D%2210.81.6.69%3A24736%22%3BLocalAddress%3D%2210.81.6.69%3A31330%22%3BLocalSite%3D%2210.81.6.69%3A23250%22%3BRemoteAddress%3D%2210.1.255.15%3A51721%22%3BRemoteSite%3D%2210.1.255.15%3A51290%22%3BMediaEpBlob%3D%22ICEWarn%3D0x0%2CICEWarnEx%3D0x0%2CLocalMR%3D198.90.11.49%3A54728%2CRemoteMR%3D198.90.11.49%3A50284%2CPortRange%3D1025%3A65000%2CLocalMRTCPPort%3D56794%2CRemoteMRTCPPort%3D50284%2CLocalLocation%3D2%2CRemoteLocation%3D2%2CFederationType%3D0%2CStunVer%3D2%2CCsntRqOut%3D0%2CCsntRqIn%3D0%2CCsntRspOut%3D0%2CCsntRspIn%3D0%2CInterfaces%3D0x2%2CBaseInterface%3D0x2%2CProtocol%3D0%2CLocalInterface%3D0x2%2CLocalAddrType%3D0%2CRemoteAddrType%3D0%2CIceRole%3D1%2CRtpRtcpMux%3D1%2CAllocationTimeInMs%3D226%2CFirstHopRTTInMs%3D3%2CTransportBytesSent%3D355%2CTransportPktsSent%3D11%2CIceConnCheckStatus%3D4%2CPrelimConnChecksSucceeded%3D0%2CIceInitTS%3D3725374081444%2CContactSrvMs%3D166%2CAllocFinMs%3D226%2CFinalAnsRcvMs%3D483%2CConnChksStartTimeMs%3D484%2CFirstPathMs%3D566%2CUseCndChksStartTimeMs%3D566%2CReinviteSntMs%3D626%2CAckReinviteRcvMs%3D680%2CBlobGenTime%3D3725374082129%2CMediaDllVersion%3D6.0.8968.273%2CBlobVer%3D1%22%3BMediaMgrBlob%3D%22MrDnsE%3Davedge.domain.org%2CMrResE%3D0%2CMrErrE%3D11001%2CMrBgnE%3D37253740814345392%2CMrEndE%3D37253740814411520%2CMrDnsI%3Dskypeedgepool.domain.org%2CMrResI%3D1%2CMrErrI%3D0%2CMrBgnI%3D37253740814345184%2CMrEndI%3D37253740814352504%2CMrDnsCacheReadAttempt%3D0%2CBlobVer%3D1%22%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20am%20able%20to%20replicate%20this%20issue%20after%20upgrading%20my%20other%20Skype%20Room%20System's%20to%20version%203.0.16%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20attempted%20to%20reboot%20the%20device%20without%20any%20luck.%20I%20have%20not%20seen%20anything%20from%20Microsoft%20recognizing%20this%20issue.%20Is%20anyone%20else%20experiencing%20this%20or%20have%20any%20advice%3F%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-151024%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EConferencing-Meeting%20Join%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESkype%20Room%20Systems%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-158724%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20v2%20Meeting%20Join%20Fail%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-158724%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Alexander%2C%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20checked%20the%20logs%20on%20the%20SRS%2C%20but%20unfortunately%20it%20is%20only%20limited%20to%205%20Event%20IDs%3A%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fmt797747.aspx%23Understand%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fmt797747.aspx%23Understand%3C%2FA%3E%20the%20log%20entries%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHowever%2C%20a%20few%20days%20ago%20Microsoft%20sent%20over%20an%20email%20saying%20they%20officially%20recognized%20this%20is%20as%20a%20bug%20and%20they%20are%20working%20on%20correcting%20it.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-158432%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20Room%20System%20v2%20Meeting%20Join%20Fail%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-158432%22%20slang%3D%22en-US%22%3E%3CP%3EHave%20you%20looked%20at%20the%20logs%20on%20the%20deivce%20itself%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

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? 

 

 

 

2 Replies

Have you looked at the logs on the deivce itself?

Hello Alexander, 

 

I have checked the logs on the SRS, but unfortunately it is only limited to 5 Event IDs: 

https://technet.microsoft.com/en-us/library/mt797747.aspx#Understand the log entries

 

However, a few days ago Microsoft sent over an email saying they officially recognized this is as a bug and they are working on correcting it.