Multiparty instant messaging requests from an RTC 1.3 client program are sent to the custom media manager of an RTC 1.2 client program in Live Communications Server 2005 (890299)

MORE INFORMATION

Consider the following scenario:

• You have a client program that was created by using the RTC Client API version 1.2.
• The client program performs its own custom media management.
• The client program receives multiparty Session Initiation Protocol (SIP) INVITE requests from a program that was created by using the RTC Client API version 1.3.

In this scenario, the INVITE requests are sent to the custom media manager component in your program. They are not handled by the RTC Client version 1.2 stack.

The RTC Client version 1.2 stack does not understand the initial Session Description Protocol (SDP) data that is sent by the RTC Client version 1.3 stack. In this scenario, if you did not use a custom media manager, the RTC Client version 1.2 stack would return a 488 response to the initial request. This 488 response would cause the RTC Client version 1.3 stack to fall back to the correct SDP format. The invitation would then complete successfully. However, because you use a custom media manager, the custom media manager handles the RTC Client version 1.3 SDP format.

If your custom media manager cannot handle the SDP format, configure your custom media manager to send a 488 response to the RTC Client version 1.3 request. To do this, call the following method:For additional information about the RTC Client, visit the following Microsoft Web site: For additional information about how to obtain the RTC Client API binary files, visit the following Microsoft Web site: