CopiaFacts can process a collection of infobox files in a .IBC (Infobox Collection) file. IBC files allow you to tidy up your image directory by reducing the number of small files. They also allow Copia and third-parties to prepare 'canned' applications which can be distributed in a single file. Using IBC files can also significantly enhance the responsiveness of your CopiaFacts application.
Infobox Collection files are conventionally named with extension .IBC. However if the included infobox files contain references to encrypted variables, you should name the infobox collection with an .IBCA extension. This will cause COLLECT to prompt for a password and generate an authentication digest in the file. Collection files with authentication cannot be used in releases of CopiaFacts earlier than version 8.
The IBC file is logically a concatenation of all the component infobox files. The file contains no image, voice or data look-up files, which continue to be held externally. The file is listable, but contains cross-references which make it extremely unwise to attempt to edit it manually.
File Creation and Maintenance
Currently, an IBC file can only be created from a set of IIFs using the COLLECT program. You should retain the original IIF files for maintenance purposes.
Specifying and Using IBC Files
To use an IBC file, it must be preloaded from the configuration file using the $load_ibc command:
$load_ibc line ibcname ibcpathname
$load_ibc * FFVM c:\faxfacts\image\ffvoice1.ibc
The line can be the usual line number or "*" for all lines. The ibcname field is the logical name for the IBC application (for example FFVM for a voicemail application). You may load multiple IBC files with the same logical name and the first one that matches name and line will be selected.
To use infoboxes from an file, a special keyword of "IBC" must be used on a $script_locn command in place of a directory name. This keyword is followed by the logical name of the IBC file. For example:
$script_locn FFVM0000 FFVMzzzz IBC ffvm
When an infobox number lies in the range corresponding to an IBC file, a matching IIF in the IBC file is processed exactly as if it was an IIF in the same directory as the IBC file. This implies that an accompanying voice file (for example containing a menu script) should be placed in the same directory as the IBC file if specified as $image_desc standard in the IIF.
You can override individual components of an IBC file by including an IIF file in a directory specified on an earlier $script_locn command with a matching range.
For IBC 'application' files, it is recommended that all infobox names in the file should start with a unique 4-character prefix, of which the first two letters define the originator. All Copia-supplied infobox files distributed as IBCs will start with the letters FF. For example, a Copia-supplied voice-mail application might contain infoboxes FFVM0001 to FFVMZZZZ.
If you wish to make your IBC files available to other CopiaFacts users, please contact Copia to register a unique two-letter prefix code.
If you build an IBC just to improve the performance of your existing set of numeric infobox files, it is not necessary to change the names of the files. However you should probably place the IBC file in your regular script directory so that all files remain accessible, and you will need $script_locn commands for both the script directory and the IBC.
Voice (.VOX) files supplied with and used by an IBC (for example, menu scripts) will normally need to be re-recorded in your own voice to match your other voice files. For this reason the voice files are not included in the IBC file, but should be kept in the same directory as the IBC file. To simplify recording of these files, the $type studio command has a parameter to specify an infobox prefix code. Using the example quoted earlier, an infobox prefix code of FFVM will allow you to record a file such as FFVM0007.VOX just by selecting entry '7' in the Recording Studio.
VOX files containing descriptions of actual document images should be kept in the same directory as the image files, as usual.
Re-Loading IBC Files
If you modify the contents of an IBC file, you can use the button on the options page of COPIAFACTS.EXE to reload it while CopiaFacts is running. When you press the button, all defined IBC files are reloaded (and therefore must be available for reloading). The contents of the original IBC files are retained for processing calls that are in progress at the time you reload, and discarded when no longer in use for any call.