Microsoft KB Archive/314630

From BetaArchive Wiki
Knowledge Base


XCCC: Allocating Multicast Addresses for Audio and Video Conferences

Article ID: 314630

Article Last Modified on 10/28/2006



APPLIES TO

  • Microsoft Exchange 2000 Conferencing Server Service Pack 1
  • Microsoft Exchange 2000 Conferencing Server Service Pack 2



This article was previously published under Q314630

IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry


SUMMARY

This article describes how to allocate multicast addresses for audio and video conferences.

MORE INFORMATION

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

The Conference Management Service component in Exchange 2000 Conferencing Server provides multicast-aware participants with multicast addresses for audio and video conferences if there are not any Multicast Address Client Allocation Protocol (MADCAP) servers available on the network.

This function provides a randomly allocated multicast address to all conferencing participants from the standard class D address range. If you need a specific address or range instead of a randomly assigned address, you can use the following registry entry to designate the number of addresses that you want to use and the starting point at which these addresses are assigned.

NOTE: 224.0.0.0 through 224.0.0.255 is a reserved range that is used for multicast administrative functions like registration and propagation between routers. Your scopes should be set to something other than these IP addresses.

To designate the number of addresses that you want to use and the starting point at which these addresses are assigned:

  1. Start Registry Editor (Regedt32.exe).
  2. Locate the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange

  3. On the Edit menu, click Add Key, and then add the following key:

    Key Name: Conferencing
    Class: Leave blank

  4. Locate the following registry key:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Conferencing

  5. On the Edit menu, click Add Key, and then add the following key:

    Key Name: Parameters
    Class: Leave blank

  6. Click the newly-created Parameters key, click Add Value on the Edit menu, and then add the following values:
    • Value Name: No Random Mcast Address
      Data Type: REG_DWORD
      Data: 0
    • Value Name: Random Mcast Address Count
      Data Type: REG_DWORD
      Data: The amount of addresses that are needed, for example, 400
    • Value Name: Random Mcast Address Start
      Data Type: REG_SZ
      String: start of multicast address scope
  7. Quit Registry Editor.


Keywords: kbhowto KB314630