Closed GoogleCodeExporter closed 8 years ago
version 1.1.0 works.
Original comment by flu...@gmail.com
on 4 Aug 2014 at 2:59
As far as I can see, although an MRCPv1 profile was used with MRCPRecog(), the
MRCPv2 agent was still somehow involved in session initialization, which is
definitely not the expected behavior.
[Aug 1 10:20:08] DEBUG[1795] src/apt_task.c: Signal Message to
[MRCPv2ConnectionAgent] [0x7fa5bc005fa0;1;0]
I'm not even sure whether this can be a configuration or build issue or
anything else. As the next step, can you provide additional information such as
configuration and build related details (Linux, gcc version,...).
Original comment by achalo...@gmail.com
on 12 Aug 2014 at 1:16
I'm using Centos 6.5, kernel 2.6.32-431.20.3.el6.x86_64, I use
gcc-4.4.7-4.el6.x86_64 to build uni-ast-package-1.2.0. I send you all the
configs. Thank's for the response....please tell me if you need more info
Original comment by laar78...@gmail.com
on 12 Aug 2014 at 10:05
Attachments:
It looks like app_unimrcp loads MRCP version 1 profiles incorrectly (MRCP
version 2 profiles are not affected).
I had made a few related changes in the client stack recently which were
included in UniMRCP-1.2.0 release. The client stack itself is not affected,
both v1 and v2 profiles work as intended. However, app_unimrcp needs to be
patched.
Temporary workarounds:
1) Use MRCPv2 instead of MRCPv1
or
2) Use unimrcp-1.1.0 with the latest Asterisk modules 1.2.0
or
3) Downgrade to uni-ast-package-1.1.0 completely
Original comment by achalo...@gmail.com
on 14 Aug 2014 at 5:32
Fixed in r2161. Thanks for bringing this up.
Original comment by achalo...@gmail.com
on 18 Aug 2014 at 7:15
Original issue reported on code.google.com by
laar78...@gmail.com
on 28 Jul 2014 at 9:07Attachments: