Zoomtopia is here. Unlock the transformative power of generative AI, helping you connect, collaborate, and Work Happy with AI Companion.
Register nowEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Learn moreKeep your Zoom app up to date to access the latest features.
Download Center Download the Zoom appDownload hi-res images and animations to elevate your next Zoom meeting.
Browse Backgrounds Zoom Virtual BackgroundsEmpowering you to increase productivity, improve team effectiveness, and enhance skills.
Zoom AI CompanionUser groups are unique spaces where community members can collaborate, network, and exchange knowledge on similar interests and expertise.
Help & Resources is your place to discover helpful Zoom support resources, browse Zoom Community how-to documentation, and stay updated on community announcements.
The Events page is your destination for upcoming webinars, platform training sessions, targeted user events, and more. Stay updated on opportunities to enhance your skills and connect with fellow Zoom users.
Starting February 3, 2025, Zoom Phone customers must add their phone numbers to an approved 10DLC campaign in order to use SMS/MMS capabilities on their numbers.
Introducing more live support options! More Zoom customers now have access to live agent chat support. Sign in and visit our Contact Support page to see all your available support options. We’re here to help!
2025-02-05 08:32 PM
Solved! Go to Solution.
2025-02-06 12:05 PM
That's quite a bit of issues and I suspect Zoom is seeing this as a local network issue. I've been down this road plenty of times. The challenge here is that Zoom does not troubleshoot local networks even when it's impacting Zoom phone. Even if you had Premier or Premier+ which our organization does, Zoom just won't help. Your best bet would be to engage Poly/HP to help you enable logging levels and capture what is causing the issue. If you don't have support? You might want to purchase a new E550 with support, then using that one as your example. Poly/HP will not allow you to add support on a device that has already been purchased.
2025-02-06 07:21 AM
Hello Mark,
Can you tell us exactly what your issue is with the Poly Edge E350?
2025-02-06 10:41 AM
Hello Sparrow,
Our Poly E-350 desk phones initially worked fine with Zoom, but we've been experiencing persistent issues, seemingly related to the provisioning server.
Frequent "URL Calling Disabled" Errors:
Outbound Call Failures:
Phone Rebooting & Missing Features:
It's been two weeks since opening a support ticket, and we're still facing these issues. Any insights or next steps would be greatly appreciated.
Cheers,
Mark
2025-02-06 10:47 AM
Hello Sparrow,
Our Poly E-350 desk phones initially worked fine with Zoom, but we've been experiencing persistent issues, seemingly related to the provisioning server.
Frequent "URL Calling Disabled" Errors:
Outbound Call Failures:
Phone Rebooting & Missing Features:
It's been two weeks since opening a support ticket, and we're still facing these issues. Any insights or next steps would be greatly appreciated.
Cheers,
Mark
2025-02-06 10:48 AM
Hi Sparrow,
I have posted a detailed reply three times but don't see it published in this community forum.
Mark
2025-02-06 12:05 PM
That's quite a bit of issues and I suspect Zoom is seeing this as a local network issue. I've been down this road plenty of times. The challenge here is that Zoom does not troubleshoot local networks even when it's impacting Zoom phone. Even if you had Premier or Premier+ which our organization does, Zoom just won't help. Your best bet would be to engage Poly/HP to help you enable logging levels and capture what is causing the issue. If you don't have support? You might want to purchase a new E550 with support, then using that one as your example. Poly/HP will not allow you to add support on a device that has already been purchased.
2025-02-07 07:10 PM
I have the answers!
My phone that was sending messages throughout the day that it was losing provisioning:
- On the Poly's menu is diagnostics. I would jump into that when the phone failed and see that the Poly provisioning server would sometimes fail. Sometimes, there would be a DNS failure. So, I went into my TP-Link router and did two things. #1 changed the DNS server address from whatever it was to Google's 8.8.8.8 and 8.8.4.4. Then, I also found a setting called flow control, and the hint said some devices don't like this setting, so I turned it off. It is fixed. My phone is stable and has not lost provisioning since
-The second big deal was a common room phone that would reboot continuously during the day, saying the network was down. I even had to unplug the device as its reboot tones were constant and unbearable. This phone is on WiFi. I decided to remove the phone from the wall and take it to my office to troubleshoot. I had a spare power adapter, so I used that. In my office, the phone worked perfectly. Put it back in the common room, and it would fail. Long story short, the plug-in transformer from Poly had two identically sized blades that pushed into the AC outlet. There is not one size larger than the other, as you might expect for a device that requires it to be in the hot lead. OMG, I flipped the plug-in adapter around, and the phone came to life immediately and has not failed since.
While I am thrilled to have solved all of the issues I was having, I would still grade the support team with critically low marks for not even opening my case in nearly two weeks.
Mark
2025-02-06 12:13 PM
That is a very kind and thoughtful response; thank you so much! Our network is relatively simple: Zipply Fiber 1GB up/down, TP-Link router with all security disabled for other phones, and a couple of Netgear Gig hubs.
Appreciate the 411!