Oops, I had some typos in the original code block (and for some reason, can't edit the original post).
Use this one instead. We saw similar issues with GoToMeeting and certain other automated attendants with the Trio, and this was the fix.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <PHONE_CONFIG> <ALL tone.dtmf.onTime="100" /> </PHONE_CONFIG>
Thanks for providing the update version of your code, but this still does not work. Our phone is still unable to detect the # key.
I am trying to connect to Google Meet and it fails to register the PIN number. Also, our VoIP provider is a service called Dialpad. I'm not sure how much this help because the issue appears to be the Polycom phone itself.
Try the other settings in the FAQ article
Try this first:
Then try these two:
Use the same format as my previous file.
welcome back to the Polycom Community.
As maybe already outlined please 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 please post either your phone's MAC address or your Polycom devices serial so I can 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
I am currently on holiday so please wait for my return in case you need information on who to contact for support.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Polycom Global Services
If official support is required please check how to phone or open a case here----------------
Reading this thread helped me resolve my issue. I exported the config of our Trio 8500 and added the line:
between the tags in the file. Seems to be fine now with our BT conference service which requires a pin to authenticate once connected to the service
Thank you for your feedback!
We have finally resolved this issue! Our VoIP provider kept on pushing there config down to our phone, so it always reverted the changes when we made a modification. To circumvent this, we had to null the values on the provisioning server fields and any other related fields, then had to include the following codes in the config file:
voIpProt.SIP.dtmfViaSignaling.rfc2976="1" tone.dtmf.viaRtp="0" tone.dtmf.rfc2833Payload="127"