System information
iscallback
1=act based on anumberhandling (default - connect to the ivr if not authenticated as enduser, otherwise callback immediately)
2=connect to the ivr if not authenticated as enduser, otherwise callback immediately
3=connect to the ivr if authenticated as enduser, otherwise callback immediately
4=drop the call if not authenticated as enduser, otherwise callback immediately
5=drop the call if authenticated as enduser, otherwise callback immediately
6= callback immediately always
7=always ivr
other=ivr id to use (otherwise will check the "ivrid" field)
Example 1: if you want to call only authenticated users (no expense for failed authentication on callback):
ivrauthentication: 1
iscallback: 1
Example 2: if you have a free to call number or you can afford the callback payment to unauthenticated users then you can use the following settings:
ivrauthentication: 1
iscallback: 8
Example 3: no free callback and no trust in A number authentication
ivrauthentication: 3
iscallback: 2
*Note: if you would like to allow calls to IVR or to callback numbers from not authenticated parties, then set the “freeivraccess” and “freeaccessuserid” configuration options accordingly.
Technical details
1. call initated from console, db check or iscallback user
2. mainlogic process asyncCallback and initiate call
3. client endpoint changed to server ep on connect
4. ivr starts requiring pin if needed and the target number
5. ivr callforward with 2 leg billing
4.11.17. Calling Card services
For a calling card service you must setup an IVR (and a campaign) that will handle the authentication and forward the call to the requested destination.
To create an access number, add a “enduser” and set the ivrid to the campaign id you wish to use.
You can also allow authentication based on A number by setting “anumberlookup” for the traffic sender.
Example IVR:
-Play File: Welcome to xxx. Please enter your PIN number
-Wait for dtmf (acquire PIN digits)










