Description: Used to have the Tenor provide a secondary prompt for calls that come in to the PSTN trunk group. This includes providing a simple second dial tone or a series of Interactive Voice Response (IVR) prompts for Pre-paid or Post-paid accounts.
Cmd Type: command.
Prompt Level: config pstntg 1# and config pbxtg 1#
Syntax: ivrtype {0 | 1 | 2 | 3 | 4 | 5 | 6 | 9}
Arguments:
0 Feature Disabled
1 Provides 2nd Dial Tone
2 Pre-paid Calling Card
3 Post-paid Calling Account - Type 0
4 ANI Authorization - Type 1
5 ANI Authorization - Type 2
6 Post-paid Calling Account - Type 1
7 Not used yet
8 Not used yet
9 ANI Authorization - Type 3 (added during s/w release P4-2-15)
Default: 0 - Disabled
Availability: For software release 4 or greater (P4-1-9): On all Digital & Analog Tenors, regardless of choice of Signaling. In the past, there were some limitations on this.
Guidelines: Typically, you would have the Trunk Group's passthru set to "no" for IVR applications.
If you set this option to 1 (2nd Dial Tone), the Tenor will authenticate PIN entries against the value set in the pincode field. A RADIUS Server is not required for this ivrtype, the Tenor provides the Authentication & Authorization in this case.
If you set this option to 2 (Pre-paid Calling Card), you will have the option to set the card length (ivrcardlength), and to choose the Language for the IVR Prompts played on this TG (ivrlanguage).
If you set this option to 3 or 6 (Post-paid Calling Card Types 0 & 1), you will have the option to set the account length and the PIN length (ivraccountlength & ivrpinlength), and to choose the Language for the IVR Prompts played on this TG (ivrlanguage). o The difference between Type 0 and Type 1is that Type 0 (ivrtype = 3) sends the Account Number and PIN in 2 separate fields to the RADIUS server and Type 1 (IVRType = 6) is interoperable with RADIUS Servers which accept those 2 pieces of information together in one field.
If you set this option to 4, 5 or 9 (ANI Authorization Types 1, 2 or 3), the Tenor will transmit the ANI of the Calling Party to the RADIUS Server for "automatic" authorization to place calls.
The difference between Type 1 and Type 2 is that in ANI Type 1 (ivrtype = 4), when a match is not found on the RADIUS Server for an ANI, the call is disconnected. In other words, the ANI must be known by the RADIUS Server to place a call. In ANI Type 2 (ivrtype = 5), if the ANI does not match, the caller may manually enter in the Account Number, so that calls can be made, no matter what location the caller is calling from. For ANI Type 3 (ivrtype = 9) incoming calls over PRI, the ANI is passed to the RADIUS Server for Authentication and Authorization, and when successful, the call is connected automatically to a destination based on the DNIS, but determined by the RADIUS Server. If the setup message does not include both the ANI & the Called Number, the call will be rejected.
Examples:
config pstntg 1# ivrtype 2
Sets the ivrtype to Prepaid Calling Card.
Related Cmds: pincode, ivraccessnumber, ivranswerdelay, ivraccountlength, ivrpinlength, ivrcardlength, ivrlanguage, ivrlangtype, multisession, retrycounter
Note
See the RADIUS/IVR Chapter of Section IX (9) for an "IVR Quick-Start Guide" or the RADIUS Developer's Guide (downloadable from the Customer Service section of www.quintum.com) for many more details regarding these processes.