Getting 015 no-match-maxtime from Nuance server

19 views

Skip to first unread message

Sameer Joshi

unread,

Jan 10, 2023, 6:18:11 AM1/10/23

to UniMRCP

Hi All,

I am running the umc client available as part of UniMRCP library.

I am trying to run "recog" scenario in umc client with the latest version 1.8 of library.

ASR server being used is Nuance.

After running the "recog" scenario, I am getting 015-no-match-maxtime from Nuance server in RECOGNIZE result.

I could hear "one" being played out in the RTP audio captured very clearly. Still Nuance responds with 015-no-match-maxtime.

Any clue what could be wrong here? Also, in client-profiles directory I see nuance.xml being present. Can someone tell me how this client-profile is being used ? Does the code include recognition of server its talking to and accordingly load those settings from client-profile?

following are the logs:

2023-01-10 13:12:45:385910 [INFO] Start Task [Framework Agent]
>2023-01-10 13:12:45:389980 [NOTICE] UniMRCP Client [1.8.0]
2023-01-10 13:12:45:389980 [INFO] APR [1.5.2]
2023-01-10 13:12:45:389980 [NOTICE] Create MRCP Client
2023-01-10 13:12:45:389980 [NOTICE] Open Config File [C:\Users\samejoshi\source\repos\unimrcp\unimrcp-1.8.0\unimrcp-1.8.0\x64\Debug\conf\unimrcpclient.xml]
2023-01-10 13:12:45:408004 [INFO] Set Property ip:10.21.40.30
2023-01-10 13:12:45:408004 [INFO] Set Property server-ip:205.214.15.94
2023-01-10 13:12:45:408004 [INFO] Register Codec [PCMU]
2023-01-10 13:12:45:408004 [INFO] Register Codec [PCMA]
2023-01-10 13:12:45:408004 [INFO] Register Codec [L16]
2023-01-10 13:12:45:408004 [INFO] Register Codec [G722]
2023-01-10 13:12:45:408004 [NOTICE] Register Resource [speechsynth]
2023-01-10 13:12:45:408004 [NOTICE] Register Resource [speechrecog]
2023-01-10 13:12:45:408004 [NOTICE] Register Resource [recorder]
2023-01-10 13:12:45:408004 [NOTICE] Register Resource [speakverify]
2023-01-10 13:12:45:408004 [INFO] Register Resource Factory
2023-01-10 13:12:45:408004 [NOTICE] Create SofiaSIP Agent [SIP-Agent-1] [1.12.11-239-g54ef3e2] sip:10.21.40.30:8062;transport=udp
2023-01-10 13:12:45:408004 [INFO] Register Signaling Agent [SIP-Agent-1]
2023-01-10 13:12:45:408004 [NOTICE] Create RTSP Client [RTSP-Agent-1] [100]
2023-01-10 13:12:45:408919 [INFO] Register Signaling Agent [RTSP-Agent-1]
2023-01-10 13:12:45:410982 [NOTICE] Create MRCPv2 Agent [MRCPv2-Agent-1] [100]
2023-01-10 13:12:45:414980 [INFO] Register Connection Agent [MRCPv2-Agent-1]
2023-01-10 13:12:45:414980 [NOTICE] Create Media Engine [Media-Engine-1]
2023-01-10 13:12:45:414980 [INFO] Register Media Engine [Media-Engine-1]
2023-01-10 13:12:45:415889 [NOTICE] Create RTP Termination Factory 10.21.40.30:[4000,5000]
2023-01-10 13:12:45:416223 [INFO] Register RTP Termination Factory [RTP-Factory-1]
2023-01-10 13:12:45:416223 [INFO] Register RTP Settings [RTP-Settings-1]
2023-01-10 13:12:45:416223 [WARN] Missing Required Attribute <id> in Element <sip-settings>
2023-01-10 13:12:45:416223 [INFO] Enter Directory [C:\Users\samejoshi\source\repos\unimrcp\unimrcp-1.8.0\unimrcp-1.8.0\x64\Debug\conf\client-profiles]
2023-01-10 13:12:45:417248 [NOTICE] Open Config File [C:\Users\samejoshi\source\repos\unimrcp\unimrcp-1.8.0\unimrcp-1.8.0\x64\Debug\conf\client-profiles\lumenvox.xml]
2023-01-10 13:12:45:418250 [INFO] Create SIP Settings 205.214.15.94:5060
2023-01-10 13:12:45:418250 [INFO] Register Signaling Settings [LumenVox-SIP-Settings]
2023-01-10 13:12:45:418250 [INFO] Create RTSP Settings 205.214.15.94:554
2023-01-10 13:12:45:418250 [INFO] Register Signaling Settings [LumenVox-RTSP-Settings]
2023-01-10 13:12:45:418250 [NOTICE] Create MRCPv2 Profile [lv2]
2023-01-10 13:12:45:418250 [INFO] Register Profile [lv2]
2023-01-10 13:12:45:418250 [NOTICE] Create MRCPv1 Profile [lv1]
2023-01-10 13:12:45:418250 [INFO] Register Profile [lv1]
2023-01-10 13:12:45:418250 [NOTICE] Open Config File [C:\Users\samejoshi\source\repos\unimrcp\unimrcp-1.8.0\unimrcp-1.8.0\x64\Debug\conf\client-profiles\nuance.xml]
2023-01-10 13:12:45:419246 [INFO] Create SIP Settings 205.214.15.94:5060
2023-01-10 13:12:45:419246 [INFO] Register Signaling Settings [Nuance-SIP-Settings]
2023-01-10 13:12:45:419246 [INFO] Create RTSP Settings 205.214.15.94:4900
2023-01-10 13:12:45:419246 [INFO] Register Signaling Settings [Nuance-RTSP-Settings]
2023-01-10 13:12:45:419246 [INFO] Register RTP Settings [Nuance-RTP-Settings]
2023-01-10 13:12:45:419246 [NOTICE] Create MRCPv2 Profile [nss2]
2023-01-10 13:12:45:419246 [INFO] Register Profile [nss2]
2023-01-10 13:12:45:419246 [NOTICE] Create MRCPv1 Profile [nss1]
2023-01-10 13:12:45:419246 [INFO] Register Profile [nss1]
2023-01-10 13:12:45:419246 [NOTICE] Open Config File [C:\Users\samejoshi\source\repos\unimrcp\unimrcp-1.8.0\unimrcp-1.8.0\x64\Debug\conf\client-profiles\speechpro.xml]
2023-01-10 13:12:45:420246 [INFO] Create RTSP Settings 205.214.15.94:8000
2023-01-10 13:12:45:420246 [INFO] Register Signaling Settings [SpeechPro-RTSP-Settings]
2023-01-10 13:12:45:421246 [NOTICE] Create MRCPv1 Profile [sp1]
2023-01-10 13:12:45:421246 [INFO] Register Profile [sp1]
2023-01-10 13:12:45:421246 [NOTICE] Open Config File [C:\Users\samejoshi\source\repos\unimrcp\unimrcp-1.8.0\unimrcp-1.8.0\x64\Debug\conf\client-profiles\unimrcp.xml]
2023-01-10 13:12:45:422248 [INFO] Create SIP Settings 205.214.15.94:5060
2023-01-10 13:12:45:422248 [INFO] Register Signaling Settings [UniMRCP-SIP-Settings]
2023-01-10 13:12:45:422248 [INFO] Create RTSP Settings 205.214.15.94:1554
2023-01-10 13:12:45:423246 [INFO] Register Signaling Settings [UniMRCP-RTSP-Settings]
2023-01-10 13:12:45:423246 [NOTICE] Create MRCPv2 Profile [uni2]
2023-01-10 13:12:45:423246 [INFO] Register Profile [uni2]
2023-01-10 13:12:45:423246 [NOTICE] Create MRCPv1 Profile [uni1]
2023-01-10 13:12:45:427713 [INFO] Register Profile [uni1]
2023-01-10 13:12:45:428698 [INFO] Leave Directory [C:\Users\samejoshi\source\repos\unimrcp\unimrcp-1.8.0\unimrcp-1.8.0\x64\Debug\conf]
2023-01-10 13:12:45:428698 [NOTICE] Create Application
2023-01-10 13:12:45:429701 [INFO] Register Application [UMC]
2023-01-10 13:12:45:429701 [INFO] Start Task [MRCP Client]
2023-01-10 13:12:45:431154 [INFO] Start Task [SIP-Agent-1]
2023-01-10 13:12:45:431154 [INFO] Start Task [RTSP-Agent-1]
2023-01-10 13:12:45:431154 [INFO] Start Task [MRCPv2-Agent-1]
2023-01-10 13:12:45:431798 [INFO] Start Task [Media-Engine-1]
Adding nameserver: 205.214.10.211
Adding nameserver: 205.214.10.212
Adding nameserver: 192.168.1.1
2023-01-10 13:12:45:447406 [NOTICE] MRCP Client Started
2023-01-10 13:12:45:447406 [INFO] Enter Directory [C:\Users\samejoshi\source\repos\unimrcp\unimrcp-1.8.0\unimrcp-1.8.0\x64\Debug\conf\umc-scenarios]
2023-01-10 13:12:45:449645 [INFO] Load Scenario Name [dtmf] Class [DtmfRecognizer]
2023-01-10 13:12:45:449645 [INFO] Load Scenario Name [recog] Class [Recognizer]
2023-01-10 13:12:45:451618 [INFO] Load Scenario Name [params] Class [Params]
2023-01-10 13:12:45:452618 [INFO] Load Scenario Name [rec] Class [Recorder]
2023-01-10 13:12:45:452618 [INFO] Load Scenario Name [synth] Class [Synthesizer]
2023-01-10 13:12:45:453618 [INFO] Load Scenario Name [verify] Class [Verifier]
run recog
>[1]
2023-01-10 13:12:49:288704 [NOTICE] Create MRCP Handle 0x1fc0a2b43a0 [uni2]
2023-01-10 13:12:49:291734 [INFO] Create Channel umc-1 <new>
2023-01-10 13:12:49:291734 [INFO] Receive App Request umc-1 <new> [2]
2023-01-10 13:12:49:292705 [INFO] Add MRCP Handle umc-1 <new>
2023-01-10 13:12:49:292705 [NOTICE] Add Control Channel umc-1 <new@speechrecog>
2023-01-10 13:12:49:301853 [INFO] Send Offer umc-1 <new> [c:1 a:1 v:0] to 205.214.15.94:5060
2023-01-10 13:12:49:301853 [INFO] Local SDP umc-1 <new>
v=0
o=UniMRCPClient 0 0 IN IP4 10.21.40.30
s=-
c=IN IP4 10.21.40.30
t=0 0
m=application 9 TCP/MRCPv2 1
a=setup:active
a=connection:new
a=resource:speechrecog
a=cmid:1
m=audio 4000 RTP/AVP 0 8 9 96 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:9 G722/8000
a=rtpmap:96 L16/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendonly
a=ptime:20
a=mid:1

2023-01-10 13:12:49:309732 [INFO] Receive SIP Event [nua_i_state] Status 0 INVITE sent [SIP-Agent-1]
2023-01-10 13:12:49:309732 [NOTICE] SIP Call State umc-1 [calling]
2023-01-10 13:12:49:652825 [INFO] Receive SIP Event [nua_r_invite] Status 200 OK [SIP-Agent-1]
2023-01-10 13:12:49:653839 [INFO] Receive SIP Event [nua_i_state] Status 200 OK [SIP-Agent-1]
2023-01-10 13:12:49:656120 [NOTICE] SIP Call State umc-1 [ready]
2023-01-10 13:12:49:661081 [INFO] Remote SDP umc-1 <new>
v=0
o=- 1673336569 1673336569 IN IP4 205.214.15.94
s=Nuance MRCP session V2
c=IN IP4 205.214.15.94
t=0 0
a=session-timeout:600000
m=application 6075 TCP/MRCPv2 1
a=cmid:1
a=setup:passive
a=connection:new
a=channel:1945@speechrecog
m=audio 8418 RTP/AVP 0 8 96 101
a=rtpmap:0 pcmu/8000
a=rtpmap:8 pcma/8000
a=rtpmap:96 l16/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=recvonly
a=ptime:20
a=mid:1

2023-01-10 13:12:49:663293 [INFO] Receive Answer umc-1 <new> [c:1 a:1 v:0] Status 200
2023-01-10 13:12:49:663293 [INFO] Receive SIP Event [nua_i_active] Status 200 Call active [SIP-Agent-1]
2023-01-10 13:12:49:672693 [INFO] Enable RTP Session 10.21.40.30:4000
2023-01-10 13:12:49:672693 [INFO] Open RTP Transmitter 10.21.40.30:4000 -> 205.214.15.94:8418
2023-01-10 13:12:49:674675 [INFO] Media Path umc-1 Source->[LPCM/8000/1]->Bridge->[LPCM/8000/1]->Encoder->[PCMU/8000/1]->Sink
2023-01-10 13:12:49:919177 [NOTICE] Established TCP/MRCPv2 Connection 10.21.40.30:58599 <-> 205.214.15.94:6075
2023-01-10 13:12:49:920178 [INFO] Add Control Channel <1945@speechrecog> 10.21.40.30:58599 <-> 205.214.15.94:6075 [1]
2023-01-10 13:12:49:922180 [INFO] Raise App Response umc-1 <1945> [2] SUCCESS [0]
2023-01-10 13:12:49:925255 [INFO] Receive App MRCP Request umc-1 <1945>
2023-01-10 13:12:49:926311 [INFO] Send MRCP Request umc-1 <1945@speechrecog> [1]
2023-01-10 13:12:49:927312 [INFO] Send MRCPv2 Data 10.21.40.30:58599 <-> 205.214.15.94:6075 [439 bytes]
MRCP/2.0 439 DEFINE-GRAMMAR 1
Channel-Identifier: 1945@speechrecog
Content-Type: application/srgs+xml
Content-Id: request1@form-level
Content-Length: 278

<?xml version="1.0"?>
<grammar xmlns="http://www.w3.org/2001/06/grammar" xml:lang="en-US" version="1.0" mode="voice" root="digit">
<rule id="digit">
<one-of>
<item>one</item>
<item>two</item>
<item>three</item>
</one-of>
</rule>
</grammar>
2023-01-10 13:12:50:202117 [INFO] Receive MRCPv2 Data 10.21.40.30:58599 <-> 205.214.15.94:6075 [68 bytes]
MRCP/2.0 68 1 200 COMPLETE
Channel-Identifier: 1945@speechrecog

2023-01-10 13:12:50:202117 [INFO] Raise App MRCP Response umc-1 <1945>
2023-01-10 13:12:50:203136 [INFO] Receive App MRCP Request umc-1 <1945>
2023-01-10 13:12:50:204119 [INFO] Set [C:\Users\samejoshi\source\repos\unimrcp\unimrcp-1.8.0\unimrcp-1.8.0\x64\Debug\data\one-8kHz.pcm] as Speech Source
2023-01-10 13:12:50:206120 [INFO] Send MRCP Request umc-1 <1945@speechrecog> [2]
2023-01-10 13:12:50:207121 [INFO] Send MRCPv2 Data 10.21.40.30:58599 <-> 205.214.15.94:6075 [292 bytes]
MRCP/2.0 292 RECOGNIZE 2
Channel-Identifier: 1945@speechrecog
Content-Type: text/uri-list
Cancel-If-Queue: false
No-Input-Timeout: 5000
Recognition-Timeout: 10000
Start-Input-Timers: true
Confidence-Threshold: 0.5
Save-Waveform: true
Content-Length: 27

session:request1@form-level
2023-01-10 13:12:50:483583 [INFO] Receive MRCPv2 Data 10.21.40.30:58599 <-> 205.214.15.94:6075 [71 bytes]
MRCP/2.0 71 2 200 IN-PROGRESS
Channel-Identifier: 1945@speechrecog

2023-01-10 13:12:50:483583 [INFO] Raise App MRCP Response umc-1 <1945>
2023-01-10 13:12:51:378506 [INFO] Receive MRCPv2 Data 10.21.40.30:58599 <-> 205.214.15.94:6075 [138 bytes]
MRCP/2.0 138 START-OF-INPUT 2 IN-PROGRESS
Channel-Identifier: 1945@speechrecog
Proxy-Sync-Id: 0-1945@speechrecog
Input-Type: speech

2023-01-10 13:12:51:379091 [INFO] Raise App MRCP Event umc-1 <1945>
2023-01-10 13:13:01:401788 [INFO] Receive MRCPv2 Data 10.21.40.30:58599 <-> 205.214.15.94:6075 [319 bytes]
MRCP/2.0 319 RECOGNITION-COMPLETE 2 COMPLETE
Channel-Identifier: 1945@speechrecog
Waveform-URI: <http://ENG-INASR02:90/Nuance/callLogs/MyApp/2023/01January/10/00/NUAN-42-49-ENG-INASR02-38e71832-0b5d-123c-af92-1d28a3171fb2-utt001-SAVEWAVEFORM.wav>; size=12524; duration=1560
Completion-Cause: 015 no-match-maxtime

2023-01-10 13:13:01:401788 [INFO] Raise App MRCP Event umc-1 <1945>
2023-01-10 13:13:01:403789 [WARN] No NLSML data available
2023-01-10 13:13:01:404789 [INFO] Receive App Request umc-1 <1945> [1]
2023-01-10 13:13:01:406419 [INFO] Terminate Session umc-1 <1945>
2023-01-10 13:13:01:407322 [INFO] Remove Control Channel <1945@speechrecog> [0]
2023-01-10 13:13:01:407322 [INFO] Close TCP/MRCPv2 Connection 10.21.40.30:58599 <-> 205.214.15.94:6075
2023-01-10 13:13:01:412595 [INFO] Close RTP Transmitter 10.21.40.30:4000 -> 205.214.15.94:8418 [s:101 o:16160]
2023-01-10 13:13:01:413603 [INFO] Remove RTP Session 10.21.40.30:4000
2023-01-10 13:13:01:869933 [INFO] Receive SIP Event [nua_r_bye] Status 200 OK [SIP-Agent-1]
2023-01-10 13:13:01:869933 [INFO] Receive SIP Event [nua_i_state] Status 200 to BYE [SIP-Agent-1]
2023-01-10 13:13:01:870954 [NOTICE] SIP Call State umc-1 [terminated]
2023-01-10 13:13:01:872934 [INFO] Session Terminated umc-1 <1945>
2023-01-10 13:13:01:872934 [NOTICE] Destroy TCP/MRCPv2 Connection 10.21.40.30:58599 <-> 205.214.15.94:6075
2023-01-10 13:13:01:872934 [INFO] Remove MRCP Handle umc-1 <1945>
2023-01-10 13:13:01:873933 [INFO] Raise App Response umc-1 <1945> [1] SUCCESS [0]
2023-01-10 13:13:01:873933 [NOTICE] Destroy MRCP Handle umc-1

Thanks,

Sameer Joshi

unread,

Jan 10, 2023, 6:25:23 AM1/10/23

to UniMRCP

I tried to look into details further and I observed there are different profiles of clients we can run using third parameter to run command.

like "run recog nss2" is for nuance with MRCPv2.

After using this profile, it worked. I see the difference being RTCP bye being sent now, which was not sent earlier.

I think Nuance server needs RTCP bye or some period of silence after the speech to recognize the speech.

Since the umc tool stops sending packets and does not send required amount of silence for Nuance, it replies with no-match-maxtime as seen earlier.

After using nss2 profile of client , things are working fine.

Regards,

Sameer Joshi

Arsen Chaloyan

unread,

Jan 26, 2023, 6:49:52 PM1/26/23

to uni...@googlegroups.com

> After using this profile, it worked. I see the difference being RTCP bye being sent now, which was not sent earlier.

Right.

> Since the umc tool stops sending packets and does not send required amount of silence for Nuance, it replies with no-match-maxtime as seen earlier.

Right. The RTCP Bye will not be required if there is "sufficient" trailing silence in the utterance.

--
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/8ee407bd-2c61-4dc7-84ee-97f3de3e9963n%40googlegroups.com.