Microsoft SRS sign in to SkyeForBusiness after migrating user to Cloud (Sign in.. to Skype problem)

Occasional Visitor


We have MS SRS rooms (Logitech Group Conferance with Smartdock with SRS software) running both SfB and Teams Meetings.

This worked flowlessly for a long time now, but couple of weeks ago, out IT dep. migrated users to Cloud.
Now after migration the Teams meetings works fine, but the SfB meetins don't.

We get a purple bar on top of the screen with Sign In messege.
As ou can see in the picture below, Teams meetings forks as they schould, but we canæt Join Skype For Business meetings.

We are going to shut down Skyope in about a year, until then we need to be abble to use both SfB and Teams meetings.

Any one has any idea on whare is the problem?


2 Replies

Hi @Martin_Adam_Martinsen

this could have multiple root causes but lets try out following.

Is SIP proxy address same as UPN and same as Primary SMTP? This proved to me as best practice. 

Also check if this attribute on user is setup same way msRTCSIP-PrimaryUserAddress . Sometimes it is missed and hence making issue with login of Skype account. 

Is the Skype user now migrated to S4b Online and Teams user is in Islands mode or Teams Only mode? If Teams Only mode then make sure there is still Skype Online license assigned to MTR account.  

For Hybrid account coming from on-premise and being migrated to Online you should see InterpretedUserType as Hybrid OnlineSfbUser.  Check if Cs-GetCsOnlineUser is really with RegistrarPool set to sippool*** and is not pointing still to on-premise s4b. I would say hybrid setup is in that manner tricky one. 

Is the SIP domain Auto Discovery DNS resolution pointing to on-premise or S4B Online environment? 

@Martin_Adam_Martinsen Some good suggestions above.

I would also suggest checking it's not network related, are there any corporate firewalls or proxies on it's way to the internet? Can you connect it to a simple network with direct internet access, maybe a guest network and see if it works from there. My guess is that some proxy in the path is requesting authentication.