<div dir="auto">Thanks, Gohar! Very good questions:<div dir="auto"><br></div><div dir="auto">1. Module relies on RFC2833 (DTMF Events). No in-band decoding is implemented at the moment.</div><div dir="auto"><br></div><div dir="auto">2. Module is observer-only for now. It doesn't try to block or in any way alter the RTP stream being forwarded. Hovewer, that might be something to consider as a next step, in fact it might be almost trivial to replace the actual digits with some junk.</div><div dir="auto"><br></div><div dir="auto">Our goal with this initial release was to provide something that could be immediately useful and unblock OpenSIPS work in this area. Big part of the effort went to refine and build up interfaces on rtpproxy side to make future development easier for this functionality as well as allow us and others implementing various packet-processing options (i.e. bridge_srtp certainly high on priority list). Also, the module infrastructure is decoupled from the core, so it should allow using all kinds of crazy external code libraries (DSP, voice recognition etc), without compromising our core integrity when the functionality is not used.</div><div dir="auto"><br></div><div dir="auto">-Max</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu., May 14, 2020, 7:25 p.m. Gohar Ahmed, <<a href="mailto:scribedfor@gmail.com">scribedfor@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">Hi,<div dir="auto">That's big news indeed. Quick question though, is it capable of capturing inband DTMF and possibly drop them ? </div><div dir="auto"><br></div><div dir="auto">Looking forward for next episode of SIP chronicles. </div><div dir="auto"><br></div><div dir="auto">Best Regards,</div><div dir="auto">Gohar Ahmed</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu., May 14, 2020, 9:10 p.m. Maxim Sobolev, <<a href="mailto:sobomax@sippysoft.com" target="_blank" rel="noreferrer">sobomax@sippysoft.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr" data-smartmail="gmail_signature"><div dir="ltr">Hi Razvan & OpenSIPS-users,</div><div dir="ltr"><br></div><div>This is just a quick heads up about catch_dtmf functionality being available in the rtpproxy/master effective immediately. It is needed for the DTMF call control feature in OpenSIPS 3.1. The only difference between it and rtpp_2_1_dtmf code is that in order to enable the feature in master one needs to load catch_dtmf module either by using "--dso /some/where/rtpp_catch_dtmf.so" or by providing configuration file with catch_dtmf section in modules:</div><div><br></div><div>modules {<br>[...]</div><div> catch_dtmf {<br> load = /some/where/rtpp_catch_dtmf.so<br> }<br>}<br></div><div><br></div><div>The module code has been developed in collab with Razvan + sponsored by the OpenSIPS Solutions and comes with the test case providing 95% coverage*. Any feedback is highly appeciated, as usually, happy DTMF'ing!</div><div><br></div><div>-Max</div><div>*) <a href="https://coveralls.io/builds/30800066/source?filename=modules/catch_dtmf/rtpp_catch_dtmf.c" rel="noreferrer noreferrer" target="_blank">https://coveralls.io/builds/30800066/source?filename=modules/catch_dtmf/rtpp_catch_dtmf.c</a></div></div></div>
<p></p>
-- <br>
You received this message because you are subscribed to the Google Groups "rtpproxy" group.<br>
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:rtpproxy+unsubscribe@googlegroups.com" rel="noreferrer noreferrer" target="_blank">rtpproxy+unsubscribe@googlegroups.com</a>.<br>
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/rtpproxy/CAH7qZfuucLr2TYrYFT6X%2B9WL%3D7xay7pJsExUxAhp5gb4UL5%2Bsg%40mail.gmail.com?utm_medium=email&utm_source=footer" rel="noreferrer noreferrer" target="_blank">https://groups.google.com/d/msgid/rtpproxy/CAH7qZfuucLr2TYrYFT6X%2B9WL%3D7xay7pJsExUxAhp5gb4UL5%2Bsg%40mail.gmail.com</a>.<br>
</blockquote></div>
</blockquote></div>