Platform SDK: TAPI

Multicast COM Interfaces

The multicast COM interfaces allow access to the network's facility for allocating, renewing, and releasing leases on multicast addresses. They encapsulate a set of Win32 functions and data structure definitions. The COM interfaces free the programmer from the burden of understanding and manipulating these data structures. Moreover, because TAPI 3.0 itself is COM-based, these interfaces make multicast address allocation accessible in a way that is consistent with the other facilities provided by TAPI 3.0. Applications written using Visual Basic®, Java, or scripting languages that cannot normally access the Win32 API directly are able to use these interfaces.

Multicast address allocation is currently the subject of an IETF working group. To access current information, query on "MDHCP" or "MADCAP" and "Internet draft" using any Internet search engine. In addition to MADCAP, the proposed architecture includes a protocol for server-to-server coordination within a domain or AS, as well as a protocol for interdomain coordination. While this architecture is currently evolving, the client need not concern itself with the details of this scheme.

This component currently supports only IP version 4 addresses.

Note  The protocol used for these interfaces is currently named MADCAP. In previous versions it was known as MDHCP.

The multicast object is created by calling CoCreateInstance on the IMcastAddressAllocation interface. The IMcastAddressAllocation interface exposes the EnumerateScopes method, which allows an application to get a list of all available multicast scopes.

Once a working scope has been obtained, the RequestAddress method is used to request a multicast address from the server. If the request is successful, an IMcastLeaseInfo pointer is returned. The EnumerateAddresses method exposed by this interface can then be used to obtain the addresses.

Each Media object associated with the conference exposes an ITConnection interface. The ITConnection::SetAddressInfo method allows assignment of the multicast addresses obtained to the media of the conference. The address must be set for each ITConnection interface of every Media object associated with the conference.