MRCP Keep Alive Does Not Work Over SIP

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Set up an MRCP server with SIP support
2. Run discover application.
3. Callback will return with failure response (despite valid response from 
UniMRCP server).

I am using an UniMRCP 1.0.0

Seems like the problem is caused by Sofia-SIP not parsing the OPTIONS body.

See discussions in Sofia-SIP developers' forum [here 
http://www.mail-archive.com/sofia-sip-devel@lists.sourceforge.net/msg04087.html]

and more in UniMRCP Google Group [here 
http://groups.google.com/group/unimrcp/browse_thread/thread/6be4d8596fbafddc]

Original issue reported on code.google.com by borisu...@gmail.com on 15 Jan 2011 at 7:15

[GoogleCodeExporter]

Well, the problem relates to the implementation of the resource discovery 
mechanism which is also might be used or actually used as a keep alive 
mechanism. So, now it seems clear how the SDP message should be retrieved from 
the SIP OPTIONS response using Sofia-SIP's NUA.

Original comment by achalo...@gmail.com on 19 Jan 2011 at 5:33

• Changed state: Accepted
• Added labels: Component-Client, Component-MRCPv2, OpSys-All, Priority-Medium, Type-Defect

[GoogleCodeExporter]

Forgot to change the status of this issue. It has been fixed in r1799

Original comment by achalo...@gmail.com on 15 Jul 2011 at 8:21

• Changed state: Fixed