Trio 8800 VisualPro Unable to Join Skype Meeting

[coost]

I have a Trio 8800 VisualPro (GS500 + EagleEyeIV). 

Trio Software = 5.8.0.15024 

We're fully O365 Cloud, Skype and Exchange Online, no hybrid

I am able to sign into Skype for Business, it's connecting to Exchange and pulling down meeting information, the Join button shows up next to Skype meetings, but when I click Join I get a fast busy on the Trio and this in the logs:

0321135308|pps |4|00|[PpsHybridC]: OnEvRegistrarUpdate clearing regParams State(0) Expire(0) isOcs(1)
0321135308|wmgr |4|00|[sendXMLObject] Proxy connect result '0'
0321135309|app1 |5|00|[cccpScheduledMeetingJoin] Input Link(sip:jdoe@contoso.com;gruu;opaque=app:conf:focus:id:7RH1RN7K?conversation-id=E7Bi87jI06;) Output Url(sip:jdoe@contoso.com;gruu;opaque=app:conf:focus:id:7RH1RN7K?conversation-id=E7Bi87jI06;) isCallLogRejoin(0) Subject Exist(1)
0321135310|sip |4|00|[CStkCccp::getMedSessHdl] no MedSessHdl found. AVMCU(0x0) m_hUI(0x0) AppShare(0x0) m_hUI(0x0)
0321135310|app1 |4|00|AppHybridC::procLclMsg conference call, increasing watchdogTimeOut to 20000
0321135310|app1 |4|00|AppHybridC::procLclMsg conference call, increasing watchdogTimeOut to 20000
0321135310|wmgr |4|00|[sendXMLObject] Proxy connect result '0'
0321135310|app1 |4|00|AppHybridC::procLclMsg conference call, increasing watchdogTimeOut to 20000
0321135310|sip |4|00|[CStkCccp::getMedSessHdl] no MedSessHdl found. AVMCU(0x0) m_hUI(0x0) AppShare(0x0) m_hUI(0x0)
0321135310|wmgr |4|00|[sendXMLObject] Proxy connect result '0'
0321135311|sip |4|00|[CStkCccp::getMedSessHdl] no MedSessHdl found. AVMCU(0x0) m_hUI(0x0) AppShare(0x0) m_hUI(0x0)
0321135311|sip |4|00|~CStkCccp C3PFacade REMOVE not possible without call(0x0) sess(0x0) indexHdl(0x0)
0321135312|app1 |4|00|AppHybridC::procLclMsg conference call, increasing watchdogTimeOut to 20000
0321135312|wmgr |4|00|[sendXMLObject] Proxy connect result '0'
0321135313|clist|4|00|dbCfg::getServerDir:Unknown dbCfg type
0321135313|clist|4|00|dbCfg::getServerDir:Unknown dbCfg type

With "Meet Now", I get "Internal Conference Error" on the Trio screen and this in the logs:

0321135833|sip  |4|00|[CStkCccp::getMedSessHdl] no MedSessHdl found. AVMCU(0x0) m_hUI(0x0) AppShare(0x0) m_hUI(0x0)
0321135833|sip  |4|00|Failure response for C3pGetConferencingAbilities. Move on to AddConference
0321135833|sip  |4|00|[CStkCccp::getMedSessHdl] no MedSessHdl found. AVMCU(0x0) m_hUI(0x0) AppShare(0x0) m_hUI(0x0)
0321135834|sip  |4|00|[CStkCccp::getMedSessHdl] no MedSessHdl found. AVMCU(0x0) m_hUI(0x0) AppShare(0x0) m_hUI(0x0)
0321135834|sip  |4|00|[CStkCccp::getMedSessHdl] no MedSessHdl found. AVMCU(0x0) m_hUI(0x0) AppShare(0x0) m_hUI(0x0)
0321135834|sip  |4|00|~CStkCccp C3PFacade REMOVE not possible without call(0x0) sess(0x0) indexHdl(0x0)

[SteffenBaierUK]

Hello @coost ,

welcome to the Polycom Community.

We would need far more detailed and longer logs as what you shared with the community.

Jan 17, 2017 Question:How can I troubleshoot simple Skype for Business, LYNC or Office365 issues?

Resolution: Have a look => here <=

If all of this fails you can always open a ticket.

In order to raise a support ticket you need to work with your Polycom reseller as they need to do this for you.

End Customers are unable to open a ticket directly with Polycom support.

If this is some sort of an Internet discounter providing your MAC address or your Polycom devices serial will enable us to look up who would be able to support you. This may not be who you purchased the Polycom device from.

If the unit is no longer within warranty please be prepared to Pay Per Incident / PPI. This is all outlined in detail here

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

[coost]

Attached are more details logs.  I signed out of Skype and signed back in.  The Trio is setup for Hybrid registration with an internal DMA on line 2 and Zoom on line 3, but I took it outside of the corporate network to verify my issues weren't firewall related so you'll see DMA registration failing in the logs.  I initiated 1 test call, which can be seen at the bottom of the logs.

Here are the Skype for Business Parameters:

User Certificate Fetch Status	Got User Certificate
Web Auto Discovery User Location	External
Web Auto Discovery FQDN	sipfed0A.online.lync.com
Certificate Valid from	Fri Mar 22 11:43:36 2019
Certificate Valid up to	Fri Mar 22 19:43:36 2019
Skype for Business Environment	Skype for Business EnvO365Prod
Skype for Business O365 Status	Enabled
Certificate Valid Until	27901 seconds
Certificate Validity Duration	28800 seconds
Certificate Exists	Yes
Certificate Expired	No
Credential Type	Username and Password
Certificate Provisioning Service URL	Not Configured
Web Ticket Service URL	https://webpooldm10a22.infra.lync.com/WebTicket/WebTicketService.svc
Web Ticket Proof URL	https://webpooldm10a22.infra.lync.com/CertProv/CertProvisioningService.svc/WebTicket_Proof_SHA1
Root Certificate Chain URL	
Web Ticket Server Pin Auth	
Web Ticket Server Certificate Auth	https://webpooldm10a22.infra.lync.com/WebTicket/WebTicketService.svc/cert
Federation Data Mex URL	http://nexus.microsoftonline-p.com/federationmetadata/2006-12/FederationMetaData.xml
Update Server Internal URL	https://sippoolDM10a22.infra.lync.com:9999/RequestHandler/ucdevice.upx
Update Server External URL	https://webpoolDM10a22.infra.lync.com:443/RequestHandlerExt/ucdevice.upx

[SteffenBaierUK]

Hello @coost ,

again the logs do not contain more details. A backup could also be helpful to see if there are parameters that would affect this.

The logs where not changed for example to show more details on the SIP logging module.

I suggest, if you are stuck, follow up as already advised and open a ticket as explained.

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier