I just finished migrating from Lync 2010 Standard to Lync 2013 Enterprise.
I have the following Servers in my Topology:
1 Front-End
1 Back-End (SQL Database)
1 Edge Server
1 WAC
1 Reversed Proxy (ARR_3.0)
I'm currently having trouble with PowerPoint Sharing and others features such as Poll and Whiteboard for Internal and External Users.
We have 2 Client versions that are being used by our users, Lync 2010 and Lync 2013 Basic Client. Only lync 2013 client are having trouble with the presentation.
Computers Internally are joined to domain. But when I use computer that are not domain joined and using Skype for Business client. The Error was "Can't sign in to Skype for Business. There was a problem verifying the certificate from the server"
Certificate Used: Internal CA and WildCard. Wild Card is beeing used by EDGE external and Reversed Proxy Server.
.............Back to the client presentation error....
I got the log on the client and found the following errors:
Error 1. I/O In
SIP/2.0 401 Unauthorized
Date: Mon, 24 Sep 2018 15:31:25 GMT
WWW-Authenticate: NTLM realm="SIP Communications Service", targetname="LetoFrontEnd.newpagcor.com", version=4
WWW-Authenticate: Kerberos realm="SIP Communications Service", targetname="sip/LetoFrontEnd.newpagcor.com", version=4
WWW-Authenticate: TLS-DSK realm="SIP Communications Service", targetname="LetoFrontEnd.newpagcor.com", version=4, sts-uri="https://lync2013pool1.newpagcor.com:443/CertProv/CertProvisioningService.svc"
From: <sip:lync.user2@pagcor.ph>;tag=852225f2a0;epid=576706f365
To: <sip:lync.user2@pagcor.ph>;tag=3271CA61C8AD21D0EC6E6BBFECB1D25A
Call-ID: d894dbfa7b794d1aacac8d67940c06aa
CSeq: 1 REGISTER
Via: SIP/2.0/TLS 192.168.100.19:57984;ms-received-port=57984;ms-received-cid=7000
Server: RTC/5.0
Content-Length: 0
Error 2:
SIP/2.0 403 Forbidden
Proxy-Authentication-Info: Kerberos qop="auth", opaque="CC034702", srand="DF097C61", snum="1", rspauth="040401ffffffffff0000000000000000132b0b11061fdef76519cd81", targetname="sip/LetoFrontEnd.newpagcor.com",
realm="SIP Communications Service", version=4
From: <sip:lync.user2@pagcor.ph>;tag=852225f2a0;epid=576706f365
To: <sip:lync.user2@pagcor.ph>;tag=3271CA61C8AD21D0EC6E6BBFECB1D25A
Call-ID: d894dbfa7b794d1aacac8d67940c06aa
CSeq: 2 REGISTER
Via: SIP/2.0/TLS 192.168.100.19:57984;ms-received-port=57984;ms-received-cid=7000
ms-diagnostics: 4004;reason="Credentials provided are not authorized to act as specified from URI";AuthenticatedIdentity="CORPORATE\FDCAdmin";source="LetoFrontEnd.newpagcor.com"
ms-diagnostics-public: 4004;reason="Credentials provided are not authorized to act as specified from URI";AuthenticatedIdentity="CORPORATE\FDCAdmin"
Server: RTC/5.0
Content-Length: 0
Error 3:
SIP/2.0 401 Unauthorized
Date: Mon, 24 Sep 2018 15:31:26 GMT
WWW-Authenticate: NTLM realm="SIP Communications Service", targetname="LetoFrontEnd.newpagcor.com", version=4
WWW-Authenticate: Kerberos realm="SIP Communications Service", targetname="sip/LetoFrontEnd.newpagcor.com", version=4
WWW-Authenticate: TLS-DSK realm="SIP Communications Service", targetname="LetoFrontEnd.newpagcor.com", version=4, sts-uri="https://lync2013pool1.newpagcor.com:443/CertProv/CertProvisioningService.svc"
From: <sip:lync.user2@pagcor.ph>;tag=9b09120414;epid=576706f365
To: <sip:lync.user2@pagcor.ph>;tag=3271CA61C8AD21D0EC6E6BBFECB1D25A
Call-ID: 6c8edf5f211f438a8fcfba36a864e844
CSeq: 1 REGISTER
Via: SIP/2.0/TLS 192.168.100.19:57985;ms-received-port=57985;ms-received-cid=7100
Server: RTC/5.0
Content-Length: 0
Error 4:
SIP/2.0 403 Location profile only available when UC enabled.Proxy-Authentication-Info: Kerberos qop="auth", opaque="0AB87503", srand="FB970A96", snum="2", rspauth="040401ffffffffff0000000000000000efd85699eeed3a7a68c30cda", targetname="sip/LetoFrontEnd.newpagcor.com", realm="SIP Communications Service", version=4
Via: SIP/2.0/TLS 192.168.100.19:57985;ms-received-port=57985;ms-received-cid=7100
From: <sip:lync.user2@pagcor.ph>;tag=f06af18b0a;epid=576706f365
To: <sip:lync.user2@pagcor.ph;gruu;opaque=app:locationprofile:get;default>;tag=3271CA61C8AD21D0EC6E6BBFECB1D25A
Call-ID: 2c71a1dc2e5c4d6bb66eb23acb79ad24
CSeq: 1 SERVICE
ms-diagnostics: 2;reason="See response code and reason phrase";AppUri="http://www.microsoft.com/LCS/TranslationService";source="LetoFrontEnd.newpagcor.com"
Server: RTC/5.0
Content-Length: 0
Then, on the FE server Log, I found this Event ID 31055 and 31059.
I found this forum but I guess this is not applicable to me as I have completed the migration already.
social.technet.microsoft.com/Forums/lync/en-US/c96ac7d8-dff1-4dde-9030-be505e276752/lync-2013-error-31055-31059-ls-call-park-service-the-database-being-used-by-group-pickup-is-not?forum=lyncdeploy
Need some advise for this.
Thanks!