<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Opus Research &#187; PerSay</title>
	<atom:link href="http://opusresearch.net/wordpress/tag/persay/feed/" rel="self" type="application/rss+xml" />
	<link>http://opusresearch.net/wordpress</link>
	<description>Analysis and Expertise on Voice Services and Recombinant Communications</description>
	<lastBuildDate>Thu, 29 Jul 2010 23:57:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Vodafone Turkey Offers Customers Voice Biometric-Based Authentication</title>
		<link>http://opusresearch.net/wordpress/2009/06/23/vodafone-turkey-offers-customers-voice-biometric-based-authentication/</link>
		<comments>http://opusresearch.net/wordpress/2009/06/23/vodafone-turkey-offers-customers-voice-biometric-based-authentication/#comments</comments>
		<pubDate>Tue, 23 Jun 2009 16:20:34 +0000</pubDate>
		<dc:creator>Dan Miller</dc:creator>
				<category><![CDATA[CAT Scans]]></category>
		<category><![CDATA[Opus Research]]></category>
		<category><![CDATA[PerSay]]></category>
		<category><![CDATA[secure customer care]]></category>
		<category><![CDATA[Vodafone]]></category>
		<category><![CDATA[voice biometrics. caller authentication]]></category>
		<category><![CDATA[voice portal]]></category>

		<guid isPermaLink="false">http://opusresearch.net/wordpress/?p=841</guid>
		<description><![CDATA[Vodafone Turkey is introducing caller authentication as part of its customer care strategy. PerSay provides the biometric engine which is baked into the Vodafone Voice Portal Platform by Turkish speech VAR SPEECHOUSE.]]></description>
			<content:encoded><![CDATA[<p><img src="http://opusresearch.net/wordpress/wp-content/uploads/2009/06/Picture-2.png" alt="Vodafone" title="Vodafone" width="112" height="108" class="alignleft size-full wp-image-844" />The adoption of voiceprints to authenticate wireless subscribers is accelerating, thanks to a new installation of PerSay&#8217;s VocalPassword(TM) developed and installed by Turkish speech application specialist SPEECHOUSE at Vodafone Turkey. With roughly 16 million subscribers, Vodafone Turkey is the second largest mobile carrier in the country. Yet, if past is prologue, the incorporation of voice authentication into the customer care fabric of any Vodafone subsidiary is bound to have implications across all of its properties &#8211; an empire of over 300 million customers. </p>
<p><img src="http://opusresearch.net/wordpress/wp-content/uploads/2009/06/Picture-11.png" alt="Picture 1" title="Picture 1" width="143" height="70" class="alignright size-full wp-image-843" />The deployment as a milestone in a couple of respects. The mobile market holds huge potential for speaker authentication for customer care and electronic payments. In addition, Vodafone Turkey clearly sees subscriber authentication as a source of differentiation in a long-standing battle for share versus Turkcell. In that pursuit, SPEECHOUSE has successfully integrated speaker authentication into the IVR-based Vodafone Voice Portal Platform. The immediate result is the use of a spoken password for secure self service applications the mobile equivalent of password reset,  GSM PUK (Personal Unlocking Key) reset.</p>
<p>We&#8217;ll be learning more about the details and timing of the complete in the coming days to include in an advisory, and in our long-standing set of company and deployment dossiers.</p>
]]></content:encoded>
			<wfw:commentRss>http://opusresearch.net/wordpress/2009/06/23/vodafone-turkey-offers-customers-voice-biometric-based-authentication/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
