- Home
- Services & Support
- Downloads
- Helpweb
- Dialogic API information
- Find a Dialogic API
- DM3 & JCT Media Boards
- Host Media Processing (HMP)
- Global Call API
- Brooktrout Fax
- IP Media Server
- CSP / MSP / IMG
- DMG-series Media Gateways
- Signaling products
- Global Call API
- Multimedia Platform for ATCA
- Diva Media Boards
- Diva SDK
- Diva Client
- Eiconcards (X.25)
- Other products
- Online Training
- Manuals
- Contact
Dialogic Support Helpweb
Dialogic® Diva® SDK
Using the Component API with Delphi 7
Firstly, make sure that the Diva Component API is registered in your Delphi development system. See "DivaRegisterComponent.bat" (in the SDK \basic\bin directory) for the command that does this.
1. Go to Project/Import Library in the Delphi IDE
2. Click "Add" and locate the DivaSDK.DLL (usually in \Windows\System32).
3. Make sure the box "Generate Component Wrapper" is ticked", and click Install
The type library "Diva SDK 1.0 Type Library (Version 1.0)" is now available for programs to use.
On the component toolbar (on the "ActiveX" tab) you will find four new icons that represent the four types of object exported by the Diva Server Component API: DivaSystem; DivaDevice; DivaCall; DivaInstance. You can select these objects and place them on the design form in the normal way. Secondly, the component wrapper "DIVASDKLib_TLB.pas" is generated and placed in "\Program Files\Borland\Delphi7\Imports". This should be included (on the "uses" clause of a program) to give access to all the methods and properties of the Diva SDK objects.
For example, to use the TDivaCall object, the object that represents a single telephony call:
1. Select the TDivaCall object on the toolbar and drop one on the form. You should now find that the TForm1 code has a reference included to an object, usually "DivaCall1" of type "TDivaCall".
2. Selecting this object on the form will allow you to set the relationship between events (received by DivaCall1) and which functions they activate. For example, DivaCall1 has events like "OnConnected", "OnDisconnected", "OnToneReceived". Clicking on the event field causes Delphi to automatically generate a skeleton of the procedure needed to handle the event. You can then fill in the rest of the code manually.
Notes:
1. The Diva Server SDK objects DivaSystem, DivaDevice, DivaCall, DivaInstance are imported by Delphi as TDivaSystem, TDivaDevice, TDivaCall, TDivaInstance, fitting in with normal Borland naming conventions.
2. Some of the methods are renamed relative to the Dialogic® Diva documentation PDF. This is because Delphi renames procedure when it gets a name collision. For example the "Connect" and "Disconnect" events are known as "Connect1" and "Disconnect1" in Delphi code.
If in doubt, you can always check the DIVASDKLib_TLB.pas file, which has the formal definition of all the symbols and methods.
3. When you select an object, the 'properties' list (in the Object Inspector) does not list all of the properties of the TDivaCall object. All the properties exist, though, it is only necessary to look them up in the Dialogic® Diva PDF file and write the code into your procedures.
1. Go to Project/Import Library in the Delphi IDE
2. Click "Add" and locate the DivaSDK.DLL (usually in \Windows\System32).
3. Make sure the box "Generate Component Wrapper" is ticked", and click Install
The type library "Diva SDK 1.0 Type Library (Version 1.0)" is now available for programs to use.
On the component toolbar (on the "ActiveX" tab) you will find four new icons that represent the four types of object exported by the Diva Server Component API: DivaSystem; DivaDevice; DivaCall; DivaInstance. You can select these objects and place them on the design form in the normal way. Secondly, the component wrapper "DIVASDKLib_TLB.pas" is generated and placed in "\Program Files\Borland\Delphi7\Imports". This should be included (on the "uses" clause of a program) to give access to all the methods and properties of the Diva SDK objects.
For example, to use the TDivaCall object, the object that represents a single telephony call:
1. Select the TDivaCall object on the toolbar and drop one on the form. You should now find that the TForm1 code has a reference included to an object, usually "DivaCall1" of type "TDivaCall".
2. Selecting this object on the form will allow you to set the relationship between events (received by DivaCall1) and which functions they activate. For example, DivaCall1 has events like "OnConnected", "OnDisconnected", "OnToneReceived". Clicking on the event field causes Delphi to automatically generate a skeleton of the procedure needed to handle the event. You can then fill in the rest of the code manually.
Notes:
1. The Diva Server SDK objects DivaSystem, DivaDevice, DivaCall, DivaInstance are imported by Delphi as TDivaSystem, TDivaDevice, TDivaCall, TDivaInstance, fitting in with normal Borland naming conventions.
2. Some of the methods are renamed relative to the Dialogic® Diva documentation PDF. This is because Delphi renames procedure when it gets a name collision. For example the "Connect" and "Disconnect" events are known as "Connect1" and "Disconnect1" in Delphi code.
If in doubt, you can always check the DIVASDKLib_TLB.pas file, which has the formal definition of all the symbols and methods.
3. When you select an object, the 'properties' list (in the Object Inspector) does not list all of the properties of the TDivaCall object. All the properties exist, though, it is only necessary to look them up in the Dialogic® Diva PDF file and write the code into your procedures.
