IVR - Revision history

Allyntree: Needs revising edit

2018-03-16T18:54:23Z

Needs revising edit

Allyntree: /* IVR Hardware density */

2018-03-16T18:53:00Z

IVR Hardware density

Allyntree: /* TelcoBridges and IVR capabilities */

2018-03-16T18:51:36Z

TelcoBridges and IVR capabilities

Lucas Trottier: /* TelcoBridges and IVR capabilities */

2016-07-08T19:08:22Z

TelcoBridges and IVR capabilities

Cbilodeau: add needs revising category - need to define IVR

2013-02-11T16:56:47Z

add needs revising category - need to define IVR

Luc Morissette: Added TMG7800 in the list of available devices for DSP/VoIP and removed TM1000

2012-02-22T13:15:41Z

Added TMG7800 in the list of available devices for DSP/VoIP and removed TM1000

Show changes

Abrassard at 19:45, 6 January 2012

2012-01-06T19:45:02Z

Abrassard: Added table for Relay

2011-12-08T15:29:39Z

Added table for Relay

Abrassard: Added table for joined call legs. Removed section for textual explanations, the table is much more self-explanatory

2011-12-08T15:17:34Z

Added table for joined call legs. Removed section for textual explanations, the table is much more self-explanatory

Abrassard: Added summary table for non-joined call legs

2011-12-08T15:04:43Z

Added summary table for non-joined call legs

← Older revision		Revision as of 18:54, 16 March 2018
Line 140:		Line 140:

	[[Category:Glossary]]		[[Category:Glossary]]
−	~~[[category:Needs revising]]~~

@@ Line 20: / Line 20: @@
 === IVR Hardware density  ===
-DSP chips and VoIP chips can both provide IVR functionality. When both are present on the hardware, DSPs are used first (to let VoIP resources available for actual VoIP RTP stream), and fall-back to VoIP channels when no DSP resource are available.
+DSP chips and VoIP chips can both provide IVR functionality. When both are present on the hardware, DSPs are used first (to make VoIP resources available for actual VoIP RTP stream), and fall-back to VoIP channels when no DSP resource are available.
 ==== DSP chips  ====
@@ Line 30: / Line 30: @@
 ==== VoIP chips  ====
-*Each VoIP chip can provide 341 channels of IVR functionality (though some calls will require two VoIP channels, one for RTP stream, one for Play/Record stream)
+*Each VoIP chip can provide 341 channels of IVR functionality (although some calls will require two VoIP channels, one for RTP stream, one for Play/Record stream)
 *Tmedia [[TMG3200]], TMedia [[TMG7800|TMG7800]] and Tdev [[TMP6400]] can have between 1 and 16 VoIP chips.
 *Tmedia [[TMG800]] and Tdev [[TMP800]] can have 1 or 2 VoIP chips.
 <br>
 === Number of IVR channels required  ===

@@ Line 5: / Line 5: @@
 TelcoBridges products support IVR functionality via dedicated digital signal processor (DSP) chips, or via voice over IP (VoIP) chips.
-*For release 2.4 and older, DSPs are required for any IVR functionality.
+*With release 2.4 and older, DSPs are required for any IVR functionality.
 *With release 2.5, DSPs are required only for playing/recording, as digit/tone collection and generation can be handled using VoIP chips.
 *With release 2.8.111 and above, there is also a possibility to use VoIP chips for playing/recording with special licensing. Please contact TelcoBridges support team to learn more about that feature.

@@ Line 7: / Line 7: @@
 *For release 2.4 and older, DSPs are required for any IVR functionality.
 *With release 2.5, DSPs are required only for playing/recording, as digit/tone collection and generation can be handled using VoIP chips.
-*With release 2.6 and above, there is also a possibility to use VoIP chips for playing/recording with specific network conditions. Please contact TelcoBridges support team to learn more about that feature.
+*With release 2.8.111 and above, there is also a possibility to use VoIP chips for playing/recording with special licensing. Please contact TelcoBridges support team to learn more about that feature.
 == Hardware IVR capabilities on TMedia products  ==

← Older revision		Revision as of 16:56, 11 February 2013
Line 140:		Line 140:

	[[Category:Glossary]]		[[Category:Glossary]]
		+	[[category:Needs revising]]

@@ Line 6: / Line 6: @@
 * For release 2.4 and older, DSPs are required for any IVR functionality.
 * With release 2.5, DSPs are required only for playing/recording, as digit/tone collection and generation can be handled using VoIP chips.
-* With release 2.6 and above, IVR functionality can be entirely handled by VoIP chips.
+* With release 2.6 and above, there is also a possibility to use VoIP chips for playing/recording with specific network conditions. Please contact TelcoBridges support team to learn more about that feature.
 == Hardware IVR capabilities on TMedia products ==

@@ Line 35: / Line 35: @@
 |-
 ! scope="col" |
-! scope="col" | Non joined call leg
+! scope="col" bgcolor="#EEEEEE" | Non joined call leg
-! scope="col" | Joined call leg, temporarily un-joined for playing to on of the two legs
+! scope="col" bgcolor="#EEEEEE" | Joined call leg, temporarily un-joined for playing to on of the two legs
 |-
-! scope="row" | None
+! scope="row" bgcolor="#EEEEEE" | None
 | 0 || 0
 |-
-! scope="row" | Digit/tone collection/generation
+! scope="row" bgcolor="#EEEEEE" | Digit/tone collection/generation
 | 1 || 1
 |-
-! scope="row" | Playing audio
+! scope="row" bgcolor="#EEEEEE" | Playing audio
 | 1 || 1
 |-
-! scope="row" | Recording audio
+! scope="row" bgcolor="#EEEEEE" | Recording audio
 | 1 || 1
 |-
-! scope="row" | Tone + playing + recording
+! scope="row" bgcolor="#EEEEEE" | Tone + playing + recording
 | 1 || 1
 |}
@@ Line 59: / Line 59: @@
 |-
 ! scope="col" |
-! scope="col" | For a leg joined to a TDM leg
+! scope="col" bgcolor="#EEEEEE" | For a leg joined to a TDM leg
-! scope="col" | For a leg joined to a VoIP leg
+! scope="col" bgcolor="#EEEEEE" | For a leg joined to a VoIP leg
 |-
-! scope="row" | None
+! scope="row" bgcolor="#EEEEEE" | None
 | 0 || 0
 |-
-! scope="row" | Digit/tone collection/generation
+! scope="row" bgcolor="#EEEEEE" | Digit/tone collection/generation
 | 1 || 0
 |-
-! scope="row" | Recording audio
+! scope="row" bgcolor="#EEEEEE" | Recording audio
 | 1 || 1
 |-
-! scope="row" | Tone + recording
+! scope="row" bgcolor="#EEEEEE" | Tone + recording
 | 2 || 1
 |}

@@ Line 29: / Line 29: @@
-=== IVR resources usage explained ===
+=== Number of IVR channels required ===
-==== Non-joined call legs ====
+The following table represents the number of IVR resources required for non-joined call legs, or for joined call legs that are temporarily un-joined due to playing to one of the two joined legs:
-For non-joined call legs, IVR resources are required for:
-* Digit/tone collection or generation
-* Playing or recording files. Note: IVR resource remains allocated for 1 second after playing file finished, in case application needs to play another file.
-'''=> One IVR channel is required''' to perform IVR on non-joined call legs.
-−
-==== Playing files to joined call legs ====
-When playing files, joined call legs are temporarily un-joined for the duration of the play. The behavior is thus the same as for non-joined call legs (see above)
-−
-==== Recording joined call legs ====
-Recording on joined call legs always requires one extra IVR channel (in addition to IVR resource that may be required for digit/tone collection or generation)
-* Exception: If playing too, we get back to the non-joined case
-−
-==== Call legs joined to a VOIP call leg ====
-When a call leg (A) (of type VoIP or TDM) is joined with another call leg (B) which is of type VoIP, the VoIP resource of the other all leg (B) can be used to perform digit/tone collection or generation for call leg (A). Thus:
-* '''No IVR channel is required''' to perform digit/tone collection or generation on legs joined with a VoIP call leg (it uses VoIP channel of the joined call leg)
-−
-==== Call legs joined to a TDM call leg ====
-When a call leg (A) (of type VoIP or TDM) is joined with another call leg (B) which is of type TDM:
-* '''One IVR channel is required''' to perform digit/tone collection or generation on legs joined with a TDM call leg. This resource is of type "flowthrough", introducing a 40ms delay in the audio path (in order to perform complete tone suppression)
-−
-−
-−
-=== IVR resources usage summary table ===
-Following table represents the number of IVR resources required for non-joined call legs, or for joined call legs that are temporarily un-joined due to playing to one of the two joined legs:
 {| class="wikitable" border="1" cellpadding="4" cellspacing="0"
@@ Line 77: / Line 53: @@
 | 1 || 1
 |}
 [[category:Glossary]]