Windows Messenger OS Design Development (Windows CE 5.0)
The Microsoft® Windows® Messenger for Windows CE real-time communications software combines real–time voice and text communications with file transfer capability. In addition, Windows Messenger is presence–enabled, so that users can see who is available online before trying to contact them and also control their online status that others see.
For information about the network services that Windows Messenger uses to communicate, see Windows Messenger Architecture.
OS Design Information
The following table shows operating system design information for Windows Messenger.
Concept | Description |
---|---|
Dependencies | RTC Client API
Kerberos Authentication CryptoAPI 2.0 Certifications GIF Decoder PNG Decoder Internet Explorer Browser Control Host Standard I/O ASCII String Safe Utility Functions Windows Internet Services and Passport SSI 1.4 Authentication |
Hardware considerations | Network connection |
Modules and Components
The following table shows the components and modules that implement Windows Messenger.
Item | Module | Component |
---|---|---|
Windows Messenger | msmsgs | None |
Localizable resources | msgslang | None |
Implementation Considerations
The following table shows the Sysgen variables for Windows Messenger.
Sysgen variable | Description |
---|---|
SYSGEN_MESSENGER | Adds the Windows Messenger application that detects the presence of contacts, and provides text and voice messaging and file transfers by using .NET Messenger and Real-time Communications (RTC) services. |
The following non-Sysgen implementation considerations are also relevant to OEMs:
TCP ports must be configured so that sockets on a port remain open for extended periods of time.
For voice communications, the .NET Messenger Service establishes an outgoing TCP connection from port 6901 for all voice communications.
In the case of computer-to-computer communications, the call recipient also uses TCP port 6901.
All voice traffic also uses User Datagram Protocol (UDP) packets. The user's computer sends and receives UDP packets using a dynamic port.
For file transfers, both incoming and outgoing TCP connections use this range of ports: 6891 to 6900. These ports allow up to 10 simultaneous file transfers per sender. If you open only port 6891, users are able to do only one file transfer at a time.
To allow users to have a direct connection to instant messaging services through a firewall, instruct them how to:
- Open outgoing TCP connections to port 1863 on proxy servers.
- Determine which kind of proxy server their networks use (HTTP, SOCKS4, or SOCKS5) and enter the corresponding details in the Windows Messenger application (such as server name and port number) by choosing the Tools menu, choosing Options, changing to the Connection tab, and entering the information.
- Verify that the internal local area network (LAN) has access to the Domain Name System (DNS) servers to resolve the names of external resources.
See Also
Send Feedback on this topic to the authors