July 19, 1996
Communique! 4.2 New Features
| Communique! 4.2 adds the following improvements and enhancements over earlier
versions. New Functionality The multicast addresses that are used by Communique! can now be configured by the user. The addresses are specified in the C.INI file under Windows 3.x, and in the Registry for Windows 95 and Windows NT. In the Registry they must be string values, not numbers.
If custom addresses are not specified, the default values are used. Each participant uses a port and address calculated as follows: The default port number (55555 for video and 55811 for audio) plus this participant handle (generated according to the order in which the users joined the conference) is used. Multicast address includes two default octets (224.88 for video and 224.77 for audio) and two octets derived from this participant local IP address. If the port numbers and multicast addresses are specified in the configuration file or Registry, the port number is generated by adding the participant handle to the port number that is specified. The multicast address is comprised of the address specified in the file, with the participant handle added to the last octet in the address. Communique! now accepts arguments that enable it to start conferences as soon as it is launched. In order to start a conference from the command line, you can either include a conference address as the argument; for example:
or the path to a .ICE file
You can use the command line arguments to start a conference, or to initiate a conference when Communique! is already loaded. This enables you to create shortcuts that will automatically start conferences. If you attempt to launch Communique! with a command line argument when Communique! is already loaded, the existing instance of Communique! will be used, but it will try to invite the users included on the command line (or in the .ICE file) to the conference. If you are already in a conference, Communique! will attempt to add the members specified in the command line. The format of a .ICE file is as follows:
Osprey-1k Users Communique! 4.2 for Windows NT (Intel) requires version 1.1.1 or higher of the Osprey-1k series software drivers. Please refer to the Osprey web site (http://www.mmac.com) for the latest information concerning the Osprey 1004 audio/video board. For mixed video or multi-way conferencing, under Windows 95, the user must select Use Software Codec Only. This is done using the IP64 Selector. Currently, if the user selects use HW/SW they will be unable to view multiple video or mixed video formats, i.e., H.261 to CellB. Using the HW Codec the user may see a still frame of the incoming video in their TV Station. In addition, if the TV Station window is repainted the local video will show up on the viewer until the incoming video repaints. Contacting Technical Support InSoft technical support has been relocated to MDL's corporate headquarters in Bellevue, Washington. For assistance, contact MDL's technical support staff. |
Return to Desktop Video Conferencing Page