Click here to Skip to main content
11,928,078 members (27,067 online)
Click here to Skip to main content
Add your own
alternative version


34 bookmarked

Creating a Managed Automated Information Agent (mBot)

, 12 Aug 2004 CPOL
Rate this:
Please Sign up or sign in to vote.
mBot manages multiple RTC Client objects and exposes interfaces to them via .NET Remoting and .NET Web Services so that they can be managed and used remotely by other .NET applications or by entirely different platforms such as a Java J2EE/SOAP application like Jabber IM running on Linux or Windows.
Sample Image - Managed_RTC_LCS_Bot.gif


In his article “Implementing Automated Agents (Bots) using the RTC Client API[1],” Robert Osborne [Microsoft] provides a reasonable starting place for framing an automated information agent, or instant messaging (IM) bot. This article is also about bots, but takes a very different approach by utilizing Microsoft’s modern .NET technologies to enable a bot infrastructure with C#, .NET Remoting Services, and Web Services. Moreover, the significant limitations of the RTC Client 1.2 API’s STA threading model are treated, making the infrastructure code for the bot much cleaner and better prepared to adapt to forthcoming collaboration APIs, such as those found in Longhorn.

The figure above provides an aerial view of what this article sets out to do: Craft a facility, called mBot, that will manage multiple RTC Client objects and expose interfaces to them via .NET Remoting and .NET Web Services so that they can be managed remotely by other .NET applications or from entirely different instant messaging platforms such as a Java J2EE/SOAP application like Jabber running on Linux or Windows.

This article is more about framing a managed open infrastructure around the RTC Client COM object than it is about the RTC Client COM object itself. The RTC Client COM object is most certainly an essential central messaging component, but it is also one whose COM API we desire to abstract away with .NET Remoting and Web Service methods.

Documentation and Source Code Provided

The two zip files contain .NET C# code (source) and a 60 page PDF file (demo) that thoroughly documents the solution.

[1] "Implementing Automated Agents (Bots) using the RTC Client API"


  • 12th August, 2004: Initial post


This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


About the Author

Web Developer
United States United States
Michael J. Chase has been presenting communication technology courses for the past twenty years to companies such as AT&T Bell Labs, Avaya, Digital (now HP/Compaq), the Department of Energy ( Los Alamos and Livermore ), IBM, Lucent, StorageTek, Texas Instruments, et al.

Mr. Chase has served as the assistant director for the graduate program for Telecommunications at the University of Colorado Boulder where he has also taught telephone systems and computer systems architecture at the graduate level. He as worked at Bell Laboratories and IBM. He has the degrees BSEE (Columbia), MSCS (USC), and an MS Telecommunications (Colorado). Mr. Chase has published in the Microsoft Systems Journal.

His current contract work utilizes C#, C++ and Java in client/server applications, embedded telemetry systems, and real-time collaboration systems. Mr. Chase has participated as an inventor in multiple patent applications in the VoIP arena and has served as an expert witness in intellectual property disputes involving patent infringement and licensing issues surrounding telecommunications software. Mr. Chase has created training and education courseware for RTC and LCS 2003 platform developers in a managed .Net environment.

You may also be interested in...

Comments and Discussions

GeneralMonitor line from RTC APIs Pin
MyRitu7-Nov-07 15:23
memberMyRitu7-Nov-07 15:23 
GeneralTCP vs TLS Pin
chileric9-May-07 12:03
memberchileric9-May-07 12:03 
QuestionCan I use RTC 1.3? Pin
chileric30-Apr-07 12:53
memberchileric30-Apr-07 12:53 
AnswerRe: Can I use RTC 1.3? Pin
RTC-LCS-Developer2-May-07 9:10
memberRTC-LCS-Developer2-May-07 9:10 
QuestionProblem on LCS Server [modified] Pin
Tom_Ky24-Oct-06 0:58
memberTom_Ky24-Oct-06 0:58 
QuestionRe: Problem on LCS Server Pin
Tom_Ky24-Oct-06 15:48
memberTom_Ky24-Oct-06 15:48 
GeneralProblems running the example Pin
MARCO PICCC7-Jul-06 5:21
memberMARCO PICCC7-Jul-06 5:21 
GeneralRTC Conversation Pin
riccardobecker25-Jun-06 3:42
memberriccardobecker25-Jun-06 3:42 
QuestionRTC over mobile Pin
alon.heller13-May-06 23:09
memberalon.heller13-May-06 23:09 
QuestionHow to set IM's font and color ? Pin
xz_king13-Mar-06 4:41
memberxz_king13-Mar-06 4:41 
GeneralJabber Pin
arash_14-Dec-05 11:47
memberarash_14-Dec-05 11:47 
GeneralIt's helpful to me . Pin
xz_king7-Nov-05 21:11
memberxz_king7-Nov-05 21:11 
GeneralRTC audio stream Pin
serup27-Oct-05 5:59
memberserup27-Oct-05 5:59 
GeneralSame Old error Pin
Anandakumar Thangaraju29-Nov-04 1:19
memberAnandakumar Thangaraju29-Nov-04 1:19 
GeneralRe: Same Old error Pin
RTC-LCS-Developer1-Dec-04 7:50
memberRTC-LCS-Developer1-Dec-04 7:50 
GeneralRe: Same Old error Pin
Anandakumar Thangaraju2-Dec-04 1:32
memberAnandakumar Thangaraju2-Dec-04 1:32 
GeneralRe: Jabber is not Java Pin
RTC-LCS-Developer17-Aug-04 13:19
memberRTC-LCS-Developer17-Aug-04 13:19 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

| Advertise | Privacy | Terms of Use | Mobile
Web03 | 2.8.151126.1 | Last Updated 13 Aug 2004
Article Copyright 2004 by RTC-LCS-Developer
Everything else Copyright © CodeProject, 1999-2015
Layout: fixed | fluid