IVR

From TBwiki
(Difference between revisions)
Jump to: navigation, search
(Added explanations for recording, and for legs joined to TDM call legs)
m (Needs revising edit)
 
(9 intermediate revisions by 5 users not shown)
Line 1: Line 1:
−
TelcoBridges products support for IVR, including digit/tone play/collection and voice playing/recording, across its entire product line.
+
TelcoBridges products support for IVR, including digit/tone play/collection and voice playing/recording, across its entire product line.  
  
−
== TelcoBridges and IVR capabilities ==
+
== TelcoBridges and IVR capabilities ==
−
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.
+
TelcoBridges products support IVR functionality via dedicated digital signal processor (DSP) chips, or via voice over IP (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.
+
  
−
== Hardware IVR capabilities on TMedia products ==
+
*With release 2.4 and older, DSPs are required for any IVR functionality.
−
* In the case of the Tmedia [[TMG3200]], Tdev [[TMP6400]], and Tmonitor [[TM1000]], DSP or VoIP chips can be included during the initial purchase or added subsequently via hardware upgrade.
+
*With release 2.5, DSPs are required only for playing/recording, as digit/tone collection and generation can be handled using VoIP chips.  
−
* 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.
+
*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.
  
−
== Calculating the number of IVR channels required ==
+
== Hardware IVR capabilities on TMedia products  ==
−
The number of IVR channels required in a system depends on the type of calls handled by the system, and the type of IVR operations performed. Below we explain how to calculate IVR resources requirements.
+
  
−
=== IVR Hardware density ===
+
*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.
−
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.
+
*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.
  
−
==== DSP chips ====
+
== Calculating the number of IVR channels required  ==
−
* 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)
+
−
* Tmedia [[TMG3200]] and Tdev [[TMP6400]] can have between 1 and 4 DSP chips.
+
−
* Tmedia [[TMG800]] and Tdev [[TMP800]] cannot have DSP chips.
+
  
−
==== VoIP chips ====
+
The number of IVR channels required in a system depends on the type of calls handled by the system, and the type of IVR operations performed. Below we explain how to calculate IVR resources requirements.  
−
* 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)
+
−
* Tmedia [[TMG3200]] and Tdev [[TMP6400]] can have between 1 and 16 VoIP chips.
+
−
* Tmedia [[TMG800]] and Tdev [[TMP800]] can have 1 or 2 VoIP chips.
+
  
 +
=== IVR Hardware density  ===
  
−
=== IVR resources usage ===
+
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.  
−
==== Non-joined call 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 ====
+
==== DSP chips  ====
−
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 ====
+
*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)  
−
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)
+
*Tmedia [[TMG3200]], Tmedia [[TMG7800|TMG7800]] and Tdev [[TMP6400]] can have between 1 and 4 DSP chips.
−
* Exception: If playing too, we get back to the non-joined case
+
*Tmedia [[TMG800]] and Tdev [[TMP800]] cannot have DSP chips.
  
−
==== Call legs joined to a VOIP call leg ====
+
==== VoIP chips  ====
−
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 ====
+
*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)  
−
When a call leg (A) (of type VoIP or TDM) is joined with another call leg (B) which is of type TDM:
+
*Tmedia [[TMG3200]], TMedia [[TMG7800|TMG7800]] and Tdev [[TMP6400]] can have between 1 and 16 VoIP chips.
−
* '''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)
+
*Tmedia [[TMG800]] and Tdev [[TMP800]] can have 1 or 2 VoIP chips.
  
−
[[category:Glossary]]
+
<br>
 +
 
 +
=== Number of IVR channels required  ===
 +
 
 +
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:
 +
 
 +
{| cellspacing="0" cellpadding="4" border="1" class="wikitable"
 +
|-
 +
! scope="col" |
 +
! bgcolor="#EEEEEE" scope="col" | Non joined call leg
 +
! bgcolor="#EEEEEE" scope="col" | Joined call leg, temporarily un-joined for playing to on of the two legs
 +
|-
 +
! bgcolor="#EEEEEE" scope="row" | None
 +
| 0
 +
| 0
 +
|-
 +
! bgcolor="#EEEEEE" scope="row" | Digit/tone collection/generation
 +
| 1
 +
| 1
 +
|-
 +
! bgcolor="#EEEEEE" scope="row" | Playing audio
 +
| 1
 +
| 1
 +
|-
 +
! bgcolor="#EEEEEE" scope="row" | Recording audio
 +
| 1
 +
| 1
 +
|-
 +
! bgcolor="#EEEEEE" scope="row" | Tone + playing + recording
 +
| 1
 +
| 1
 +
|}
 +
 
 +
<br> The following table represents the number of IVR channels required (''per call leg'') for IVR functions on joined call legs
 +
 
 +
{| cellspacing="0" cellpadding="4" border="1" class="wikitable"
 +
|-
 +
! scope="col" |
 +
! bgcolor="#EEEEEE" scope="col" | For a leg joined to a TDM leg
 +
! bgcolor="#EEEEEE" scope="col" | For a leg joined to a VoIP leg
 +
|-
 +
! bgcolor="#EEEEEE" scope="row" | None
 +
| 0
 +
| 0
 +
|-
 +
! bgcolor="#EEEEEE" scope="row" | Digit/tone collection/generation
 +
| 1
 +
| 0
 +
|-
 +
! bgcolor="#EEEEEE" scope="row" | Recording audio
 +
| 1
 +
| 1
 +
|-
 +
! bgcolor="#EEEEEE" scope="row" | Tone + recording
 +
| 2
 +
| 1
 +
|}
 +
 
 +
<br> The following table represents the number of IVR channels required (''per call leg'') for tone relay on joined calls.
 +
 
 +
{| cellspacing="0" cellpadding="4" border="1" class="wikitable"
 +
|-
 +
! scope="col" |
 +
! scope="col" |
 +
! bgcolor="#DDDDDD" colspan="4" scope="col" | Call leg B
 +
|-
 +
! scope="col" |
 +
! scope="col" |
 +
! bgcolor="#EEEEEE" scope="col" | TDM
 +
! bgcolor="#EEEEEE" scope="col" | VoIP (in-band relay)
 +
! bgcolor="#EEEEEE" scope="col" | VoIP (RFC2833 relay)
 +
! bgcolor="#EEEEEE" scope="col" | VoIP (SIP Info relay)
 +
|-
 +
! bgcolor="#DDDDDD" rowspan="4" scope="col" | Call leg A
 +
! bgcolor="#EEEEEE" scope="row" | TDM
 +
| 0
 +
| 0
 +
| 0
 +
| 0
 +
|-
 +
! bgcolor="#EEEEEE" scope="row" | VoIP (in-band relay)
 +
| 0
 +
| 0
 +
| 0
 +
| 0
 +
|-
 +
! bgcolor="#EEEEEE" scope="row" | VoIP (RFC2833 relay)
 +
| 0
 +
| 0
 +
| 0
 +
| 0
 +
|-
 +
! bgcolor="#EEEEEE" scope="row" | VoIP (SIP Info relay)
 +
| 0
 +
| 0
 +
| 0
 +
| 0
 +
|}
 +
 
 +
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 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)
 +
 
 +
[[Category:Glossary]]

Latest revision as of 13:54, 16 March 2018

TelcoBridges products support for IVR, including digit/tone play/collection and voice playing/recording, across its entire product line.

Contents

TelcoBridges and IVR capabilities

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.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.

Hardware IVR capabilities on TMedia products

  • In the case of the Tmedia TMG3200, Tmedia TMG7800 and Tdev TMP6400TM1000, 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

The number of IVR channels required in a system depends on the type of calls handled by the system, and the type of IVR operations performed. Below we explain how to calculate IVR resources requirements.

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.

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)
  • Tmedia TMG3200, Tmedia TMG7800 and Tdev TMP6400 can have between 1 and 4 DSP chips.
  • Tmedia TMG800 and Tdev TMP800 cannot have DSP chips.

VoIP chips

  • 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 and Tdev TMP6400 can have between 1 and 16 VoIP chips.
  • Tmedia TMG800 and Tdev TMP800 can have 1 or 2 VoIP chips.


Number of IVR channels required

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:

Non joined call leg Joined call leg, temporarily un-joined for playing to on of the two legs
None 0 0
Digit/tone collection/generation 1 1
Playing audio 1 1
Recording audio 1 1
Tone + playing + recording 1 1


The following table represents the number of IVR channels required (per call leg) for IVR functions on joined call legs

For a leg joined to a TDM leg For a leg joined to a VoIP leg
None 0 0
Digit/tone collection/generation 1 0
Recording audio 1 1
Tone + recording 2 1


The following table represents the number of IVR channels required (per call leg) for tone relay on joined calls.

Call leg B
TDM VoIP (in-band relay) VoIP (RFC2833 relay) VoIP (SIP Info relay)
Call leg A TDM 0 0 0 0
VoIP (in-band relay) 0 0 0 0
VoIP (RFC2833 relay) 0 0 0 0
VoIP (SIP Info relay) 0 0 0 0

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 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)
Retrieved from "https://docs.telcobridges.com/mediawiki/index.php?title=IVR&oldid=25243"
Personal tools