-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
-
×InformationWindows update impacting certain printer icons and names. Microsoft is working on a solution.
Click here to learn moreInformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center.
- HP Community
- Poly Phones
- UC Platforms
- Re: Trio 8800 Daisy Chaining breaks Exchange calendar logon.
Create an account on the HP Community to personalize your profile and ask a question
05-01-2019 05:23 PM
We have 2 Trio 8800 devices on 5.9.0AA
Both are in Skype for Business base profile
Both have Autodiscover enabled with the url of "https://outlook.office365.com/EWS/Exchange.asmx"
Device 1 is in Hub mode and paired with a Visual Plus
Device 2 is in Device mode
Device 1 is logged into an Office 365 Skype account with mailbox in 365.
Skype logon and Calendaring works without issue as an unchained device.
After Device 1 is chained with Device 2 we start to see the message
Warning, Failed for connect to Exchange Server. Re-enter credential to access Exchange server.
You can click details and sign in. Device 1 will sign back into exchange..
At this point you can see meetings on Device 1 but Device 2 shows Connecting...
After a few minutes both devices will display the warning again.
Breaking the chaining between the Trios will return device 1 to its normal function with access to the calendar.
Device 2 configured as a stand alone non chained device will alsodisplay calendar as expeced.
We attempted re-enabling autodiscover and https://outlook.office365.com/EWS/Exchange.asmx url on Device 2 while chained. The setting was wiped by the device after a few minutes but remained on Device 1.
Long story short.. Trio 8800 cannot access the 365 mailbox calendar while chained with another Trio. Breaking chaining restores the calendar function.
Solved! Go to Solution.
Accepted Solutions
08-29-2019 07:22 AM
Hello all,
this seems to have been fixed by a user raising 1-11984694395. We fixed this internally via EN-130493 and documented this >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
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.
Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN
05-02-2019 12:32 AM
Hello @Scott Schering ,
welcome to the Poly Community.
When using Daisy Chaining no configuration is required on the 2nd or 3rd etc. unit.
Please, factory default the unit. All changes required are only needed on the main unit.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.
Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN
05-06-2019 09:53 AM
@SteffenBaierUK wrote:Hello @Scott Schering ,
welcome to the Poly Community.
When using Daisy Chaining no configuration is required on the 2nd or 3rd etc. unit.
Please, factory default the unit. All changes required are only needed on the main unit.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Thanks ! We had the same issue where every 10 or 15min a popup message indicated an Exchange authenticated issue. We did a factory default this morning on both units and since then so far so good. No more error message.
Thanks
05-06-2019 11:59 AM
2nd test
New skype account - same reqults
3rd test
Factoy wipe both devices
On Both devices
LLDP off ( Required on our netowork to prevent from dropping the device into the phone vlan )
CDB Off ( Required on our netowork to prevent from dropping the device into the phone vlan )
Device 1 (Host) - set to Skype for Business mode
Signed in as skype resource account.
verified calendar and address book
Device 2 - set to device mode
Device 1 - Entered networked devices and waited for Device 2 to appear.
Paired devices
Skype works from both devices.
Device 2 can not connect to exchange server calendar ( account is in office 365 )
Same reqults as before
05-06-2019 01:52 PM
Hello @Scott Schering ,
If you are not adding any configuration to the 2nd unit please open a support ticket.
In order to raise a support ticket, you need to work with your Poly reseller as they need to do this for you.
End Customers are unable to open a ticket directly with Poly support.
If this is some sort of an Internet discounter providing your MAC address or your Poly devices serial will enable us to look up who would be able to support you. This may not be who you purchased the Poly device from.
If the unit is no longer within the 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
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.
Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN
08-29-2019 07:22 AM
Hello all,
this seems to have been fixed by a user raising 1-11984694395. We fixed this internally via EN-130493 and documented this >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
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.
Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN
Didn't find what you were looking for? Ask the community