Closed achaloyan closed 9 years ago
version 1.1.0 works.
Reported by flujan
on 2014-08-04 14:59:05
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,...).
Reported by achaloyan
on 2014-08-12 01:16:04
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
Reported by laar78910
on 2014-08-12 22:05:40
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
Reported by achaloyan
on 2014-08-14 17:32:02
Accepted
Fixed in r2161. Thanks for bringing this up.
Reported by achaloyan
on 2014-08-18 19:15:50
Fixed
Originally reported on Google Code with ID 173
Reported by
laar78910
on 2014-07-28 21:07:26