Not sure if this is necessary, but UniMRCP probably has to set the Accept: header to in the OPTIONS request to application/sdp. If not, UniMRCP should check the OPTIONS response for Content-Type: and Content-Length: fields to determine if an application/sdp was sent with the response. If a SDP response was sent, use the sdp module to parse that response: http://sofia-sip.sourceforge.net/refdocs/sdp/index.html -Jarod
________________________________ From: Boris Ouretskey [mailto:borisu...@gmail.com] Sent: Tuesday, January 04, 2011 8:19 AM To: sofia-sip-devel@lists.sourceforge.net Subject: [Sofia-sip-devel] Parsing OPTIONS SDP body Hi, While using UniMRCP infratrstructure which in its turn uses Sofia-SIP as its SIP engine we encountered the following issue. Seems like Sofia-SIP does not support parsing SDP body of OPTIONS reply. This issue fails keep-alive mechanism of UniMRCP server which relies on SDP response to OPTIONS request. (suppose OPTIONS body request was empty) Is anyone aware of the problem and knows how to fix it? Thanks ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
