Let me clarify this a bit.
The response to the SIP OPTIONS request does contain an SDP message and it's
clear how it should be parsed in general. The question is how to retrieve the
SDP message included in the response to the SIP OPTIONS request using nua API
in
particular.
nua_options() is used to send requests, while nua_r_options is intended to be
used to handle the responses. The nua documentation states
http://sofia-sip.sourceforge.net/refdocs/nua/nua_8h.html#abca36033336ce16e538a279413d2ca51a379a42069d0268db014b5d3bb5d40112
nua_r_options Answer to outgoing OPTIONS.
Parameters:
status response status code (if the request is retried the status is 100 and
the sip->sip_status->st_status contain the real status code from the response
message, e.g., 302, 401, or 407)
phrase a short textual description of status code
nh operation handle associated with the incoming OPTIONS request
hmagic application context associated with the handle
sip response to OPTIONS request or NULL upon an error (status code is in
status and descriptive message in phrase parameters)
tags empty
See also:
nua_options(), RFC 3261 section 11, nua_i_options
All is good. However, as you can see, the tags are always empty and this is the
problem. As a workaround, instead of nua, it's certainly possible to use nta
directly...
Thanks,
Arsen
________________________________
From: Jarod Neuner <j.neu...@networkharbor.com>
To: Boris Ouretskey <borisu...@gmail.com>;
"sofia-sip-devel@lists.sourceforge.net" <sofia-sip-devel@lists.sourceforge.net>
Sent: Tue, January 4, 2011 7:59:10 AM
Subject: Re: [Sofia-sip-devel] Parsing OPTIONS SDP body
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
------------------------------------------------------------------------------
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
