IVR
(Added explanation for non-joined call legs, and call legs joined to VoIP call legs) |
(Added explanations for recording, and for legs joined to TDM call legs) |
||
| Line 36: | Line 36: | ||
'''=> One IVR channel is required''' to perform IVR on non-joined call legs. | '''=> One IVR channel is required''' to perform IVR on non-joined call legs. | ||
| − | ==== | + | ==== Playing files to joined call legs ==== |
| − | When | + | 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) | ||
[[category:Glossary]] | [[category:Glossary]] | ||
Revision as of 09:44, 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.
IVR resources usage
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
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)
