Hardware Quick Install Guides

• D/4PCI
• D/41JCT-LS
• D/120JCT-LS
• D/41ESC
• Proline/2V
• D/42-NE2
• D/82JCT-U
• D/240SC-T1
• D/300SC-E1
• D/240SC-2T1
• D/480SC-2T1
• D/300SC-2E1
• D/600SC-2E1
• D/240JCT-T1
• All Intel / Dialogic Quick Install Guides

Installation

• Installing Dialogic Boards v5.1.1 (WinNT / W2K / XP)
• Installing Dialogic Boards v5.1 (WinNT / W2K)
• Installing Dialogic Boards v5.01 (WinNT / W2K)
• Installing Dialogic Boards (Win95 / Win98)

Configuration

• Configuring your Dialogic Card with PBXpert
• Configuring your Dialogic Card to Detect Disconnect Tones
• Configuring Analog Dialogic Cards for Hold, Transfer, Conference, etc.

Links

Click here to see the GlobalCall E-1/T-1 Technology User's Guide

Click here for complete online documentation for Intel Dialogic cards and Driver information

Sample Programs

Click here for a complete list available sample programs provided by ExceleTel.

Here is a list of sample programs written specifically for Intel / Dialogic cards:

Technical Notes

Dial Tone Detection

When working with an Intel / Dialogic card The etLine.OnDialtone event will fire even when a dial tone isn't present. To test for a dial tone you have to set the property etLine.Call.PhoneNumber to a blank string then call etLine.Call.Dial. In the etLine.OnDialtone event handler routine you then set etLine.Call.PhoneNumber to "L" + the phone number (for example "L19192332232") then execute etLine.Call.Dial again. If the etLine.OnDisconnected event fires and the etLine.Call.DisconnectMode is set to LINEDISCONNECTMODE_NODIALTONE then you know that you do not have a dial tone. You can see all of this in the etDialogicDial sample program.

An easier way, depending on your application is to dial a call and detect the TeleTools OnSpecialInfo event and read the etLine.CallSpecialInfo property.  Dialogic will report no dialtone as LINESPECIALINFO_NOCIRCUIT.  Technically, this is not correct since the TAPI spec designed this to report a NO_CIRCUIT SIT tone which is received when you call a number and there is no circuit on that end.  If you need to know the difference between these events, you could use a timer, or check other call progress identifiers like "ringback" to see if it occurred before you got the message.

Early Connect

In some situations Dialogic cards may detect remote party connections incorrectly. Sometimes this can be overcome by increasing the Ring back Timeout. The default value is 700. Try increasing this by 100 or 200 until the problem goes away.

If increasing the value to more than 2000 does not solve the problem then set the number back to 700 and modify the Call Progress Analysis Flags.

The Call Progress Analysis Flags work in conjunction with PerfectCall. You will not want to enabled "Positive Answering Machine Detection" because even Dialogic says it doesn't work right. Your best bet would be to try using "DX_PVDENABLE(4).

For detailed information open the Dialogic Master.chm help file and search for "Perfect Call". You will need to look at checking the "DX_" options.

In some cases you may need to turn off Perfect Call.

The Ringback Timeout and Call Progress Analysis Flags can be found on the Call Parameters tab of the Configuration Service dialog box for the Dialogic Telephony Service Provider.

You will need to reboot for the changes to take effect.

DIGITAL BOARD USERS: Digital systems do not fire OnConnected in the same way as analog cards.  It is normal for the OnConnected event to fire as soon as the CO sets the A and B bits high. Instead of looking at
Connected states, look for Call Progress Analysis states.

D4 BOARD USERS: The D4 in some machines will simply not reliably detect voice to fire the OnConnected event.  In this case, you will have to use the D41 series.  

Important Property Settings

The following settings are the defaults. When working with Intel Dialogic cards do not change these values, Dialogic does not support them!:

•  etPlay.Device.Delay = 0 

•  etPlay.Device.Wait = False

•  etPlay.Device.Loop = False

Unformatting Phone Numbers

The Intel / Dialogic drivers do not understand how to dial phone numbers with formatting characters, you will receive a LINEERR_INVALADDRESS error (TAPI refers to a phone number or other identifier for a called party such as IP address as an "address").  For example:

1 (315) 635-3426
1.315.635.3426
555-1212

To avoid this problem set the etLine.Device.UnformatPhoneNumber property to True.  This will cause all formatting characters to be removed prior to dialing.

Another option is to use canonical formatted phone numbers and set the etLine.Device.TranslatePhoneNumber property to True.  When this property is set to True and the phone number is in canonical format then TeleTools will convert the value according to the Windows Dialing Properties.  For example:

Volume Settings

Dialogic does not have a configuration setting for the volume level. You need to set the etPlay.Volume properties. You can find information on this topic in the help file. Try the following values:

Borland C++ Builder

etPlay1->Volume->Enabled = True;   
etPlay1->Volume->Default = False; 
etPlay1->Volume->Reset = False; 
etPlay1->Volume->Position = 75;  

Borland Delphi

Visual Basic 5 & 6

Working with WAV Files

Click here for detailed information about playing and recording wave files.

Please note that Dialogic has several unresolved bugs for which there are workarounds.  As noted above, the "loop" capability is not properly implemented and can even lock the Dialogic TSP.  You must manually do this with etPlay.

Dialogic supports only the following wave formats natively:

• 11kHz, 8bit, Mono - main format and best quality

• 8kHz, 8bit, Mono - seems to be supported on newer cards 

 Unless you enable CODECS in etPlay and etRecord, you will receive an error trying to use another format

We have converted the wave files utilized by many of the TeleTools sample programs to a format that many Intel / Dialogic cards support natively, 11k8bitmono.zip.