<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: The Ultimate Voice Dialer for Asterisk and Incredible PBX	</title>
	<atom:link href="https://nerdvittles.com/the-ultimate-voice-dialer-for-asterisk-and-incredible-pbx/feed/" rel="self" type="application/rss+xml" />
	<link>https://nerdvittles.com/the-ultimate-voice-dialer-for-asterisk-and-incredible-pbx/</link>
	<description>Ward Mundy&#039;s Technobabblelog</description>
	<lastBuildDate>Thu, 01 Nov 2018 17:43:18 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: drgeoff		</title>
		<link>https://nerdvittles.com/the-ultimate-voice-dialer-for-asterisk-and-incredible-pbx/comment-page-1/#comment-175615</link>

		<dc:creator><![CDATA[drgeoff]]></dc:creator>
		<pubDate>Fri, 13 Oct 2017 18:26:20 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=23713#comment-175615</guid>

					<description><![CDATA[I think that 5% rate is totally misleading in this situation.  Maybe it can do that on connected speech but a person or company name doesn&#039;t give it enough context.  And it cannot distinguish between eg &quot;Geoff&quot; and &quot;Jeff&quot;. That is useless when trying to match the textual names in Asteridex.  (Even a human with no input other than hearing the word cannot know if &quot;Geoff&quot; or &quot;Jeff&quot; was intended.)

And even if it could achieve that 5% error rate, that would still be annoyingly high.  My old mobile phone does a good job of voice dialing because it doesn&#039;t do STT followed by a text match.  It does a fuzzy match on the spoken audio signal against the set of previously recorded spoken audio signals constructed as each name was added to the contact database.

&lt;i&gt;[WM: Your approach would certainly work. I&#039;m not aware of that many smartphones that actually store audio clips linked to phonebook entries. However, we&#039;ve had excellent results with AsteriDex queries just using a plain-text database. The simple answer to your &quot;Geoff&quot; or &quot;Jeff&quot; issue is to actually try a call, watch the Asterisk CLI, and see which spelling the STT engine returns. Then simply adjust the AsteriDex entry accordingly. For most users, there are probably a handful of these entries to work through so it&#039;s really not a showstopper. And our success rate far exceeds the 95% threshold mentioned in our article.]&lt;/i&gt;]]></description>
			<content:encoded><![CDATA[<p>I think that 5% rate is totally misleading in this situation.  Maybe it can do that on connected speech but a person or company name doesn&#8217;t give it enough context.  And it cannot distinguish between eg "Geoff" and "Jeff". That is useless when trying to match the textual names in Asteridex.  (Even a human with no input other than hearing the word cannot know if "Geoff" or "Jeff" was intended.)</p>
<p>And even if it could achieve that 5% error rate, that would still be annoyingly high.  My old mobile phone does a good job of voice dialing because it doesn&#8217;t do STT followed by a text match.  It does a fuzzy match on the spoken audio signal against the set of previously recorded spoken audio signals constructed as each name was added to the contact database.</p>
<p><i>[WM: Your approach would certainly work. I&#8217;m not aware of that many smartphones that actually store audio clips linked to phonebook entries. However, we&#8217;ve had excellent results with AsteriDex queries just using a plain-text database. The simple answer to your "Geoff" or "Jeff" issue is to actually try a call, watch the Asterisk CLI, and see which spelling the STT engine returns. Then simply adjust the AsteriDex entry accordingly. For most users, there are probably a handful of these entries to work through so it&#8217;s really not a showstopper. And our success rate far exceeds the 95% threshold mentioned in our article.]</i></p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
