Dit artikel is gearchiveerd. Het wordt aangeboden in de huidige vorm en wordt niet meer bijgewerkt.
Real-Time Communication (RTC) client communications may not work if the client is located behind a Network Address Translation (NAT) device. The hotfix that is described in this article enables NAT-aware programs to configure the RTC API to use the correct address and port when it sets up the audio or video streams. After you install this hotfix, clients that are located behind the NAT device can use audio and video communications with other clients or gateways that are located outside the NAT device. Note that this hotfix does not help clients that are located behind a NAT device to connect to the Session Initiation Protocol (SIP) server. This hotfix does not enable Microsoft Windows Messenger clients that are located behind a NAT device to use audio and video with each other. However, the hotfix does enable Windows Messenger clients that are located behind a NAT device to communicate with phone gateways.
The RTC client was not originally supported behind a NAT device.
A supported fix is now available from Microsoft, but it is only intended to correct the problem described in this article and should be applied only to systems experiencing this specific problem. This fix may receive additional testing at a later time, to further ensure product quality. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows XP service pack that contains this fix.
To resolve this problem immediately, download the fix as instructed below or contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
NOTE: In special cases, charges that are normally incurred for support calls may be canceled, if a Microsoft Support Professional determines that a specific update will resolve your problem. Normal support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The following file is available for download from the Microsoft Download Center:
For additional information about how to download Microsoft Support files, click the article number below to view the article in the Microsoft Knowledge Base:
119591 How to Obtain Microsoft Support Files from Online Services
Microsoft used the most current virus detection software available on the date of posting to scan this file for viruses. Once posted, the file is housed on secure servers that prevent any unauthorized changes to the file.
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name ------------------------------------------------------ 12-Oct-2001 14:10 5.1.2601.0 139,264 Aec.sys 11-Dec-2001 16:43 5.1.2600.16 844,288 Dxmrtp.dll 06-Feb-2002 15:41 5.1.2600.28 549,888 Rtcdll.dll 12-Oct-2001 14:22 5.1.2600.16 6,016 Splitter.sys 27-Nov-2001 14:20 5.1.2600.21 56,832 Usbaudio.sys 30-Jan-2002 18:07 5.1.2600.28 19,200 Usbuhci.sys
Microsoft has confirmed this to be a problem in the Microsoft products that are listed at the beginning of this article.
The RTC client Application Programming Interface (API) is a new feature of Windows XP. This feature is designed to facilitate the rapid development of real-time programs such as instant messaging and video-conferencing software.
Session Initiation Protocol (SIP) is an emerging Internet standard that allows flexible integration of messaging, presence, multimedia conferencing, and real-time communications such as telephony. SIP is designed to be modular to integrate programs in innovative ways, and is extensible to support new technologies