[Freeswitch-users] Polycom headache

[Michael Jerris]

Brian found this in the admin guide:

Enable Call Hold Parameter Function
Specify whether to use RFC 2543 (c=0.0.0.0) or RFC 3264 (a=sendonly or a=inactive) for outgoing hold signaling.
Specify whether to use sendonly hold signaling. Configure local call hold reminder options. Specify the music-on-hold URI.
Example Call Hold Configuration
template > parameter
sip-interop.cfg > voIpProt.SIP.useRFC2543hold
sip-interop.cfg > voIpProt.SIP.useSendonlyHold sip-interop.cfg > call.hold.localReminder.* sip-interop.cfg > voIpProt.SIP.musicOnHold.uri

> On Mar 24, 2015, at 11:25 AM, João Mesquita <jmesquita at freeswitch.org> wrote:
> 
> I am deeply sorry, I've hit send too early. Damn Gmail...
> 
> 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 voIpProt.SIP.useRFC2543hold option, it still sends 0.0.0.0 as follows:
> 
> v=0
> o=- 1167669703 1167669704 IN IP4 0.0.0.0
> s=Polycom IP Phone
> c=IN IP4 0.0.0.0
> t=0 0
> m=audio 2228 RTP/AVP 8 101
> a=rtpmap:8 PCMA/8000
> a=rtpmap:101 telephone-event/8000
> 
> I've also looked into FS code and I've found something on the lines of, but this is not kicking in either (granted, I am using 1.4.14 still and I really don't believe FS should cope with this crap either).
> 
> 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 */
> }
> 
> So, why am I coming to this ML for help? I wanted to know how did you guys figure this out, is there an exact firmware version where Polycom has this figured out or is it one of those long lasting ones that Polycom never cares to address?
> 
> And btw, I tried with UC software version 4.0.8 and 4.0.7.
> 
> Thank you,
> João Mesquita
> 
> 
> On Tue, Mar 24, 2015 at 12:19 PM, João Mesquita <jmesquita at freeswitch.org <mailto:jmesquita at freeswitch.org>> wrote:
> 
> 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
> 
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services: 
> consulting at freeswitch.org
> http://www.freeswitchsolutions.com
> 
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://confluence.freeswitch.org
> http://www.cluecon.com
> 
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20150324/19f257c1/attachment-0001.html