1. Microsoft Office System UK Developers Conference Radisson Edwardian, Heathrow 29 th & 30 th June 2005

2. Developing Client Applications For Live Communications Graham Tyler Associate Consultant Microsoft Ltd

3. Example Client Solutions Desktop Applications Messenger Applications Customer Relationship Management Integration with existing LOB applications Games Scalable Applications NotificationsBots Web Based User Interface

4. Design Goals Create a platform for IP-based real-time communications Drive compatibility by creating the reference model for interoperability Unified session management Integration of signaling and multiple media types Superior audio/video quality Adoptive codec selection

5. Current Architecture TCP/IP RTC Client API User Application RTPSIPPINTT.120

6. Current Object Model Session Object IRTCClient IRTCClientProvisioning IRTCClientPresence IRTCSession IRTCParticipant IRTCBuddy IRTCWatcher RTC Client Object Participant Object Buddy Object Watcher Object IRTCxxxEvent Event Object

7. Extensible Presence Properties Allows additional properties Phone Number, Display Name, E-mail Address, Device Name Also allows for additional data GPS Location User Action Application needs to supply namespace, and properties

8. Multiple Points Of Presence Server can accept presence information from multiple clients Server responsible for aggregation Each client can have its own presence state set Receiving client can obtain device information

9. Multiparty IM Allows for multiple participants within IM session All participants see all Instant Messages All participants are aware of each other No roster management or other control Full mesh topology

10. Session Description Control Includes new type owned by application Use different media stack or hardware Different codecs Different types of session, and description format (e.g., Games) Enables Application to handle Sending initial description Receiving initial description NegotiationRe-negotiation

11. Call Control Has key Call Control features HoldForwardTransfer Session state management handled by APIs Application receives events for progress and updates

12. Scalable Applications Tips and tricks Threading Create multiple RTC Client objects across multiple threads All resources needed for that particular object should be created on the same thread Avoid calling any routines that might block the thread

13. Tips And Tricks Scalability Disable Media Manager Disable UPnP and NAT Discovery Turn Off Detection and Recovery for IP Address Changes Disable Serializing Disabling Firewall Detection Avoid Unnecessary Events Avoid Sending Typing Messages Notifications Adding Server Class Application as Always Online Contact

14. Chat Room And Role Agent

15. Chat Room Solution This example solution uses the RTC Client APIs to build a chat room application It allows the chat manager to create chat rooms and to control access to them via Active Directory Groups SIP IDs

16. Chat Architecture Chat Bot LCS Server ChatDB in SQL ChatClient ChatClient ChatClient ChatManager

17. Role Agent Architecture Role Agent (BOT) LCS Server Roles in SQL or A/D ChatClient ChatClient InternalClient

18. Updates For LCS 2005

19. Design Goals Continue to support a solid platform to enable real-time communications Incorporate feedback from previous APIs Enable new features for LCS 2005

20. Client Features Overview Multiple Points of Presence Start a session with a particular endpoint Pass a flag to notify app that messages are forked Federation and Archiving Flag Pass a flag to notify app of federated users in the conversation and if the conversation is being logged Client Security Disabled unauthenticated watchers, invites, messages High Availability Client failover retry logic Batch Subscribes BE NOTIFY Piggyback NOTIFY Client marshalling support

21. Multiple Points Of Presence Device ID is created when the profile is enabled String of hexadecimal values Enumerate presence devices IRTCBuddy2::EnumeratePresenceDevices Get Device ID of the presence device IRTCPresenceDevice2::get_DeviceID Add a contact on a specific device as a participant of a session Use IRTCSession3:: AddParticipantEX

22. Discussion

23. © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.