05-24-2019 01:56 AM - edited 05-24-2019 06:49 AM
05-24-2019 01:56 AM - edited 05-24-2019 06:49 AM
Using a Logitech kit with a Surface Pro unit in it.
After setting everything up, the calendar is available, but the status att he top is stuck at "signing in". It keeps spinning the dotted progress circle, and once in a while it'll gray out the "new meeting" button for half a second as if it fails and restarts the login attempt.
The issue is occuring using a pre-existing account/ room mailbox. I tried creating a new one for troubleshooting and that works without issues. That shows the setup is OK, but we need to user a pre-existing account which already has lots of meetings in the calendar.
I tried signing in the troublesome account on another Teams Room System of the same model in another site, and that showed the same issue.
Both mailboxes have SIP/SMTP addresses set, passwords and mailbox type set, can be logged in at portal.office365.com okay. Licensing is correct (same for both accounts).
The environment is a 365 hybrid with account migrated from local to 365, synced from local AD.
It seems the problem is account related. What could be the issue? I have compared the old and new accounts, but can't find the difference. Clarification: New account works, but I want to use the old one which has the desired name and calendar contents.
05-24-2019 06:49 AMSolution
This problem turned out to be caused by an incorrectly set msRTCSIP-PrimaryUserAddress on the user account in local AD.
Apparently the logon to mailbox/calendar worked but not to Teams.
After correcting this, the problem went away.
09-04-2019 06:44 AM
Hi, we have the same Issue here and found until now no solution.
The Conference Room User can login to the Teams App without any Problems, only with SRS it does not work.
I checked also our msRTCSIP-PrimaryUserAddress on the user account in local AD and the entry seems to be ok with sip:User.firstname.lastname@example.org
What did you had to correct exactly?
09-05-2019 01:02 AM - edited 09-05-2019 01:03 AM
Yesterday I found that having special characters (in our case ( ) , - )in the display name of the room account causes problem with signing in to Teams in TRS. Actually it signs in and everything is working but the status bar at the top with Signing in... is still there and also the display name is not displayed in the upper right corner as it usually is on the control panel.
09-11-2019 04:50 AM
@Par Linderoth I'm having the exact same issue. I am seeing a sign in for 'Skype for Business Online' and 'Office 365 Exchange Online' in Azure AD. All functionality is available on the Lenovo ThinkSmart 500 that I'm using but I continue to see ' Signing in... ' at the top of the screen.
I too have used an existing room account that originated as Cloud Only. It has since been synced.
Did you ever resolve the issue. I've also checked for the above attribute and it doesn't exist in AD.
Any help would be most appreciated!
09-11-2019 05:06 AM
whatever's causing this problem, it's not an account issue from my point of view.
No matter which user I try, it doesn't work with any of them to logon in SRS Teams.
I have also created a new Conference Room User, which can also log in without problems, except for SRS Teams........
I opened a support ticket at Microsoft the day before yesterday, but I haven't heard much yet.
After all, I sent all logs and now I wait until it was evaluated and I hear something from the support again. Will keep you updated if i get any solution
09-11-2019 05:22 AM
I've just miraculously managed to get this to work!
It may be the Smart Hub being sporadic as it has been so far but if you login to Exchange Online Admin Centre and view the e-mail addresses for your room. Does the SIP address match the primary SMTP address / UserPrincipalName?
I was reviewing this article which gave me the idea to check it:
Mine did not. The room name contained a dash. As there was no SIP address specified in EOP it appears that it was automatically generated to contain a dash. This apparently doesn't work well with SRS.
I'm continuing to test this but I can confirm the 'Signing in....' message has now disappeared! =]
09-11-2019 06:43 AM
your solution gave me hope because we had different primary SMTP and SIP addresses.
I've corrected that now . Primary SMTP is now the same as the SIP address and UPN
Unfortunately SRS is still not able to login with teams......
09-11-2019 07:16 AM
@Kaya Denec Are you sure that the sign in to Teams isn't working in SRS/TRS? For us everything in regards to Teams is working (creating a new meeting for example) but the Signing in... info is still there. I have tried to update primary SMTP but will give it a few hours to replicate properly prior to signing in again.
09-11-2019 07:31 AM
Still have the "couldn't sign in to Teams" Error, sign in to Skype is not the Problem, only sign in to Teams still failed.
I created a Teams Meeting for this Room User and in Fact i see on SRS the scheduled Teams Meeting, but there is no Join Meeting Option available to start the Teams Meeting. Skype Meetings are working fine....
SMTP is updated and already synced. The Information are correct now (SIP, UPN,Primary)
09-12-2019 06:31 AM
Ok i got the problem in our enviroment, the problem seems to be the federated ConferenceRoom User who cant sign in to teams. I created a new user on o365 only, with the login adress email@example.com instead of xx@ourDomain.com and then it works.
so i will re-create our Conference Room User and then it should work
10-11-2019 04:01 AM
I have the same issue.
2 different system (Logitech SmartDock + Lenovo ThinkSmart Hub500) each with their unique meeting room account. Microsoft Teams Room version 4.1.22 on both systems. No AAD connect, so pure cloud accounts. SIP and SMTP addresses match.
I have the "Signing in" bar on top of the screen on both systems - but the meeting part actually works.
10-11-2019 04:08 AM
@Ulrik Andreassen I have an ongoing ticket with MS and the last info I got was that SIP and UPN must be the same. I have updated SIP in Exchange and is currently waiting for it to replicate to Teams to see if it works. The replication has still not happened 24 hours later
10-11-2019 06:48 AM
10-14-2019 02:58 AM
@Par LinderothSure I have Modern Auth enabled for Skype fB online on my tenant.
But have you ever seen a Modern Auth prompt on a SRS device?
Yes, I could see under sign-ins in my Azure AD, that the authentication from my SRS device was being blocked.
10-28-2019 02:30 PM
01-21-2020 12:19 AM
We have also just encountered this problem - setting the SIP and UPN to same value has resolved it - thanks to you all for contributing to this thread :)
03-06-2020 05:02 AM
Hi, we have noticed the same issue on several of of our devices.
Suddendly, we were not able to sign in to Teams, which worked perfectly all the time before.
We noticed that the time was not correct. We fixed clock and activated 'internet time synchronization' and after reboot the device was able to log in again.
Checking time zones and time could resolve the issue.