System information

-CallingCardAuthentication: (Will check the pincode in the database). On success go to next item, on fail play a prompt to try again
-Play File: Please enter the destination number
-Forward to phone number [dtmftrimmed] (call forwarding)
-Finish (release ivr)
If you want to bill the user for calling the ivr, then set the “ivrbilling” global config to “0”. Otherwise set to “1” and only the forwarded call will be billed.
If you need 2 leg billing, then set the “ivrbilling” value to 2. In this case 2 CDR records will be generated for the original caller.
PIN codec can be stored in the user table. Their type must be set to 0, isoperator to 6 and authentication based on username (5)
The authentication can be based on username, password or username+password or depending on the “callingcardauth” config option.
The following values are defined:
0=pin
1=callingcard username
2= callingcard password
3= callingcard username+password
4=any username
5=any password
6=any username+password
7=any username+password or username+pin
8=username for callingcard and username+password or username+pin for other users (default)
9=pin
10=password or pin
11=all combinations
12=calling card username or enduser username + password or enduser username + pin (default)
Calling cards can be generated in batch from the Tools menu.
When using the pin field based authentication, make sure that user has valid pin codes set in this field (when the users are automatically generated, the pin
is set to be username+password).
4.11.18. Phone to Phone (P2P) calls
You can implement this service on your website or in softphone.
The calls can be initiated with the following methods:
1. connect to the server console (a TCP connection) and issue the p2p call command. All communication can be encrypted and the clients are
authenticated properly.
2. Insert a new record to tb_conferences with type set to 3