Does unimrcp support in-band DTMF?

[mayama takeshi]

Hi, from this thread
  https://groups.google.com/g/unimrcp/c/XuxJtxNHxJQ/m/3wwZ2r_9BAAJ

I read:

As for the DTMFs, only RFC2833 DTMFs are currently supported by the GSR plugin, support for in-band DTMFs can be added, if needed

Is still the case that currently in-band DTMF is not supported? (I didn't check the unimrcp code but I tested and it seems it is the case).

Obs: I just need a confirmation, I'm working integrating freeswitch and unimrcp/GSR and if it is not supported I will prepare the DTMF handling at FS.

[Lewis Bergman]

I am new to both Freeswitch and uniMRCP but I think with mod_unimrcp they just kind of expect you to handle all the DTMF in dptools with the IVR functions already present.

--
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/256b5d53-f57d-4c9a-aaea-8ad6bb5183f8n%40googlegroups.com.

--

Lewis Bergman

325-439-0533 Cell

[mayamatakeshi]

Ah, in my case I actually don't need support for in-band DTMF.

I am starting a DTMF detector in FS by calling spandsp_start_dtmf and so when in-band DTMF is detected in the incoming leg, FS would send RFC2833 digits to the unimrcp SIP call.

However, it was not doing this. 

But this was because I didn't enable codec telephone-event in my unimcrp profile.

After changing this:

      <param name="codecs" value="PCMU PCMA L16/96/8000"/>

to this:

    <param name="codecs" value="PCMU PCMA L16/96/8000 telephone-event"/>

the codec telephone-event was offered by FS to unimrcp:

INVITE sip:192.168.88.136:8060 SIP/2.0
Via: SIP/2.0/UDP 192.168.2.137:16090;rport;branch=z9hG4bK96yrKg53X6H2j
Max-Forwards: 70
From: <sip:192.168.2.137:16090>;tag=10tDe66c91H7c
To: <sip:192.168.88.136:8060>
Call-ID: 3da7ea00-fe23-1239-ab88-52540012a6dc
CSeq: 33239861 INVITE
User-Agent: FreeSWITCH
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE
Supported: timer, 100rel
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 387

v=0
o=FreeSWITCH 4975629623509025572 7572976588626830541 IN IP4 192.168.2.137
s=-
c=IN IP4 192.168.2.137
t=0 0
m=application 9 TCP/MRCPv2 1
a=setup:active
a=connection:new
a=resource:speechrecog
a=cmid:1
m=audio 14008 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=sendonly
a=mid:1

And here are the MRCP messages confirming DTMF was detected by unimrcp (at the incoming leg I send in-band DTMF sequence '1234567890'):

MRCP/2.0 300 RECOGNIZE 1
Channel-Identifier: fdd06c05e10c46b4@speechrecog
Content-Type: text/uri-list
Cancel-If-Queue: false
Recognition-Timeout: 10000
Start-Input-Timers: false
Speech-Language: en-US
No-Input-Timeout: 10000
Content-Length: 45

builtin:speech/transcribe
builtin:dtmf/digits



MRCP/2.0 83 1 200 IN-PROGRESS
Channel-Identifier: fdd06c05e10c46b4@speechrecog



MRCP/2.0 113 START-OF-INPUT 1 IN-PROGRESS
Channel-Identifier: fdd06c05e10c46b4@speechrecog
Input-Type: dtmf



MRCP/2.0 396 RECOGNITION-COMPLETE 1 COMPLETE
Channel-Identifier: fdd06c05e10c46b4@speechrecog
Completion-Cause: 000 success
Content-Type: application/x-nlsml
Content-Length: 211

<?xml version="1.0"?>
<result>
<interpretation grammar="builtin:dtmf/digits" confidence="1">
<instance>1234567890</instance>
<input mode="dtmf">1 2 3 4 5 6 7 8 9 0</input>
</interpretation>
</result>

So, everything is fine.

[Lewis Bergman]

Thanks for describing how you got it working. 

--

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/CABaNFCZbR-5JAriGVgkPRgGSKK5DSpsA2zjB59PRVkpZE44ZEg%40mail.gmail.com.