Plantronics + Polycom. Now together as Poly Logo

RPD 3.7 Content button greyed out and no GAB

Occasional Collector

RPD 3.7 Content button greyed out and no GAB

In some cases we have a greyed out content and FECC button.


  • RPD 3.7 Windows calls a GS310 6.1.2 or Cisco EX 90 content doesn´t work
  • GS310 calls RPD it works.
  • RPD calls RMX it works.
  • RPD calls RPD it works

This issue is noticed after updating to 3.7.

All endpoints are in out local network and are registered in dma 6.1.2 and rm 8.2.1.


Also we can´t access our GAB in RPD Clients after updating to 3.7.


Has anybody the same problems?

Tags (3)
Message 1 of 3
Polycom Employee & Community Manager

Re: RPD 3.7 Content button greyed out and no GAB

Hello Store,

welcome to the Polycom Community.

If you can always reproduce this and if works when downgrading to RPD 3.6 please go ahead and open a Support Ticket via your Polycom reseller and deliver both working logs and a wireshark from RPD 3.6 and failing logs/wireshark.


We may also need remote access / accounts. 

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

The title Polycom Employee & Community Manager is a community setting and does not reflect my role. I am just a simple volunteer in the community like everybody else. All posts and words are my own & do not represent the views of Employer.


Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge. If you need immediate and/or official assistance please open a service ticket through your proper support channels.
Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's
Message 2 of 3
Occasional Collector

Re: RPD 3.7 Content button greyed out and no GAB

Thanks from your reply.

Now I tested with 3.6 and 3.5.1 but still the same problem. Possibly a problem with the Provision profile on our rm?




Message 3 of 3