Skip to main content

Editing the configuration file

The Phone Password Manager service uses one of two configuration files, named tpm.cfg or idtel.cfg to determine:

  • The names of script files that define call flow and logic

  • Supported languages

  • Enrollment types

  • Audio file types

  • The play back volume adjustment

  • Dialogic® voice board setup:

    • The number of lines supported on the boards

    • The type of boards

    • The number of boards installed

    • Whether or not the boards use SCBus routing

    • Any custom tones the boards support (if loop-current detection is not supported)

  • Dialogic® Host Media Processing Software setup:

    • Playback volume levels

    • The number of lines supported

    • Audio file type

    • Audio codec

When you install Phone Password Manager, the installer program automatically detects your IVR system configuration and creates this file in the \<instance>\service\ directory on the IVR server. The idtel.cfg file is only created when a Dialogic® Voice board, or Dialogic® PowerMedia Host Media Processing is detected. The idtel.cfg file is used in place of tpm.cfg to handle calls received from Dialogic® equipment.

You can modify idtel.cfg if your system configuration differs from what was auto-detected, or if you want to modify the default settings. The file includes instructions for modifying each setting in-line as comments.

There are settings within idtel.cfg that only apply to VoIP and softphone systems, which can be found under "VoIP Proxy Server Registration".

You must restart the Phone Password Manager service in order for your configuration changes to take effect.

If you are using a Dialogic® voice board and loop disconnect supervision is provided as a tone or cadence, you can configure Phone Password Manager to detect the condition of the calling party prematurely hanging up. This can be done either by defining the disconnect tone or cadence in idtel.cfg, or by creating a tsf file containing call progress tone information.

If loop disconnect supervision is provided with a loop current drop, it is not necessary to define this information, and the change in line status will be detected automatically if your voice board supports loop current supervision.

Editing the Asterisk® configuration file

Phone Password Manager uses the file asterisk.cfg to determine the following settings when interacting with an Asterisk® server:

  • The port used to listen for Asterisk® communication.

  • The IP range to listen for.

  • The number of channels upon which communication can be accepted.

  • The list of IP addresses with which communication is permitted.

  • The name of the Asterisk® server’s audio file directory

  • If Phone Password Manager should automatically upload files to the Asterisk® server.

  • Which folders to exclude if auto-uploading is enabled.

  • Whether or not to keep the temporary files created during auto-upload.

  • (Optional) Which call logic scripts to run when a call is received from an Asterisk® server.

Phone Password Manager automatically configures this file to the default settings when the Asterisk® module is installed, however you may use these options to restrict which communications your Phone Password Manager server accepts, for the sake of security.

Using 3CX PBX systems

Phone Password Manager is also capable of registering to a 3CX PBX system, in a manner similar to the Dialogic® configuration. To enable a 3CX configuration, alter the idtel.cfg file to include the following settings:

Registration "" = {
  Server = 10.0.1.1
  Realm  = "3CXPhoneSystem" // SIP only
  PhoneNumber = 333
  Password    = "333" // SIP only
}

Setting the Realm = "3CXPhoneSystem" value will enable Phone Password Manager to register a 3CX system when the next call is placed.

Defining disconnect tones in idtel.cfg

Disconnect tones can be explicitly defined within idtel.cfg. To do this:

  • Create a KVGroup in idtel.cfg with one of the following types, according to the example provided in idtel.cfg:

  • SingleTone

  • SingleCadenceTone

  • DualTone

  • DualCadenceTone

  1. Populate the KVGroup with the tones, timings, and tolerances provided by the local loop on disconnect. The name of the KVGroup can be arbitrary.

  2. Define the ToneType parameter and set it to the name of the KVGroup defining the tone or cadence.

  3. Restart all the Phone Password Manager services.

Note

This method, called Global Tone Detection , is unreliable on many Dialogic® cards. It is strongly recommended that a tsf file be specified if possible.

Defining disconnect tones with a TSF file

Dialogic® cards can be configured to use a tsf file to recognize call progress tones, including loop disconnect. The contents of this file must be defined according to the environment providing the call progress tones to the voice board. To implement this:

  1. Use the PBX Expert application provided as part of the Dialogic® drivers to discover the call progress tones. It is only necessary to discover the disconnect tones.

  2. Before saving the TSF file, mark the discovered tone set for consolidation, consolidate it, compile it, and enable it. Save it under the Dialogic® data directory.

  3. Use the Dialogic® Configuration Manager to enable tsf file support globally and set the TSF file name to the file you created.

  4. Restart the Dialogic® card.

  5. Restart all the Phone Password Manager services.

If this process was successful, when the Phone Password Manager service starts it will print an informational log message containing the text TSF has been loaded successfully . It will now treat the specified disconnect tones as a loop current off event.

In this section: