IVR - Revision history

Luc Morissette: Updated TMG800 information for IVR DSP devices

2022-01-13T20:49:44Z

Updated TMG800 information for IVR DSP devices

← Older revision		Revision as of 16:49, 13 January 2022
Line 5:		Line 5:
	TelcoBridges products support IVR functionality via dedicated digital signal processor (DSP) chips, or via voice over IP (VoIP) chips.		TelcoBridges products support IVR functionality via dedicated digital signal processor (DSP) chips, or via voice over IP (VoIP) chips.

	*With release 2.4 and older, DSPs are required for any IVR functionality.		*With release 2.4 and older, IVR 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.5, IVR 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.		*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 ==		== Hardware IVR capabilities on TMedia products ==

	*In the case of the Tmedia [[TMG3200]], Tmedia [[TMG7800\|TMG7800]] and Tdev [[TMP6400]][[TM1000\|TM1000]], DSP or ~~VoIP chips can be included during the initial purchase or added subsequently via hardware upgrade.~~		*In the case of the Tmedia [[TMG800]] , Tmedia [[TMG3200]], Tmedia [[TMG7800\|TMG7800]] and Tdev [[TMP6400]][[TM1000\|TM1000]], IVR DSP or VoIP chips can be included during the initial purchase or added subsequently via hardware upgrade.
	*In the case of the Tmedia [[TMG800]] and Tdev [[TMP800]], DSP chips are unavailable. VoIP chips can be included during the initial purchase or added subsequently via hardware upgrade.

	== Calculating the number of IVR channels required ==		== Calculating the number of IVR channels required ==
Line 20:		Line 19:
	=== IVR Hardware density ===		=== 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 make VoIP resources available for actual VoIP RTP stream), and fall-back to VoIP channels when no DSP ~~resource~~ are available.		IVR DSP chips and VoIP chips can both provide IVR functionality. When both are present on the hardware, IVR DSPs are used first (to make VoIP resources available for actual VoIP RTP stream), and fall-back to VoIP channels when no IVR DSP resources are available.

	==== DSP chips ====		==== IVR DSP chips ====

	*Each DSP chip can provide 512 channels of IVR functionality (except when Play and Record are both used at the same time, where density is 300 channels per chip)		*Each IVR DSP chip can provide 512 channels of IVR functionality (except when Play and Record are both used at the same time, where density is 300 channels per chip)
	*Tmedia [[TMG3200]], Tmedia [[TMG7800\|TMG7800]] and Tdev [[TMP6400]] can have between 1 and 4 DSP chips.		*Tmedia [[TMG3200]], Tmedia [[TMG7800\|TMG7800]] and Tdev [[TMP6400]] can have between 1 and 4 DSP chips.
	*Tmedia [[TMG800]] and Tdev [[TMP800]] ~~cannot~~ have DSP ~~chips~~.		*Tmedia [[TMG800]] and Tdev [[TMP800]] can have 1 DSP chip.

	==== VoIP chips ====		==== VoIP chips ====
Line 135:		Line 134:
	Notes:		Notes:

	*The tables above count only the IVR resources. To that number, one VoIP resource must be added if the call leg is of type VoIP.		*The tables above count only the IVR DSP resources. To that number, one VoIP resource must be added if the call leg is of type VoIP.
	*The weight of a VoIP resource may vary according to the codec used (between 58 and 341 channels per VoIP chip, depending on the codec)		*The weight of a VoIP resource may vary according to the codec used (between 58 and 341 channels per VoIP chip, depending on the codec)
	*The weight of a VoIP resource used for IVR is the same no matter if tone/play/record or all of them is used (341 channels per VoIP chip)		*The weight of a VoIP resource used for IVR is the same no matter if tone/play/record or all of them is used (341 channels per VoIP chip)

	[[Category:Glossary]]		[[Category:Glossary]]

Allyntree: Needs revising edit

2018-03-16T18:54:23Z

Needs revising edit

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

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

Allyntree: /* IVR Hardware density */

2018-03-16T18:53:00Z

IVR Hardware density

← Older revision		Revision as of 14:53, 16 March 2018
Line 20:		Line 20:
	=== IVR Hardware density ===		=== 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 ====		==== DSP chips ====
Line 30:		Line 30:
	==== VoIP chips ====		==== 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 [[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.		*Tmedia [[TMG800]] and Tdev [[TMP800]] can have 1 or 2 VoIP chips.

	<br>		<br>

	=== Number of IVR channels required ===		=== Number of IVR channels required ===

Allyntree: /* TelcoBridges and IVR capabilities */

2018-03-16T18:51:36Z

TelcoBridges and IVR capabilities

← Older revision		Revision as of 14:51, 16 March 2018
Line 5:		Line 5:
	TelcoBridges products support IVR functionality via dedicated digital signal processor (DSP) chips, or via voice over IP (VoIP) chips.		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.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.		*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.

Lucas Trottier: /* TelcoBridges and IVR capabilities */

2016-07-08T19:08:22Z

TelcoBridges and IVR capabilities

← Older revision		Revision as of 15:08, 8 July 2016
Line 7:		Line 7:
	*For release 2.4 and older, DSPs are required for any IVR functionality.		*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.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 ==		== Hardware IVR capabilities on TMedia products ==

Cbilodeau: add needs revising category - need to define IVR

2013-02-11T16:56:47Z

add needs revising category - need to define IVR

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

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

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

← Older revision		Revision as of 15:45, 6 January 2012
Line 6:		Line 6:
	* For release 2.4 and older, DSPs are required for any IVR functionality.		* 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.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 ==		== Hardware IVR capabilities on TMedia products ==

Abrassard: Added table for Relay

2011-12-08T15:29:39Z

Added table for Relay

← Older revision		Revision as of 11:29, 8 December 2011
Line 35:		Line 35:
	\|-		\|-
	! scope="col" \|		! 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		\| 0 \|\| 0
	\|-		\|-
	! scope="row" \| Digit/tone collection/generation		! scope="row" bgcolor="#EEEEEE" \| Digit/tone collection/generation
	\| 1 \|\| 1		\| 1 \|\| 1
	\|-		\|-
	! scope="row" \| Playing audio		! scope="row" bgcolor="#EEEEEE" \| Playing audio
	\| 1 \|\| 1		\| 1 \|\| 1
	\|-		\|-
	! scope="row" \| Recording audio		! scope="row" bgcolor="#EEEEEE" \| Recording audio
	\| 1 \|\| 1		\| 1 \|\| 1
	\|-		\|-
	! scope="row" \| Tone + playing + recording		! scope="row" bgcolor="#EEEEEE" \| Tone + playing + recording
	\| 1 \|\| 1		\| 1 \|\| 1
	\|}		\|}
Line 59:		Line 59:
	\|-		\|-
	! scope="col" \|		! 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		\| 0 \|\| 0
	\|-		\|-
	! scope="row" \| Digit/tone collection/generation		! scope="row" bgcolor="#EEEEEE" \| Digit/tone collection/generation
	\| 1 \|\| 0		\| 1 \|\| 0
	\|-		\|-
	! scope="row" \| Recording audio		! scope="row" bgcolor="#EEEEEE" \| Recording audio
	\| 1 \|\| 1		\| 1 \|\| 1
	\|-		\|-
	! scope="row" \| Tone + recording		! scope="row" bgcolor="#EEEEEE" \| Tone + recording
	\| 2 \|\| 1		\| 2 \|\| 1
			\|}


			The following table represents the number of IVR channels required (''per call leg'') for tone relay on joined calls.
			{\| class="wikitable" border="1" cellpadding="4" cellspacing="0"

			\|-
			! scope="col" \|
			! scope="col" \|
			! scope="col" colspan="4" bgcolor="#DDDDDD" \| Call leg B
			\|-
			! scope="col" \|
			! scope="col" \|
			! scope="col" bgcolor="#EEEEEE" \| TDM
			! scope="col" bgcolor="#EEEEEE" \| VoIP (in-band relay)
			! scope="col" bgcolor="#EEEEEE" \| VoIP (RFC2833 relay)
			! scope="col" bgcolor="#EEEEEE" \| VoIP (SIP Info relay)
			\|-
			! scope="col" rowspan="4" bgcolor="#DDDDDD" \| Call leg A
			! scope="row" bgcolor="#EEEEEE" \| TDM
			\| 0 \|\| 0 \|\| 0 \|\| 0
			\|-
			! scope="row" bgcolor="#EEEEEE" \| VoIP (in-band relay)
			\| 0 \|\| 0 \|\| 0 \|\| 0
			\|-
			! scope="row" bgcolor="#EEEEEE" \| VoIP (RFC2833 relay)
			\| 0 \|\| 0 \|\| 0 \|\| 0
			\|-
			! scope="row" bgcolor="#EEEEEE" \| VoIP (SIP Info relay)
			\| 0 \|\| 0 \|\| 0 \|\| 0
	\|}		\|}

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

@@ 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:
 {| class="wikitable" border="1" cellpadding="4" cellspacing="0"
@@ Line 77: / Line 53: @@
 | 1 || 1
 |}
 [[category:Glossary]]

← Older revision		Revision as of 11:29, 8 December 2011
Line 35:		Line 35:
	\|-		\|-
	! scope="col" \|		! 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		\| 0 \|\| 0
	\|-		\|-
	! scope="row" \| Digit/tone collection/generation		! scope="row" bgcolor="#EEEEEE" \| Digit/tone collection/generation
	\| 1 \|\| 1		\| 1 \|\| 1
	\|-		\|-
	! scope="row" \| Playing audio		! scope="row" bgcolor="#EEEEEE" \| Playing audio
	\| 1 \|\| 1		\| 1 \|\| 1
	\|-		\|-
	! scope="row" \| Recording audio		! scope="row" bgcolor="#EEEEEE" \| Recording audio
	\| 1 \|\| 1		\| 1 \|\| 1
	\|-		\|-
	! scope="row" \| Tone + playing + recording		! scope="row" bgcolor="#EEEEEE" \| Tone + playing + recording
	\| 1 \|\| 1		\| 1 \|\| 1
	\|}		\|}
Line 59:		Line 59:
	\|-		\|-
	! scope="col" \|		! 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		\| 0 \|\| 0
	\|-		\|-
	! scope="row" \| Digit/tone collection/generation		! scope="row" bgcolor="#EEEEEE" \| Digit/tone collection/generation
	\| 1 \|\| 0		\| 1 \|\| 0
	\|-		\|-
	! scope="row" \| Recording audio		! scope="row" bgcolor="#EEEEEE" \| Recording audio
	\| 1 \|\| 1		\| 1 \|\| 1
	\|-		\|-
	! scope="row" \| Tone + recording		! scope="row" bgcolor="#EEEEEE" \| Tone + recording
	\| 2 \|\| 1		\| 2 \|\| 1
			\|}


			The following table represents the number of IVR channels required (''per call leg'') for tone relay on joined calls.
			{\| class="wikitable" border="1" cellpadding="4" cellspacing="0"

			\|-
			! scope="col" \|
			! scope="col" \|
			! scope="col" colspan="4" bgcolor="#DDDDDD" \| Call leg B
			\|-
			! scope="col" \|
			! scope="col" \|
			! scope="col" bgcolor="#EEEEEE" \| TDM
			! scope="col" bgcolor="#EEEEEE" \| VoIP (in-band relay)
			! scope="col" bgcolor="#EEEEEE" \| VoIP (RFC2833 relay)
			! scope="col" bgcolor="#EEEEEE" \| VoIP (SIP Info relay)
			\|-
			! scope="col" rowspan="4" bgcolor="#DDDDDD" \| Call leg A
			! scope="row" bgcolor="#EEEEEE" \| TDM
			\| 0 \|\| 0 \|\| 0 \|\| 0
			\|-
			! scope="row" bgcolor="#EEEEEE" \| VoIP (in-band relay)
			\| 0 \|\| 0 \|\| 0 \|\| 0
			\|-
			! scope="row" bgcolor="#EEEEEE" \| VoIP (RFC2833 relay)
			\| 0 \|\| 0 \|\| 0 \|\| 0
			\|-
			! scope="row" bgcolor="#EEEEEE" \| VoIP (SIP Info relay)
			\| 0 \|\| 0 \|\| 0 \|\| 0
	\|}		\|}