Filter
Top Products
Conferencing API Programming Guide — August 2006 19
5
5.Application Development
Guidelines
This chapter contains guidelines for developing conferencing applications. The following topics
are covered:
• Using Symbolic Defines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
• Using Conferencing Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
• Creating a Conference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
• Conference Bridging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
• Terminating an Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
• Data Structure Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
• Multiprocessing Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
• Multithreading Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.1 Using Symbolic Defines
The numerical values of defines may not remain the same as new versions of the software are
released. It is recommended that you do not use a numerical value in your application when an
equivalent symbolic define is available. Symbolic defines are found in the header files; for
example, cnflib.h, cnfevts.h, cnferrs.h, and srllib.h.
5.2 Using Conferencing Devices
The types of devices used in the conferencing API library and their naming convention are as
follows:
• virtual board device, called cnfBx, where x is the logical board number
• conference device, called cnfBxCy, where x is the logical board number and y is the conference
device channel
• party device, called ptyBxPz, where x is the logical board number and z is the party device
channel
All devices are identified by a unique SRL handle. All subsequent references to the opened device
must be made using the handle, until the device is closed.
The virtual board device is the parent device for both the conference device and the party device.
You must open a virtual board device before opening a conference device or party device. After a
board device is opened, you can open and initialize all conference devices at once, and/or all party