Cisco CCX/MRCP v2

297 views
Skip to first unread message

Nathan Cartwright

unread,
Jul 1, 2020, 3:23:36 PM7/1/20
to UniMRCP
I'm not sure if this is special to CCX or not but whenever I attempt using MRCP v2 something is causing a crazy loop. 



2020-07-01 15:16:52:283476 [NOTICE] Add Session <8ae95000d42a4abc>
2020-07-01 15:16:52:283510 [INFO]   Receive Offer 0x7f770c0120b8 <8ae95000d42a4abc> [c:1 a:1 v:0]
2020-07-01 15:16:52:283534 [INFO]   Found MRCP Engine [GDF-1] for Resource [speechrecog] 0x7f770c0120b8 <8ae95000d42a4abc>
2020-07-01 15:16:52:283554 [NOTICE] Maximum channel count 2 exceeded for engine [GDF-1]
2020-07-01 15:16:52:283570 [WARN]   Failed to Create Engine Channel 0x7f770c0120b8 <8ae95000d42a4abc> [speechrecog]


Looks like there is a failure to create the channel and then it tries again using all of the licenses. 

Do not seem to have this issue with MRCP v1 so guessing this is an issue with the SDP headers... or ports?

Nathan Cartwright

unread,
Jul 2, 2020, 10:10:20 AM7/2/20
to UniMRCP
After some troubleshooting - this only seems to happen when I specify a built-in grammar to trigger a DialogFlow event. Thoughts? 


RECOGNITION-COMPLETE 107 COMPLETE MRCP/1.0
Completion-Cause: 000 success
Content-Type: application/x-nlsml
Content-Length: 783

<?xml version="1.0"?><result><interpretation grammar="session:fie...@field.grammar" confidence="99"><instance><query_text>how can I help</query_text><action>smalltalk.agent.can_you_help</action><parameters></parameters><all_required_params_present>true</all_required_params_present><fulfillment_text>I&apos;ll certainly try my best. How can I help?</fulfillment_text><fulfillment_messages><text><text>I&apos;ll certainly try my best. How can I help?</text></text></fulfillment_messages><intent></intent><intent_detection_confidence>0.999641</intent_detection_confidence><language_code>en-us</language_code><output_audio_uri>http://localhost/utterances/umsgdf-102a08ecbdfd492d-1107.wav</output_audio_uri></instance><input mode="speech">how can
2020-07-02 10:02:46:098613 [INFO]   Send RTSP Data 192.168.86.159:1554 <-> 10.10.10.120:51360 [41 bytes]
 I help</input></interpretation></result>
2020-07-02 10:02:46:117393 [NOTICE] Accepted RTSP Connection 192.168.86.159:1554 <-> 10.10.10.120:51380
2020-07-02 10:02:46:129027 [INFO]   Receive RTSP Data 192.168.86.159:1554 <-> 10.10.10.120:51380 [396 bytes]
SETUP rtsp://192.168.86.159:1554/synthesizer RTSP/1.0
CSeq: 1
Transport: RTP/AVP;unicast;client_port=35085-47360;mode=record
Content-Type: application/sdp
Content-Length: 208

v=0
o=- 123 456 IN IP4 10.10.10.120
s=Unified Contact Center Express 12.5.1.10000-31
c=IN IP4 10.10.10.120
t=0 0
m=audio 35085 RTP/AVP 0 96
a=rtpmap:0 pcmu/8000
a=rtpmap:96 telephone-event/8000
a=fmtp:96 0-15



2020-07-02 10:02:46:129194 [NOTICE] Create RTSP Session <5369649bdd334475>
2020-07-02 10:02:46:129232 [INFO]   Create Session 0x7f276001a418 <new> [uni1]
2020-07-02 10:02:46:129253 [INFO]   Add RTSP Session <5369649bdd334475>
2020-07-02 10:02:46:129313 [WARN]   Cannot read the first field in start-line
2020-07-02 10:02:46:129334 [WARN]   Failed to Parse RTSP Data
2020-07-02 10:02:46:129343 [NOTICE] Add Session <5369649bdd334475>
2020-07-02 10:02:46:129358 [WARN]   Cannot read the first field in start-line
2020-07-02 10:02:46:129391 [INFO]   Receive Offer 0x7f276001a418 <5369649bdd334475> [c:0 a:1 v:0]
2020-07-02 10:02:46:129409 [WARN]   Failed to Parse RTSP Data
2020-07-02 10:02:46:129428 [INFO]   Found MRCP Engine [GSS-1] for Resource [speechsynth] 0x7f276001a418 <5369649bdd334475>
2020-07-02 10:02:46:129431 [WARN]   Cannot read the first field in start-line
2020-07-02 10:02:46:132887 [INFO]   Enable RTP Session 192.168.86.159:5004
2020-07-02 10:02:46:132926 [INFO]   Open RTP Transmitter 192.168.86.159:5004 -> 10.10.10.120:35085
2020-07-02 10:02:46:132950 [INFO]   Media Path 0x7f276001a418 Source->[LPCM/8000/1]->Bridge->[LPCM/8000/1]->Encoder->[PCMU/8000/1]->Sink
2020-07-02 10:02:46:133133 [INFO]   Open <5369649bdd334475@gss>
2020-07-02 10:02:46:133334 [NOTICE] GSS Usage: 1/1/2
2020-07-02 10:02:46:133436 [INFO]   Send Answer 0x7f276001a418 <5369649bdd334475> [c:0 a:1 v:0] Status OK
2020-07-02 10:02:46:133527 [INFO]   Send RTSP Data 192.168.86.159:1554 <-> 10.10.10.120:51380 [392 bytes]
RTSP/1.0 200 OK
CSeq: 1
Transport: RTP/AVP;unicast;client_port=35085-47360;server_port=5004-5005;mode=record
Session: 5369649bdd334475
Content-Type: application/sdp
Content-Length: 199

v=0
o=UniMRCPServer 0 0 IN IP4 192.168.86.159
s=-
c=IN IP4 192.168.86.159
t=0 0
m=audio 5004 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv

Nathan Cartwright

unread,
Jul 2, 2020, 10:55:12 AM7/2/20
to UniMRCP
Here is the issue just not sure how to resolve. When CCX gets the response it is puking on the input mode that is being sent from the MRCP server. Is there a different way to hit your Welcome intent?

858117: Jul 02 10:35:00.992 EDT %MIVR-SS_MRCP_ASR-7-UNK: [MIVR_ENG_TASKS-31-4-TASK:0x826299e23_vxml_sample.aef] com.cisco.wf.mrcp.asr.channel.impl.MRCPSpeechChannelImpl MRCPSpeechChannel(Channel id:1, Contact id:34, Task id:35000000035): processRecResults(): NLSLM Result is: <?xml version="1.0"?><result><interpretation grammar="session:fo...@dialog.grammar" confidence="100"><instance><query_text>welcome</query_text><action>input.welcome</action><parameters></parameters><all_required_params_present>true</all_required_params_present><fulfillment_text>Good day! What can I do for you today?</fulfillment_text><fulfillment_messages><text><text>Good day! What can I do for you today?</text></text></fulfillment_messages><intent><name>projects/badgerlinkassistant-a918f/agent/intents/d3c1994b-ff27-468c-a291-497893f569f9</name><display_name>Default Welcome Intent</display_name></intent><intent_detection_confidence>1</intent_detection_confidence><language_code>en</language_code><output_audio_uri>http://localhost/utterances/umsgdf-1a8f69fa0f2f43c8-1102.wav</output_audio_uri></instance><input mode="event">welcome</input></interpretation></result>


On Wednesday, July 1, 2020 at 3:23:36 PM UTC-4, Nathan Cartwright wrote:

Arsen Chaloyan

unread,
Jul 11, 2020, 2:13:04 PM7/11/20
to UniMRCP
Your observations are correct, Nathan.

Here is a statement from release notes of GDF 1.15.0 produced back in April which you would need to follow in order to address the problem.

* Added support for an alternate way of triggering a Dialogflow welcome intent by means of 'builtin:grammar/event_welcome' in addition to 'builtin:event/welcome'. The new method is commonly supported by the majority of IVR platforms.

--
You received this message because you are subscribed to the Google Groups "UniMRCP" group.
To unsubscribe from this group and stop receiving emails from it, send an email to unimrcp+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/unimrcp/448a9b79-62a9-4237-90bb-99fb71136c59o%40googlegroups.com.


--
Arsen Chaloyan
Author of UniMRCP
http://www.unimrcp.org
Reply all
Reply to author
Forward
0 new messages