Overview
This application differs from the Calling Card application in that that it doesn't use TTS at all. The Tiny Calling Card Application requires the calling card account to have CLI mapping so it can check the account and immediately prompt for the destination. The application plays the dial tone to the user as the destination prompt. It doesn't offer to redial last destination either but immediately hangs up after the call regardless either it was successful or unsuccessful.
Call routing setup
- Add vendor connection. Set the Asterisk's host/port in the Destination field of Vendor Connection (ex: 192.168.0.100:5062).
- Set the CLD Translation Rule for the connection to the value s/.*/cctiny/.
- Add route to this connection and specify the Tiny Calling Card Extension number.
Configuration options
WARNING! Both Section and Option values MUST be lowercase in the database. They are mixed case here for readability only.
| Section | Option | Meaning | Default |
| CallingCard | MinCallDuration | Minimum allowed call duration. If calculated maximum duration of the call to the requested destination is less than this value then the user will hear the prompt "You have insufficient funds to make this call" | 10 seconds |
| CallingCard | MaxCallDuration | Maximum call duration | 3600 seconds |
| CallingCard | OutgoingSIPHost | SIP proxy host:port to send the outgoing calls to (this option can also be set from the command line) | 127.0.0.1:5060 |
| CallingCard | KeepCLI | CLI from the initial call leg will be used to call destination if this option set to true. The calling card username will be used as CLI otherwise. | False |
Database usage
The calling_card_cli_map table is used to store CLI-to-CallingCard mappings. These mappings are used to automatically select the calling card account based on the CLI of the user.