Real Time Communications (RTC) missing?

[Guest]

I'm aware of an XPe add-on update for Real Time Communications (RTC) related
to the SIP protocol (VoIP).

- RTCDLL Policy for XP SP2
- RTCDLL XPSP2
- RTCRES XPSP2

These components are included in some XPe non critical update. They also
appear to even be post-SP2. I've been unable to find any reference to these
components in searches. Perhaps they're rolled in updates for another KBXXXXX
update that's not obvious? I do have XPSP2 installed. Can anyone enlighten
me as to which update they are included in?

 

[KM]

Paul,

As a QFE for SP2 I only recall the fixed EWF API lib posted by Microsoft. No any other SP2 related QFEs.

Maybe some XP Pro related QFEs (updates), not componentized for XPe? Did you check WU site?

 

[Guest]

KM,

I've moved my embedded studio on a faster workstation. It seems that the old
build system had MS-released RTC components available in TD. However when i
look for those "RTC*" components in TD on the new system, they're missing.
Unfortunately the guy who built the original system can't recall what update
they came from. I seem to have all the available upgrades including XPSP2.
I've spent the better part of 2 days searching through the download areas.
Is there a way to track for which update repository for these items belong?

Thanks for the help,
Paul

 

[Guest]

Oh my, disregard.. apparently these components have an even lower visibility
setting then what my TD was set to.

Thanks anyway,
Paul

 

[Guest]

It seems that RTC is still a problem for me on the target system (dependency
problems??). Further, i find even more RTC related components in the CDM
which are not visible in the TD despite my component visibility being set to
the lowest possible setting (100.) How do i make ALL these visible in TD??

- RTC user Agent Library
- RTC user Agent Library - HotFix Q835732

The same filter for "rtc" yields much more results in CDM then TD.

Thanks,
paul

 

[KM]

Paul,

It seems that RTC is still a problem for me on the target system (dependency
problems??). Further, i find even more RTC related components in the CDM

Can you list those here? I can't find any differences in returned components between TD and CDM if I just create a filter by 'rtc'.

which are not visible in the TD despite my component visibility being set to
the lowest possible setting (100.) How do i make ALL these visible in TD??

There is some ways to do that but you won't gain anything. All the component with Visibility < 100 are for special purposes (like
Base Instance, EOL components, some NTe components, etc.).

- RTC user Agent Library

As far as I understand this component does not bring any files/reg.entries but just a bunch of dependencies required to get RTC
working.

The component Visibility level is 200 so you should see it in TD.

(Ther is a EOL version of the component with Vis=0 but you don't really need to mess up with it)

- RTC user Agent Library - HotFix Q835732

I don't have this one so can't really tell you what was fixed there. Perhaps, you can compare the difference in dependency lists.

The same filter for "rtc" yields much more results in CDM then TD.

Again, can you show us the differences?

You will see a bunch of irrelevant components in TD or CDM if you just filter by 'RTC'.
I think only the following would make sense:
RTC User Agent Library
RTCDLL XPSP2
RTCRES XPSP2

KM

 

[Guest]

Again, can you show us the differences?

In CDM i get:

- RTC user Agent Library [Versions 5.1.2600.1106,R1507]
- RTC user Agent Library [Version 5.1.2600,R620]
- RTC user Agent Library - Hotfix Q835732 [Version 5.1.2600.1106.1,R1900]
- RTCDLL Policy XPSP2 [Version 5.1.2600, R2890]
- RTCDLL XPSP2 [Version 5.1.2006, R2890]
- RTCRES XPSP2 [Version 5.1.2600.2180,R2890]

In TD i only get:

- RTCDLL Policy XPSP2 [Version 5.1.2600, R2890]
- RTCDLL XPSP2 [Version 5.1.2006, R2890]
- RTCRES XPSP2 [Version 5.1.2600.2180,R2890]

I expect to see at least one (probably just one) reference to "RTC User
Agent Library" in TD, but i see none. I'm anxious to add this component
because it seems that we are missing a dependency for RPC. I agree maybe its
not the source of my problem. We're unable to use the RTC component in our
SIP application as RTP will exit with error code 0x80ee0075 or
RTC_E_MEDIA_SESSION_NOT_EXIST, which from what I've read is a sign of
mismatched DLLs.

Thanks,
Paul

 

[KM]

Paul,

This is weird. You should see the "RTC user Agent Library" component in TD under "Software : System : Networking & Communications :
Infrastructure" category.
Try removing the Hotfix'ed RTC component from database (maybe it is masking other RTC components).

If you still can't get it to be seen in TD, you either:
- Re-install you SP1 database
- Move to SP2
- Manually include all the RTC dependencies. As I mentioned the "RTC user Agent Library" component is nother more that just a
list of dependencies (no files, no reg.settings).

Here is all the component's dependencies for you (please rab only the latest revisions from the list):

Dependency on "Common Control Libraries Version 5" caused by "COMCTL32.DLL"
Dependency on "Win32 API - Kernel" caused by "KERNEL32.DLL"
Dependency on "Win32 API - Advanced" caused by "ADVAPI32.DLL"
Dependency on "Primitive: Secur32" caused by "SECUR32.DLL"
Dependency on "Primitive: Ole32" caused by "OLE32.DLL"
Dependency on "Primitive: Oleaut32" caused by "OLEAUT32.DLL"
Dependency on "Win32 API - User" caused by "USER32.DLL"
Dependency on "Win32 API - GDI" caused by "GDI32.DLL"
Dependency on "RPC Local Support" caused by "RPCRT4.DLL"
Dependency on "Primitive: Shell32" caused by "SHELL32.DLL"
Dependency on "Wininet Library - Hotfix Q321232" caused by "WININET.DLL"
Dependency on "Primitive: Winmm" caused by "WINMM.DLL"
Dependency on "Primitive: Wsock32" caused by "WSOCK32.DLL"
Dependency on "Primitive: Ws2_32" caused by "WS2_32.DLL"
Dependency on "Primitive: Iphlpapi" caused by "IPHLPAPI.DLL"
Dependency on "Primitive: Crypt32" caused by "CRYPT32.DLL"
Dependency on "Routing Common Files" caused by "RTUTILS.DLL"
Dependency on "Primitive: Msasn1" caused by "MSASN1.DLL"
Dependency on "Msxml Libraries" caused by "MSXML.DLL"
Dependency on "TAPI Terminal Manager" caused by "TERMMGR.DLL"
Dependency on "DirectShow Core" caused by "QUARTZ.DLL"
Dependency on "Primitive: Ntdll" caused by "NTDLL.DLL"
Dependency on "Active Template Library (ATL)" caused by "ATL.DLL"
Dependency on "Microsoft Visual C++ Run Time - Hotfix Q305601" caused by "MSVCRT.DLL"
Dependency on "Primitive: Shlwapi" caused by "SHLWAPI.DLL"
Dependency on "Primitive: Dnsapi" caused by "DNSAPI.DLL"
Dependency on "TAPI Audio, Video and RTP Filters" caused by "DXMRTP.DLL"
Dependency on "Netmeeting" caused by "CONF.EXE"


--
Regards,
KM, BSquare Corp.

Again, can you show us the differences?

In CDM i get:

- RTC user Agent Library [Versions 5.1.2600.1106,R1507]
- RTC user Agent Library [Version 5.1.2600,R620]
- RTC user Agent Library - Hotfix Q835732 [Version 5.1.2600.1106.1,R1900]
- RTCDLL Policy XPSP2 [Version 5.1.2600, R2890]
- RTCDLL XPSP2 [Version 5.1.2006, R2890]
- RTCRES XPSP2 [Version 5.1.2600.2180,R2890]

In TD i only get:

- RTCDLL Policy XPSP2 [Version 5.1.2600, R2890]
- RTCDLL XPSP2 [Version 5.1.2006, R2890]
- RTCRES XPSP2 [Version 5.1.2600.2180,R2890]

I expect to see at least one (probably just one) reference to "RTC User
Agent Library" in TD, but i see none. I'm anxious to add this component
because it seems that we are missing a dependency for RPC. I agree maybe its
not the source of my problem. We're unable to use the RTC component in our
SIP application as RTP will exit with error code 0x80ee0075 or
RTC_E_MEDIA_SESSION_NOT_EXIST, which from what I've read is a sign of
mismatched DLLs.

Thanks,
Paul