<?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: Text-to-Speech Bonanza with Cepstral and Asterisk 1.4	</title>
	<atom:link href="https://nerdvittles.com/text-to-speech-asterisk-extravaganza/feed/" rel="self" type="application/rss+xml" />
	<link>https://nerdvittles.com/text-to-speech-asterisk-extravaganza/</link>
	<description>Ward Mundy&#039;s Technobabblelog</description>
	<lastBuildDate>Wed, 09 Dec 2015 14:28:19 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Zach		</title>
		<link>https://nerdvittles.com/text-to-speech-asterisk-extravaganza/comment-page-1/#comment-3519</link>

		<dc:creator><![CDATA[Zach]]></dc:creator>
		<pubDate>Wed, 27 Aug 2008 18:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=205#comment-3519</guid>

					<description><![CDATA[I was hoping for some direction / input on where to locate some information for a system we need to setup. The details of the system are as follows:

1) Caller calls into the system and is asked to enter an ID number.
2) ID number is recorded and then a lookup is performed against a MS SQL database for the entered ID number.
3) If the number exists, the caller is then asked to record their name, enter their phone number, record their email address and record any additional details they wish to include.
4) All the recordings above are then stored in the file system (preferably MS Fielsystem, but can work with linux) with a pointer from the MS SQL database to record each individual piece of information. Details they keyed in, such as their telephone number and ID number are stored in database.

The system above will be using Cepstral to read back information they have keyed in for confirmation.

Can someone please point me in the right direction as to where I can locate information on having Piaf connect to a MS SQL database? Also, on where I can locate some information that would explain how the recording could then be played back through a website accessed by customers to hear the information the caller recorded?

Any assistance you could provide me with on this matter is greatly appreciated.]]></description>
			<content:encoded><![CDATA[<p>I was hoping for some direction / input on where to locate some information for a system we need to setup. The details of the system are as follows:</p>
<p>1) Caller calls into the system and is asked to enter an ID number.<br />
2) ID number is recorded and then a lookup is performed against a MS SQL database for the entered ID number.<br />
3) If the number exists, the caller is then asked to record their name, enter their phone number, record their email address and record any additional details they wish to include.<br />
4) All the recordings above are then stored in the file system (preferably MS Fielsystem, but can work with linux) with a pointer from the MS SQL database to record each individual piece of information. Details they keyed in, such as their telephone number and ID number are stored in database.</p>
<p>The system above will be using Cepstral to read back information they have keyed in for confirmation.</p>
<p>Can someone please point me in the right direction as to where I can locate information on having Piaf connect to a MS SQL database? Also, on where I can locate some information that would explain how the recording could then be played back through a website accessed by customers to hear the information the caller recorded?</p>
<p>Any assistance you could provide me with on this matter is greatly appreciated.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: rick nieves		</title>
		<link>https://nerdvittles.com/text-to-speech-asterisk-extravaganza/comment-page-1/#comment-3173</link>

		<dc:creator><![CDATA[rick nieves]]></dc:creator>
		<pubDate>Sun, 02 Mar 2008 09:12:16 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=205#comment-3173</guid>

					<description><![CDATA[In my opinion the 310 sounds more clear and definitely noticeable difference.]]></description>
			<content:encoded><![CDATA[<p>In my opinion the 310 sounds more clear and definitely noticeable difference.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: eufreka		</title>
		<link>https://nerdvittles.com/text-to-speech-asterisk-extravaganza/comment-page-1/#comment-3162</link>

		<dc:creator><![CDATA[eufreka]]></dc:creator>
		<pubDate>Mon, 25 Feb 2008 15:22:41 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=205#comment-3162</guid>

					<description><![CDATA[Okay, they both sounded comparable to me. Both were acceptable, neither was exceptional. I did have to call the 310 number twice before it picked up properly though (first time, just silence).]]></description>
			<content:encoded><![CDATA[<p>Okay, they both sounded comparable to me. Both were acceptable, neither was exceptional. I did have to call the 310 number twice before it picked up properly though (first time, just silence).</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Ed Lally		</title>
		<link>https://nerdvittles.com/text-to-speech-asterisk-extravaganza/comment-page-1/#comment-3157</link>

		<dc:creator><![CDATA[Ed Lally]]></dc:creator>
		<pubDate>Thu, 21 Feb 2008 04:25:33 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=205#comment-3157</guid>

					<description><![CDATA[Hey Ward,

I have to agree with the others.  I retrieved weather by zip code on both numbers, and thought the 678 number was clearer with fewer dropouts.  The 678 number has to be the hosted solution.  I have to say, though, that the 310 number sounded perfectly acceptable for a home-based solution.]]></description>
			<content:encoded><![CDATA[<p>Hey Ward,</p>
<p>I have to agree with the others.  I retrieved weather by zip code on both numbers, and thought the 678 number was clearer with fewer dropouts.  The 678 number has to be the hosted solution.  I have to say, though, that the 310 number sounded perfectly acceptable for a home-based solution.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: JimA		</title>
		<link>https://nerdvittles.com/text-to-speech-asterisk-extravaganza/comment-page-1/#comment-3148</link>

		<dc:creator><![CDATA[JimA]]></dc:creator>
		<pubDate>Sun, 17 Feb 2008 13:07:39 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=205#comment-3148</guid>

					<description><![CDATA[Please disregard my previous comment.  I actually just need to symlink to the swift command and all worked great.  In fact I have all 5 applications working perfectly now on my system.  This is absolutely fantastic stuff.  Way to go!!!]]></description>
			<content:encoded><![CDATA[<p>Please disregard my previous comment.  I actually just need to symlink to the swift command and all worked great.  In fact I have all 5 applications working perfectly now on my system.  This is absolutely fantastic stuff.  Way to go!!!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Brett		</title>
		<link>https://nerdvittles.com/text-to-speech-asterisk-extravaganza/comment-page-1/#comment-3143</link>

		<dc:creator><![CDATA[Brett]]></dc:creator>
		<pubDate>Fri, 15 Feb 2008 17:48:05 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=205#comment-3143</guid>

					<description><![CDATA[310 definately sounds like Comcast.  We experienced the same jitter issues when our PBX was connected to Comcast.

678 is better but the same issue with the call dropping after punching in the zip code.

&lt;i&gt;[WM: See response to Comment #2, above.]&lt;/i&gt;]]></description>
			<content:encoded><![CDATA[<p>310 definately sounds like Comcast.  We experienced the same jitter issues when our PBX was connected to Comcast.</p>
<p>678 is better but the same issue with the call dropping after punching in the zip code.</p>
<p><i>[WM: See response to Comment #2, above.]</i></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Rafael Cortes		</title>
		<link>https://nerdvittles.com/text-to-speech-asterisk-extravaganza/comment-page-1/#comment-3141</link>

		<dc:creator><![CDATA[Rafael Cortes]]></dc:creator>
		<pubDate>Fri, 15 Feb 2008 15:44:08 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=205#comment-3141</guid>

					<description><![CDATA[Hey Ward, I will be using all of this as soon as I take the time to buy me some Cepestral licenses... 
Just to let you know that as of Feb-14-2008 16:00 and again Feb-15-2008 11:30 the 310-862-XXXX gave me a message that the number I&#039;ve called is not in service, please.... I am calling from Puerto Rico using a standard cell phone.
The 678-444-XXXX was working beautiful, and convinced me to get a Cepestral license! I am just hoping for Cepestral to work WELL in spanish some day... some day! 
Have a good one, and have fun at the coming FreePBX Training!]]></description>
			<content:encoded><![CDATA[<p>Hey Ward, I will be using all of this as soon as I take the time to buy me some Cepestral licenses&#8230;<br />
Just to let you know that as of Feb-14-2008 16:00 and again Feb-15-2008 11:30 the 310-862-XXXX gave me a message that the number I&#8217;ve called is not in service, please&#8230;. I am calling from Puerto Rico using a standard cell phone.<br />
The 678-444-XXXX was working beautiful, and convinced me to get a Cepestral license! I am just hoping for Cepestral to work WELL in spanish some day&#8230; some day!<br />
Have a good one, and have fun at the coming FreePBX Training!</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Kevin		</title>
		<link>https://nerdvittles.com/text-to-speech-asterisk-extravaganza/comment-page-1/#comment-3140</link>

		<dc:creator><![CDATA[Kevin]]></dc:creator>
		<pubDate>Thu, 14 Feb 2008 21:18:02 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=205#comment-3140</guid>

					<description><![CDATA[I felt like the 678 number sounded significantly clearer - but I had the same isue with Weather-by-zip that Kevin had. It looks like you&#039;re having the issue that&#039;s been discussed over in the forums, Ward. You&#039;d better go have a look at it!
Jeff

&lt;i&gt;[WM: It was the double whammy that got us. There was a permissions problem. And, after fixing the permissions, if you don&#039;t restart Asterisk, the reports don&#039;t play. All is well... finally.]&lt;/i&gt;]]></description>
			<content:encoded><![CDATA[<p>I felt like the 678 number sounded significantly clearer &#8211; but I had the same isue with Weather-by-zip that Kevin had. It looks like you&#8217;re having the issue that&#8217;s been discussed over in the forums, Ward. You&#8217;d better go have a look at it!<br />
Jeff</p>
<p><i>[WM: It was the double whammy that got us. There was a permissions problem. And, after fixing the permissions, if you don&#8217;t restart Asterisk, the reports don&#8217;t play. All is well&#8230; finally.]</i></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Kevin		</title>
		<link>https://nerdvittles.com/text-to-speech-asterisk-extravaganza/comment-page-1/#comment-3139</link>

		<dc:creator><![CDATA[Kevin]]></dc:creator>
		<pubDate>Thu, 14 Feb 2008 19:02:05 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=205#comment-3139</guid>

					<description><![CDATA[Ward,
 Called both numbers, 310 was OK but got some dropouts, 678 quality was better, but after entering the zip code I wanted the weather for, it says successfully downloaded but then hangs up. You might want to check. Weather report for 310 worked properly.

Kevin]]></description>
			<content:encoded><![CDATA[<p>Ward,<br />
 Called both numbers, 310 was OK but got some dropouts, 678 quality was better, but after entering the zip code I wanted the weather for, it says successfully downloaded but then hangs up. You might want to check. Weather report for 310 worked properly.</p>
<p>Kevin</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
