I have to use web sign-in for my vvx600 because I have multi-factor auth set up on my Microsoft account (app passwords, regular user/pass don't work - the only way I can sign in at all is web sign-in). The problem is that I have to re-sign in every single day. I am piloting this looking to roll out to the entire company, but this is a non-starter if users have to sign in every day.
I have turned off all of the timeout/auto logout options I can see. I have configured such both through the web interface and through Powershell.
Any tips?
https://login.windows.net/common/oauth2/authorize https://webdir0a.online.lync.com/WebTicket/WebTicketService.svc/OAuth https://webdir0a.online.lync.com/WebTicket/WebTicketService.svc https://login.windows.net/common/oauth2/authorize http://nexus.microsoftonline- 0508092042|auth |4|00|AuthSvc SOAuth2Error, BaseEventInit restart[0] SfbTokenFetchMethod[3] 0508092042|auth |2|00|S/E(sSOAuth2Error,kBaseEventInit),rO(4) 0508092042|auth |3|00|kEOAuth2OAuth2Start:Event(4) not found in Transition Table for state sSOAuth2Error 0508092042|auth |2|00|<\SM>(305)AuthServiceOAuthStateMachine(0x445f54b8):Ctx((513),(4),Ticks(0)) 0508092042|auth |2|00|Silent Indication, CallerService(AuthServiceCallerSnooper) 0508092042|auth |2|00|Policy Dest:(201)AuthServicePolicyServiceKey:(106)AuthServiceOAuthMsgKey:(206)AuthSvcAOServiceReplyKey Caller Service(143)AuthServiceCallerSnooper:IndicationCode(0) ,TransactionID(110363389) 0508092042|auth |2|00|Response(-1)auth,(106)AuthServiceOAuthMsgKey,(-1)lyncStatus,(14),(Expiry,TransactionId,Time,Type):(-1,110363389,1525785642,1)IndicationCode:(0) 0508092042|auth |2|00|Policy Dest:(203)AuthServicePolicyFsmKey:(106)AuthServiceOAuthMsgKey:(215)AuthSvcAOFsmReplyKey Caller Service(-1):IndicationCode(400)Failed to Get oAuth Token ,TransactionID(110363389) 0508092042|auth |2|00|Silent Indication, CallerService(AuthServiceCallerSnooper) 0508092042|auth |2|00|Policy Dest:(201)AuthServicePolicyServiceKey:(106)AuthServiceOAuthMsgKey:(206)AuthSvcAOServiceReplyKey Caller Service(143)AuthServiceCallerSnooper:IndicationCode(100)SM Started ,TransactionID(110363389) 0508092042|auth |2|00|Response(-1)auth,(106)AuthServiceOAuthMsgKey,(-1)lyncStatus,(14),(Expiry,TransactionId,Time,Type):(-1,110363389,1525785642,1)IndicationCode:(100)SM Started 0508092042|auth |2|00|Policy Dest:(202)AuthServicePolicyDBKey:(106)AuthServiceOAuthMsgKey:(212)AuthSvcAODBDBIndKey Caller Service(-1):IndicationCode(400)Failed to Get oAuth Token ,TransactionID(110363389) 0508092042|auth |2|00|<SM>(305)AuthServiceOAuthStateMachine(0x445f54b8):Ctx((513),(7)kBaseEventStop,Ticks(0)) 0508092042|auth |2|00|<\SM>(305)AuthServiceOAuthStateMachine(0x445f54b8):Ctx((513),(-1),Ticks(0)) 0508092042|auth |2|00|<SM>(304)AuthServiceUTStateMachine(0x45159790):Ctx((345),(7)kBaseEventStop,Ticks(0)) 0508092042|auth |2|00|<\SM>(304)AuthServiceUTStateMachine(0x45159790):Ctx((345),(-1),Ticks(0)) 0508092042|auth |2|00|Policy Dest:(202)AuthServicePolicyDBKey:(101)AuthServiceWTMsgKey:(211)AuthSvcAODBIEIndKey Caller Service(-1):IndicationCode(400)Failed to Get oAuth Token ,TransactionID(110363389) 0508092042|auth |2|00|Policy Dest:(202)AuthServicePolicyDBKey:(102)AuthServiceUCMsgKey:(211)AuthSvcAODBIEIndKey Caller Service(-1):IndicationCode(400)Failed to Get oAuth Token ,TransactionID(110363389) 0508092042|auth |2|00|Policy Dest:(201)AuthServicePolicyServiceKey:(102)AuthServiceUCMsgKey:(206)AuthSvcAOServiceReplyKey Caller Service(-1):IndicationCode(400)Failed to Get oAuth Token ,TransactionID(110363389) 0508092042|auth |2|00|Response(-1)auth,(102)AuthServiceUCMsgKey,(-1)pps,(14),(Expiry,TransactionId,Time,Type):(-1,110363389,1525785642,1)IndicationCode:(400)Failed to Get oAuth Token 0508092042|sip |4|00|TLS-DSK:soWebTicketCbFunc: SoWebTicketCb_ResponseError event triggered from the soWebTicket 0508092042|auth |2|00|Policy Dest:(201)AuthServicePolicyServiceKey:(106)AuthServiceOAuthMsgKey:(206)AuthSvcAOServiceReplyKey Caller Service(143)AuthServiceCallerSnooper:IndicationCode(400)Failed to Get oAuth Token ,TransactionID(110363389) 0508092042|auth |2|00|Response(-1)auth,(106)AuthServiceOAuthMsgKey,(-1)lyncStatus,(14),(Expiry,TransactionId,Time,Type):(-1,110363389,1525785642,1)IndicationCode:(400)Failed to Get oAuth Token 0508092112|sip |5|00|SSL_get_error nLen -1 errno 104 nError 5 = (0)error:00000000:lib(0):func(0):reason(0) 0508092112|sip |4|00|TLS Listen Thread Exit
[more log attached]
Hello @and,
welcome to the Polycom Community.
It is always useful to include the currently used UC Software version as issues experienced or a question asked may already be addressed in a newer release.
This also allows yourself and others to check against current software release notes, Administrator Guides or FAQ post’s.
The above is also stated in the "Must Read First" and is the absolute minimum requirement every new post should include. .
In addition providing us with this basic information gives Polycom an idea what Software Versions are used in the field and avoids wasting time trying to troubleshoot issues which have already been addressed.
Therefore the Polycom VoIP FAQ contains this post here:
Question: How can I find out my SIP or UC Software Version of my Phone?
Resolution: Please check here
Looking at your log:
Caller Service(-1):IndicationCode(400)Failed to Get oAuth Token ,TransactionID(110363389) 0508092042|auth |2|00|Policy Dest:(202)AuthServicePolicyDBKey:(102)AuthServiceUCMsgKey:(211)AuthSvcAODBIEIndKey Caller Service(-1):IndicationCode(400)Failed to Get oAuth Token ,TransactionID(110363389) 0508092042|auth |2|00|Policy Dest:(201)AuthServicePolicyServiceKey:(102)AuthServiceUCMsgKey:(206)AuthSvcAOServiceReplyKey Caller Service(-1):IndicationCode(400)Failed to Get oAuth Token ,TransactionID(110363389) 0508092042|auth |2|00|Response(-1)auth,(102)AuthServiceUCMsgKey,(-1)pps,(14),(Expiry,TransactionId,Time,Type):(-1,110363389,1525785642,1)IndicationCode:(400)Failed to Get oAuth Token 0508092042|sip |4|00|TLS-DSK:soWebTicketCbFunc: SoWebTicketCb_ResponseError event triggered from the soWebTicket 0508092042|auth |2|00|Policy Dest:(201)AuthServicePolicyServiceKey:(106)AuthServiceOAuthMsgKey:(206)AuthSvcAOServiceReplyKey Caller Service(143)AuthServiceCallerSnooper:IndicationCode(400)Failed to Get oAuth Token ,TransactionID(110363389) 0508092042|auth |2|00|Response(-1)auth,(106)AuthServiceOAuthMsgKey,(-1)lyncStatus,(14),(Expiry,TransactionId,Time,Type):(-1,110363389,1525785642,1)IndicationCode:(400)Failed to Get oAuth Token 0508092112|sip |5|00|SSL_get_error nLen -1 errno 104 nError 5 = (0)error:00000000:lib(0):func(0):reason(0) 0508092112|sip |4|00|TLS Listen Thread Exit
Have you checked with Microsoft on this?
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Polycom Global Services
Sorry - I had it in my mind to add the version then got distracted by the 20k word limit and had to create a file to add the entire log.
I am running the current latest release: 5.7.1.2205
I have a post open on the MSFT forums - will update here if anything comes of it.
In the meantime, is there anywhere else I could look or anything else I could try? Why would the phone lose the OAuth token in the first place?
Thanks.
Have you tried extension an d PIN login? Create a config file with the credentials and it should stay logged in.