System information

 fromport
 rtprecport
 callertype
 callstate
 cc_clientid
 cc_ccid
Technical description:
On routing if calleduser.ivrid > 0 than set ep ivr_id and calltype to eIvr
No other ep will be created
ivr_id is the campaignid
On invite (after routed) if calltype = eIvr () call IvrAction(actIvrStart);
IvrAction(EIvrActionType actiontype)
1. the actiontype will tell what was happened: actDefault, actIvrStart, actReady, actUserInput, actTimeout, actFail
2. load the scripts if already not loaded
3. Check next action todo (jumpto). Especially check for dtmf input action
a. if actiontype == actUserInput than check if input finished (eof or maxlen)
b. if play finished and need to repeat, than play again
c. othervise set jumpto
4. JumpTo next action if needed (check enterconditions)
5. Do the next action (datainputtype, if any)
Play file, execute sql, forward, etc
4.11.15. Callback number
Used for handling incoming calls by callcenter operators.
See the “callback“ global config option.
4.11.16. Callback services
Callback services can be implemented by entering the number to call on the website or by CID or ANI callback.
To define access numbers set tb_user.iscallback to the required ivr (campaignid) and tb_user.anumberlookup to 1.
The calls will be authenticated based on “ivrauthentication” global config value and/or “iscallback” user field. When using only A number authentication
be aware of frauding possibilities.
Callback will be initiated from “callbackcallernumber” A number or from the user who received the call if “callbackcallernumber” is not specified.
The callback will automatically start the IVR specified in the “iscallback” field or in “ivrid” field of the access number.
Ivrauthentication is deprecated. Use the anumberhandling global configuration: 0=disabled,1=only add, 2 = only accept, 3=add and accept (default)