Lync Extension / PIN login - factory reset - login failure

[James_Helman]

Robin

PIN auth not being available on the phones is almost always a DHCP configuration issue. Other issues will require logging and environment information that is best not posted to a public forum to trouble shoot. I know PIN auth works in 5.4.3.1014 as we are using it on over 600 phones currently.  Here is some logging you can use t oconfirm the DHCP settings.

Change Web Ticket logging to Debug and log file size to 180.  Restart phone and look for “soWebTicketServersGet “ and “soWebTicketServersGetPinAuthService” in the app log.  If everything is working you should find something like this. 

Good

0621091111|tickt|1|00|[soWebTicketServersGet]:[8693] Entry  Request Uri is [https://server.domain.com:443/CertProv/CertProvisioningService.svc/mex]

Bad

0918144405|tickt|1|00|soWebTicketServersGet: request URI is /mex

This is the phone enabling Pin auth

0621092055|tickt|1|00|[soWebTicketServersGetPinAuthService]:[8847] PinAuthServiceAddress is [https://server.domain.com/WebTicket/WebTicketService.svc/pin]

0621092055|tickt|1|00|[soWebTicketServersGetPinAuthService]:[8867] CertServiceAddress is [//server.domain.com /WebTicket/WebTicketService.svc/cert]

0621092055|tickt|1|00| FSM : Input      = (FSM_INPUT_EVENT_IDENTIFY_TOKEN_PROVIDER) (3)

0621092055|tickt|1|00| FSM : Old State  = (FSM_STATE_SIGNIN_ONPREM_PINAUTH) (3)

0621092055|tickt|1|00| FSM : New State  = (FSM_STATE_SIGNIN_ONPREM_PINAUTH) (3)

0621092055|tickt|1|00| FSM : Action     = (ACT_IdentifyTokenProvider) (3)

Jeff Schertz blog on DHCP Option 43 http://blog.schertz.name/2012/05/understanding-dhcp-option-43/  This is how your DHCP should be setup for PIN auth.  There are other ways to do it with the VVX phones but in my opinion they should be avoided.