Request-id too short about unimrcp HOT 7 CLOSED

Hi Vali,

I agree, that size_t is not an appropriate define for request identifier. It'd would
be reasonable to define it as apr_uint32_t (32 bit unsigned integer), as MRCPv2
states. From other side, this still will not work with some MRCPv1 clients. Honestly
I can't understand why 32 bit should not be enough for an identifier, which is scoped
to the MRCP session.
Is there any way to shorten, limit that value from VE config?

Hi Arsen,

unfortunately it is not possible. VE generates request-ids as usual, i.e. starting
from zero and increasing, with one exception -- the SPEAK requests. Their id is a
kind of hash of what is to be spoken, I guess. Unfortunately the hash is not only
32bit integer, which is not forbidden by MRCPv1 spec in fact. But it is silly, I agree.

Vali

PS. To answer your question from Issue-46. I think VoiceEnabler is not a part of
WebSphere package, but I could not google it anywhere. Maybe it is a nickname our
colleagues use (we do not have VE ourselves, we use another company's one), I will
ask about that.

Hi Arsen,
I can see that change of request id uint32 -> uint64 breaks compatibility, i.e.
server compiled with #define TOO_LONG_MRCP_REQUEST_ID can uderstand plugins compiled
the same and vice versa. Anyway, thanks for effort.
Vali

PS. About VE being part of WebSphere -- sorry, I was blind. See the line from log:
user-agent: WebSphere-VoiceEnabler 5.1.3

Hi Vali,

Sorry, I was a bit tired yesterday and just forgot to add a comment here.
I see you have already caught it!

I decided to support "too long" request identifiers at compile time for now. So you
should define TOO_LONG_MRCP_REQUEST_ID for that. Yes, plugins and server must be
compiled the same way. Hopefully it works for you.

P.S.
I suspected that VE should be included in WebSphere. A while ago someone from IBM had
contributed WebSphere MRCP package to the project, but I couldn't find VE there.
Anyway, thanks for the info.

Thanks for the hot-fix, it works.