The Sender and Receiver Overview figure presents a simplified view that illustrates a uni-directional data transmission. A bi-directional transmission, such as a audio or video conference, includes both the Sender and Receiver objects running at the same time and possibly controlled by the same application program.
Notes:
- A multi-person conference does not include multiple instances of the Receiver object. Instead, the Receiver object is designed to scale as needed to support up to 10 incoming data streams being transmitted on the same multicast connection address/port combination, or just the same port as is the case in a unicast network connection. The Multi-person Conferencing figure depicts this relationship.
- If the audio mixer is not configured for use, the Receiver object returns an error event for each incoming source that is unable to open the audio device. Generally, this is all but the first source that is received. However, if another program is using the audio device, then all sources generate an error event. The error event that is generated indicates that the audio device is in use and this source is unable to access it. As a result, audio playback for the source is automatically put in a mute state by the Receiver object. An application program should detect this error event and take the appropriate action to handle the source being muted. This action might include toggling a mute button on the user interface to indicate the audio is muted. The error event that is generated is error code MonitorADMMFail.
For introductory information, see Programming with Collaboration Objects.
