<?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>IVR World &#187; legacy ivrs</title>
	<atom:link href="http://www.ivrsworld.com/tag/legacy-ivrs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ivrsworld.com</link>
	<description>IVR, Interactive Voice Response System, CTI Applications</description>
	<lastBuildDate>Fri, 10 Feb 2012 09:25:15 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Legacy IVR or VoiceXML based IVRS</title>
		<link>http://www.ivrsworld.com/legacy-ivrs/legacy-ivr-or-voicexml-based-ivrs/</link>
		<comments>http://www.ivrsworld.com/legacy-ivrs/legacy-ivr-or-voicexml-based-ivrs/#comments</comments>
		<pubDate>Sat, 13 Jun 2009 06:39:22 +0000</pubDate>
		<dc:creator>Uttam Pegu</dc:creator>
				<category><![CDATA[legacy ivrs]]></category>
		<category><![CDATA[voicexml]]></category>
		<category><![CDATA[clinical trial ivrs]]></category>
		<category><![CDATA[configuring ss7]]></category>
		<category><![CDATA[dialogic boards]]></category>
		<category><![CDATA[digium board]]></category>
		<category><![CDATA[IVR Software]]></category>
		<category><![CDATA[ivrs]]></category>
		<category><![CDATA[ivrs software]]></category>
		<category><![CDATA[medical IVRS]]></category>
		<category><![CDATA[ss7]]></category>
		<category><![CDATA[synway boards]]></category>
		<category><![CDATA[telecom switch]]></category>
		<category><![CDATA[voice portal]]></category>

		<guid isPermaLink="false">http://www.ivrsworld.com/?p=356</guid>
		<description><![CDATA[Whats is legacy IVRS and what is VoiceXML based IVR System ? Legacy IVRS Legacy IVRS can be defined as the IVR Software installed on a personal computer and is developed using available native CTI Card APIs. The IVR software is developed for one CTI brand and model and the IVR Software may not work [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><strong>Whats is legacy IVRS and what is VoiceXML based <a href="http://www.ivrsworld.com">IVR System</a> ?</strong></p>
<p><strong>Legacy IVRS</strong><br />
Legacy IVRS can be defined as the IVR Software installed on a personal computer and is developed using available native CTI Card APIs. The IVR software is developed for one CTI brand and model and the IVR Software may not work for any other CTI board or even model. Also, this type of IVR Software depends on the telephony interface used between CTI board and telephone exchange.<br />
   Legacy IVR software is supposed to control both the telephone interface part as well as VUI ( Voice User Interface). IVR software developer is supposed to be well versed with API provided by one particular CTI board as well as knowledgeable in switch technologies. Legacy IVR software performs every functionality in a interactive voice response system.</p>
<p><strong>VoiceXML based IVRS</strong><br />
VoiceXML based IVR software can be defined as those IVR software which are written in <a href="http://www.voicexml.com">VoiceXML</a>.  They normally deal with VUI(Voice User Interface) part of a interactive voice response system. VoiceXMX based IVR Software are neither dependent on CTI board/CTI Model nor interface with telephone switch. Any hardware interaction is performed by VoiceXML interpreter.<br />
    VoiceXML based IVR applications mainly deal with call flow of the IVRS. So, to write a VoiceXML based IVR software one may not require to know about CTI boards or any telecom switch!</p>
<p><strong>Comparison</strong><br />
Both legacy IVRS and VoiceXML based IVRS have their own advantages and disadvantages. Though recently, many IVR companies are moving towards voiceXML based IVRS, there are still many die-hard legacy IVRS fans including me. Here I am trying to compare between legacy IVRS and voiceXML mased IVRS:<br />
<span id="more-356"></span><br />
1. It is not easy to change call flow in a legacy IVR Software due to its strict dependence on CTI hardware used. But since VoiceXML based IVRS is independent of CTI boards, the call change is easy.</p>
<p>2. Programming in legacy IVRS is dependent on the CTI board, vendor and even model as well as the interface with telecom switch, but in case of VoiceXML, it is not dependent on those hardware.</p>
<p>3. VoiceXML based IVRS is much easier to develop as it is more like HTML for web portals and rightly they are said to be voice portals. Legacy IVRS is more difficult to develop as one has to learn about CTI board, its APIs and also its interfacing with telecom switch.</p>
<p>4. VoiceXML based IVRS is independent of operating systems used while legacy IVRS is dependent on operating system used.</p>
<p>5. VoiceXML is standard with fixed syntax. While legacy IVRS is not standardised in a sense that they are developed in wide variety of computer languages and platforms. Some use C++, some VB, some C language. Coding style may differ from one developer to another making it difficult for third-party to improve on a existing legacy IVRS.</p>
<p>Though, while developing VoiceXML based IVRS, one may not be dependent on CTI board or Telephony Interface used, but this is an disadvantage for a developer. They will be hostage to the VoiceXML interpreter. With many CTI manufacturer with various specification, it may not be easy for one VoiceXML interpreter to work on all CTI boards!  So, it may not be correct to say that VoiceXML is totally independent of CTI boards.</p>
<p>In a legacy IVRS, developer has complete control of the software. So it is much easier in legacy IVRS to ingerate the IVR software with any other application which may not be possible in case of VoiceXML based IVRS. For example, in a call center, if there is already an existing CRM software and IVRS needs to be integrated with it, then most probably, VoiceXML based IVRS may not be able to integrate, but legacy IVRS can easily be integrated.</p>
<p>Both legacy and voiceXML has advantages and disadvantages. It will be wise to choose one among them as per requirements and usage. In some cases, voiceXML based IVRS may be better ( for example Voice Portal) while in scientific or specific application like medical applications, legacy IVRS is better suited.</p>
<p>My personal opinions.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ivrsworld.com/legacy-ivrs/legacy-ivr-or-voicexml-based-ivrs/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>IVRS Jargon and Glossary</title>
		<link>http://www.ivrsworld.com/ivrs-tips/ivrs-jargons-and-glossary/</link>
		<comments>http://www.ivrsworld.com/ivrs-tips/ivrs-jargons-and-glossary/#comments</comments>
		<pubDate>Sat, 09 May 2009 10:49:45 +0000</pubDate>
		<dc:creator>Uttam Pegu</dc:creator>
				<category><![CDATA[IVRS Tips]]></category>
		<category><![CDATA[crbt]]></category>
		<category><![CDATA[cti board]]></category>
		<category><![CDATA[dialogic]]></category>
		<category><![CDATA[ivr jargon]]></category>
		<category><![CDATA[ivrs]]></category>
		<category><![CDATA[ivrs in india]]></category>
		<category><![CDATA[ivrs jargin]]></category>
		<category><![CDATA[ivrs world]]></category>
		<category><![CDATA[legacy ivrs]]></category>
		<category><![CDATA[voice portal]]></category>
		<category><![CDATA[voicexml]]></category>

		<guid isPermaLink="false">http://www.ivrsworld.com/?p=347</guid>
		<description><![CDATA[There are many jargon used in IVRS World! When two IVR professionals discuss IVR Application or IVR Integration with EPABX or switches, most probably, many people as well as beginners in IVRS field might just be totally clueless what they might be blabbering! So I am compiling jargon related to IVRS (Interactive Voice response System). [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>There are many <a href="http://en.wikipedia.org/wiki/Jargon">jargon</a> used in IVRS World! When two IVR professionals discuss IVR Application or IVR Integration with EPABX or switches, most probably, many people as well as beginners in IVRS field might just be totally clueless what they might be blabbering! So I am compiling jargon related to IVRS (<a href="http://www.ivrsworld.com">Interactive Voice response System</a>).</p>
<p>1. IVR/IVRS : Interactive Voice Response System. This blog is all about IVRS.<br />
2. CTI : Computer Telephony Integration, IVRS is a CTI application. Some variants of CTI are CTI Application, CTI Board, CTI Cards, CTI Hardware.<br />
3. EPABX/SWITCH : EPABX stands for Electronic Private Automatic Branch Exchange. Another version is PABX ( Private Automatic Branch Exchange). Switch is same as EPABX but switch is much bigger, many more features.In fact it may not be right thing to compare EPABX and Switch. But IVRS has a very close relationship with them.<br />
4. DIALOGIC : It is name of the company who is undisputed leader is CTI boards. It is almost synonymous with IVRS.<br />
5. ISDN PRI  : Integrated Services Digital Network Primary Rate Interface. It is an interfacing protocol between CTI Boards with EPABX/Switch.<br />
<span id="more-347"></span>6. ANI/CLI : Automatic Number Identification, Caller Line Identification. IVR Software can detect who is calling it! Other versions are : Caller ID, CLIP.<br />
7. R2MF : R2 Line Signaling Multiple Frequency. It is another interfacing protocol between IVRS and Switch/EPABX. use of this interface is on decline.<br />
8. DTMF : Dual Tone Multiple Frequency, used to choose option in IVRS by a caller.<br />
9. VUI : Voice User Interface &#8211; It is the communication medium between human and IVRS by use of speech recognition or DTMF.<br />
10. SS7 : Signaling System 7: Variant : CCS7. Most widely used interfacing protocol between IVRS and Switch. It has many advantages over other interfacing protocols as it gives more control  as well as more information to the IVR Software. It gives IVR Developers more opportunities to develop varieties of IVR Applications to suit many industries. Normally SS7 CTI boards are costlier.<br />
11.  Inbound : Normally it means incoming calls to IVRS like inbound IVRS, when user calls in to the IVRS, it is an inbound IVRS.<br />
12. Outbound : IVRS making outgoing calls to people. IVRS making outgoing calls to people and announce some news alerts, urge for vote a candidate in elections.<br />
13.  E1 : E1 Link/Line. E1 is 2.048 Mbit/s (full duplex) which is split into 32 time slots, used countries other than Japan and USA. Other similar jargon are E1 Modem, PCM line ( used mainly by BSNL, India).<br />
14.  T1 : T1 link/Line. T1 1.544Mbits, normally has 24 time slots. used by USA and Japan.<br />
15. Call Flow : Flow chart of IVR Software, literally. Menus for IVR application, either speech driven or DTMF driven.<br />
16. UMS : Unified Messaging Service, an interesting IVR Application.<br />
17. CRM : Customer Resource Management, an integral part of call center, so it is related to IVRS. Most <strong>Call Center Software</strong> has IVRS and CRM as a part of it.<br />
18. DNI : Dialed Number Identification. Mainly used in Voice Portal and CRBT<br />
19. CRBT : Caller RingBack Tone, an revenue generating IVR Application with intelligent usage of SS7.<br />
20. ASR : Automatic Speech recognition, used in Voice Driven Menu in IVR Software.<br />
21. TTS : Text to Speech Converter. Used in IVRS to read out text in an IVR Software.<br />
22. CDR : Call Data Record. Important in <a href="http://www.ivrsworld.com">Voice Portal</a>.<br />
23. Engage Tone, Busy Tone, Disconnect Tone : Commonly heard while working on analog CTI boards with analog telephone lines.<br />
24. Nokia, Siemens, Ericson : Switch Vendors.<br />
25. MSP : Mobile Service Provider.<br />
26. VoiceXML : Latest tool for developing voice portal.</p>
<p>There might more jargon out there and I will keep updating them here. Readers are welcome to add few of them here. Thank you in advance.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ivrsworld.com/ivrs-tips/ivrs-jargons-and-glossary/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

