I updated to 5.5.1.11526 yesterday and now I am seeing an alert on the top-right of my VVX 400 screen. The alert is "exchange url not configured"
I'm not wanting to use Exchange and it's completely disabled (see attached image).
Any ideas how to clear the warning?
Solved! Go to Solution.
Hi again,
After playing around this seems to due the trick.
<exchange.server exchange.server.url="0.0.0.0" />
You're not alone... you can clear it from the Settings -> Status -> Warnings menu, howerver, it will most likely show back up after a reboot.
Hello all,
welcome to the Polycom Community.
Could you try:
<test feature.EWSAutodiscover.enabled="0" feature.exchangeCalendar.enabled="0" />
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Polycom Global Services
Steffen,
Good stuff, thanks for the quick reply on this.
Steffen,
I have applied this configuration and have confirmed that these services are indeed disabled (checked status in the web interface) but the warning is still displayed after each reboot.
Hello cwallace-ena,
so you are still seeing the triangle after rebooting and the message in the diagnostic menu?
I would open a support ticket.
In order to raise a support ticket you need to work with your Polycom reseller as they need to do this for you.
If this is some sort of an Internet discounter please post your phone's MAC address so I can look up who would be able to support you.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
Polycom Global Services
Will do, jsut wanted to provide initial feedback for those that were following. Thanks Steffen!
Hello all,
if the phone is in Open SIP / Generic mode I can reproduce this.
Anyone affected by this should open a Service Ticket via their Polycom reseller quoting 1-4612541293 / VESC-7062
The only workaround at present is either:
Best Regards
Steffen Baier
Hi to all,
We got thsi from support-
" The issue is set to be fixed on 5.5.2 ETA around end of February. There are a lot of complains received about this issue and there may be a fix that will come out earlier however it is not confirmed yet."
Hi again,
After playing around this seems to due the trick.
<exchange.server exchange.server.url="0.0.0.0" />