Writing an IVR - Revision history

Moritz Orbach: /* What handlers to install */ additional linking to message articles

2014-03-10T18:55:37Z

‎What handlers to install: additional linking to message articles

Moritz Orbach: grammar in headings

2014-03-10T18:51:45Z

grammar in headings

Moritz Orbach: section depth corrected: first heading is h2/==. "See also" as a section

2014-03-10T18:48:59Z

section depth corrected: first heading is h2/==. "See also" as a section

Moritz Orbach: order of explanations in intro, link to wp, acronym spelled out. One of the duplicated "just a channel"-explanations removed

2014-03-10T18:46:21Z

order of explanations in intro, link to wp, acronym spelled out. One of the duplicated "just a channel"-explanations removed

Monica at 11:52, 4 November 2013

2013-11-04T11:52:36Z

Dana: /* What handlers to install */

2012-12-11T11:33:55Z

‎What handlers to install

Dana at 09:50, 16 November 2012

2012-11-16T09:50:01Z

Dana at 09:39, 16 November 2012

2012-11-16T09:39:49Z

Dana at 14:39, 31 October 2012

2012-10-31T14:39:19Z

Dana at 14:39, 31 October 2012

2012-10-31T14:39:05Z

@@ Line 27: / Line 27: @@
 The application should install handlers for messages like "[[chan.dtmf]]" and "[[chan.notify]]" and act as a state machine, processing incoming events, changing the state and attaching voice sources and/or consumers via the "[[chan.attach]]" message.
-The caller can be transferred to another channel (which can be another IVR) by masquerading a "call.execute" message. As soon as the caller is connected to the transfer target channel the current application (the IVR) is automatically disconnected and terminated.
+The caller can be transferred to another channel (which can be another IVR) by masquerading a "[[call.execute]]" message. As soon as the caller is connected to the transfer target channel the current application (the IVR) is automatically disconnected and terminated.
 An application can also disconnect the caller by simply exiting.
@@ Line 35: / Line 35: @@
 As a local option an IVR can enable generating its own "[[chan.disconnected]]" message. While handling it an IVR can safely perform cleanup operations. However, once "[[chan.disconnected]]" is acknowledged the communication channel is closed and the script terminated after a very short delay.
-Nothing prevents an IVR from implementing other functionality. A route to a given called number can be obtained by emitting a "call.route" message and looking at the answer. An IVR can even act as a short lived routing module, for example to implement a meeting room.
+Nothing prevents an IVR from implementing other functionality. A route to a given called number can be obtained by emitting a "[[call.route]]" message and looking at the answer. An IVR can even act as a short lived routing module, for example to implement a meeting room.
 == See also ==

@@ Line 3: / Line 3: @@
 From Yate's point of view the IVR (the application behind it) is just a channel. It can be written in any programming language.
-== Start an IVR ==
+== Starting an IVR ==
 In Yate an IVR is an application started when an incoming call is routed to that application. This application gets the opportunity of inspecting events generated by the caller and giving commands to Yate - all these by handling or generating [[Messages]].
-== What should do an IVR ==
+== What an IVR should do ==
 An IVR application must at least:
@@ Line 23: / Line 23: @@
 Currently the options are PHP (via [[Lib Yate PHP|libyate.php]]) or Python (via libyate.py or [[YAYPM]]).
-== What handlers to install==
+== What handlers to install ==
 The application should install handlers for messages like "[[chan.dtmf]]" and "[[chan.notify]]" and act as a state machine, processing incoming events, changing the state and attaching voice sources and/or consumers via the "[[chan.attach]]" message.

@@ Line 3: / Line 3: @@
 From Yate's point of view the IVR (the application behind it) is just a channel. It can be written in any programming language.
-=== Start an IVR ===
+== Start an IVR ==
 In Yate an IVR is an application started when an incoming call is routed to that application. This application gets the opportunity of inspecting events generated by the caller and giving commands to Yate - all these by handling or generating [[Messages]].
-=== What should do an IVR ===
+== What should do an IVR ==
 An IVR application must at least:
@@ Line 18: / Line 18: @@
 Since all these are complex it is better to use libraries that can handle at least part of the job.
-=== How to implement an IVR ===
+== How to implement an IVR ==
 Usually an IVR is implemented using a script run under the control of the the external module and a library that converts incoming and outgoing messages in objects the programming language can handle.
 Currently the options are PHP (via [[Lib Yate PHP|libyate.php]]) or Python (via libyate.py or [[YAYPM]]).
-=== What handlers to install===
+== What handlers to install==
 The application should install handlers for messages like "[[chan.dtmf]]" and "[[chan.notify]]" and act as a state machine, processing incoming events, changing the state and attaching voice sources and/or consumers via the "[[chan.attach]]" message.
@@ Line 37: / Line 37: @@
 Nothing prevents an IVR from implementing other functionality. A route to a given called number can be obtained by emitting a "call.route" message and looking at the answer. An IVR can even act as a short lived routing module, for example to implement a meeting room.
+== See also ==
-'''See also'''
 * [[External Module]]

@@ Line 1: / Line 1: @@
-An IVR is a script written in a programming language that will be for Yate just a channel. An IVR can be used for playing prompts to users, register messages or configure other functionalities for the users.
+An [[wikipedia:IVR|IVR]] ('''I'''nteractive '''v'''oice '''r'''esponse) is an application that can be used for playing prompts to users, register messages or configure other functionalities for the users.
 === Start an IVR ===
-In Yate an IVR is an application started when an incoming call is routed to that application. This application gets the opportunity of inspecting events generated by the caller and giving commands to Yate - all these by handling or generating [[Messages]]. From Yate's point of view the IVR (the application behind it) is just a channel.
+In Yate an IVR is an application started when an incoming call is routed to that application. This application gets the opportunity of inspecting events generated by the caller and giving commands to Yate - all these by handling or generating [[Messages]].
 === What should do an IVR ===

← Older revision		Revision as of 11:52, 4 November 2013
Line 40:		Line 40:
	* [[External Module]]		* [[External Module]]
	* [[Lib Yate PHP\|Library PHP in Yate]]		* [[Lib Yate PHP\|Library PHP in Yate]]
		+
		+	[[Category:Extmodule]] [[Category:PHP]] [[Category:Programmers]] [[Category:Scripting]] [[Category:IVR]]

← Older revision		Revision as of 09:50, 16 November 2012
Line 34:		Line 34:

	Nothing prevents an IVR from implementing other functionality. A route to a given called number can be obtained by emitting a "call.route" message and looking at the answer. An IVR can even act as a short lived routing module, for example to implement a meeting room.		Nothing prevents an IVR from implementing other functionality. A route to a given called number can be obtained by emitting a "call.route" message and looking at the answer. An IVR can even act as a short lived routing module, for example to implement a meeting room.
		+
		+
		+	'''See also'''
		+
		+	* [[External Module]]
		+	* [[Lib Yate PHP\|Library PHP in Yate]]

← Older revision		Revision as of 14:39, 31 October 2012
Line 3:		Line 3:

	In Yate an IVR is an application started when an incoming call is routed to that application. This application gets the opportunity of inspecting events generated by the caller and giving commands to Yate - all these by handling or generating [[Messages]]. From Yate's point of view the IVR (the application behind it) is just a channel.		In Yate an IVR is an application started when an incoming call is routed to that application. This application gets the opportunity of inspecting events generated by the caller and giving commands to Yate - all these by handling or generating [[Messages]]. From Yate's point of view the IVR (the application behind it) is just a channel.
−

	=== What should do an IVR ===		=== What should do an IVR ===