You can set the polycom config to use the other rfc, we did that here.

Thanks,

Moishe Grunstein

Tornado Computer Systems, Inc.

212.400.7650 888.IPPBX.US
Service Request Email: support@nysolutions.com

Computer Networking * Managed Services * IP Video Surveillance * Network Assessments * Web Solutions * Voice over IP * Disaster Recovery * Network Security * Site Surveys * CMS

From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of João Mesquita
Sent: Tuesday, March 24, 2015 11:19 AM
To: freeswitch-users@lists.freeswitch.org
Subject: [Freeswitch-users] Polycom headache

Guys, I am sure most of you have been through this but this is my first time. I am having a HOLD problem with Polycom where they refuse to work according to the "new" RFC3624 using SDP a attributes (sendonly/recvonly) to indicate hold and keep sending 0.0.0.0 as the old RFC2543. I guess this is a known thing since I've found several hits on Google about it and they even created an option for it on their provisioning material. Unfortunately, it doesn't work. No matter what I set on the 

<pre>
if ((sdp->sdp_connection && sdp->sdp_connection->c_address && !strcmp(sdp->sdp_connection->c_address, "0.0.0.0"))) {
switch_log_printf(SWITCH_CHANNEL_SESSION_LOG(session), SWITCH_LOG_WARNING, "RFC2543 from March 1999 called; They want their 0.0.0.0 hold method back.....\n");
sendonly = 2; /* global sendonly always wins */
}

João Mesquita