That is a valid point. I will include the support for both. Thanks, Arjun.
________________________________ From: Nikolay Kondratyev [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 03, 2008 4:02 AM To: Nair, Arjun (CAR:9D30); [EMAIL PROTECTED] Subject: RE: [sipX-dev] Far side hold detected incorrectly in SipConnection.cpp I'd like to coment on this as a sipx user. I know that many devices (phones and fxs gw's) still support both ("0.0.0.0" and "sendonly") hold formats. So I believe that sipx should also understand both "hold formats" to support old configurations. Thanks and regards, Nikolay. ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Arjun Nair Sent: Monday, June 02, 2008 9:14 PM To: [EMAIL PROTECTED] Subject: [sipX-dev] Far side hold detected incorrectly in SipConnection.cpp Hello, Currently in "SipConnection::processInviteRequest" (sipXcallLib), far side holds are detected by checking if the remote RTP port, in the SDP data of the re-Invite, is set to 0, or if the remote RTP IP address is set to "0.0.0.0". According to section 8.4 of RFC 3264, this method of placing a call on hold is deprecated, and instead, the re-Invite is sent with the parameter "a=sendonly" set in the SDP data. I have attached patch for this change. I will open a JIRA issue and submit the patch. Comments? Thanks, Arjun <<SipConnection.diff>>
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
