Failed to Find Channel errors about unimrcp HOT 2 CLOSED

First of all, thanks for the issue report and the detailed description.

Initially reading the description, I considered, that client received MRCP message
through wrong TCP/MRCPv2 connection. Then I tried and reproduced the issue on my side
and soon came to conclusion that it was indeed a typical memory corruption.
Probably the most interesting part is issue appeared to be related to recognizer
only, at least the described behavior wasn't replicable for synthesizer. I was just
"surprised" when eventually found the issue in RTP transmitter code. 
Size of the buffer allocated for RTP packets must include not only RTP payload, but
RTP header also. Actually outstanding 12 bytes can override anything allocated next
to this buffer, the result is completely unpredictable...
It was indeed a major issue, which existed for a while.
Anyway now it's fixed in r956 and this fix can (should) be easily applied over any
recent source distribution.

This issue can be safely marked as "verified" now.