IVR
From TBwiki
(Difference between revisions)
(Added summary table for non-joined call legs) |
(Added table for joined call legs. Removed section for textual explanations, the table is much more self-explanatory) |
||
| Line 29: | Line 29: | ||
| − | === IVR | + | === 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: | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
{| class="wikitable" border="1" cellpadding="4" cellspacing="0" | {| class="wikitable" border="1" cellpadding="4" cellspacing="0" | ||
| Line 77: | Line 53: | ||
| 1 || 1 | | 1 || 1 | ||
|} | |} | ||
| + | |||
| + | |||
| + | The following table represents the number of IVR channels required (''per call leg'') for IVR functions on joined call legs | ||
| + | {| class="wikitable" border="1" cellpadding="4" cellspacing="0" | ||
| + | |- | ||
| + | ! scope="col" | | ||
| + | ! scope="col" | For a leg joined to a TDM leg | ||
| + | ! scope="col" | For a leg joined to a VoIP leg | ||
| + | |- | ||
| + | ! scope="row" | None | ||
| + | | 0 || 0 | ||
| + | |- | ||
| + | ! scope="row" | Digit/tone collection/generation | ||
| + | | 1 || 0 | ||
| + | |- | ||
| + | ! scope="row" | Recording audio | ||
| + | | 1 || 1 | ||
| + | |- | ||
| + | ! scope="row" | Tone + recording | ||
| + | | 2 || 1 | ||
| + | |} | ||
| + | |||
| + | 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]] | [[category:Glossary]] | ||
Revision as of 10:17, 8 December 2011
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.
- 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.
Hardware IVR capabilities on TMedia products
- 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.
- 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 let 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 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 (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.
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 |
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)
