Do you find the Support WebCast transcripts helpful?
Let us know!

Note This document is based on the original spoken Support WebCast transcript. It has been edited for clarity.

Juan Flowers: My name is Juan Flowers. I would like to say hello and welcome to everyone today that is listening and also viewing our Support WebCast. In today’s topic we’re going to talk about Microsoft® Windows Messenger for Windows® XP.

To begin (slide 2), the ubiquity of Internet connections provides an ideal medium for instant interactive communications. E-mail is terrific for communications when you don’t an immediate response. Telephone communications are, of course, essential in business and personal intercourse. Instant Messaging, with a program like Windows Messenger, provides a third communications method that offers a number of other advantages.

The first advantage is that it’s interactive. You can exchange questions and answers in real time instead of sending e-mail messages back and forth over a period of hours, days, or weeks.

The second advantage is that it’s not as intrusive as telephone communication. If you choose, you continue working in other programs or with other activities while you carry out an Instant Messaging session.

The third advantage is that it’s more private. Users can control the display of their availability on other users’ screens. You can block specific people from seeing your availability and from seeing and also sending you messages. As with Caller ID, you can see who is trying to reach you before you answer. Strangers can’t join your conversation as they can in an Internet chat session.

The fourth advantage, and our last advantage, is that it’s versatile. As with e-mail, you can send and receive text and files. You can also make voice calls as you would with a telephone. In addition, you can send and receive video and work collaboratively with a whiteboard or a program. You can take control of another user’s computer with that person’s permission, of course. Also, it serves as an alert service by notifying you of new e-mail messages that appear in your Hotmail mailbox. Furthermore, it notifies you of events on your calendar, changes in certain stock prices, and other events you choose.

Today’s overview (slide 3) will cover the following topics: system requirements for Microsoft Windows Messenger for Windows XP, new features, and troubleshooting common issues, of course.

Let’s begin with the system requirements (slide 4). As you see here, we’re going to talk about the hardware, the Internet connection, of course, Microsoft .NET Passport. The minimum system requirements. To begin with, a computer with a 300 megahertz (MHz) or faster processor clock speed is recommended, but a minimum speed of 233 MHz is required. It can be either a single- or a dual-processor system. Intel Pentium/Celeron family or AMD K6/Athlon/Duron family or compatible processor is recommended.

The operating system: Windows XP Professional or Windows XP Home Edition. You must have 10 megabytes (MB) of disk space available for installation. The memory, 128 MB of RAM or more is recommended, but 64 MB is the minimum that is supported. It may limit the performance and some features.

For the video display, we require a Super VGA 800×600 or higher resolution video adapter and monitor.

For networking, network adapter appropriate for the type of local area, wide area, wireless, or home network you wish to connect to and access to an appropriate network infrastructure. Access to third-party networks may require additional charges.

For text instant messaging, voice and video conferencing, and application sharing, both parties need a Microsoft .NET Passport account and Internet access or Microsoft Exchange 2000 Server Instant Messaging account and network access. Some configurations may require a download of additional components.

For voice and video conferencing, both parties also need, preferably, a modem with the speed of 33.6 kilobits per second (Kbps) or faster and a working connection speed of 33.6 Kbps or faster; a speaker and a microphone that plug in either the sound card or the USB port or a headset that plugs into either the sound card or the USB port.

For video conferencing, both parties also need a PC video camera compatible with Windows XP. For more information, you can go to the Start menu and select All Programs, and then select the Windows Catalog on specific video cameras that are considered to be compatible.

Then lastly, of course you need Windows XP.

A special note, for voice calls or video calls, you obviously get better quality with greater bandwidth. Cable or DSL connections are ideal, but you can actually get decent results with a dial-up connection. At a bare minimum, you will need a 28.8 Kbps modem that’s connected at 28.8.

For application sharing, both parties also need a modem with the speed of 33.6 Kbps per second or faster and a working connection at this particular speed.

For Remote Assistance, both parties must be running Windows XP and be connected by a network.

Lastly, for sound, a modem with a speed of 33.6 Kbps or faster and working connection speed of this rate as well.

Note, actual requirements will vary, based on your system configuration and applications and features you choose to install. Additional available hard disk space may be required, if you are installing over a network.

Let’s talk more specifically about the Internet connection. Another basic requirement to run Windows Messenger is simple. You need a working Internet connection and a .NET Passport. This is true even if you plan to use Windows Messenger only to converse with others on your local area network because your list of contacts is available only when you’re connected to the Internet.

Moving along to the .NET Passport. A .NET Passport provides the connection to the server where your contacts are stored. Because your contacts are stored on a central server, they’re available to you no matter where you are, when you sign in using your Passport. If you haven’t already obtained a .NET Passport and linked it to your user account, you can do so through the User Accounts option in Control Panel. But an easier way would be to double-click the Windows Messenger icon in the notification area. Unless your account is already linked to a .NET Passport, this action opens the .NET Passport Wizard. The wizard helps you obtain a .NET Passport if you don’t have one and then links it to your user account so that you can log in automatically whenever you sign on into your computer.

Note, when Microsoft started its Passport service, to get a Passport you had to have an e-mail address at hotmail.com, msn.com or passport.com. You can still use one of these addresses if you have one or you can use the wizard to set up a Hotmail account, but you can now link a Passport to any e-mail address.

We just got finished talking about the system requirements and now we’re going to move along to the new features (slide 5). As you see here, the features that we’re going to talk about today that are core features within the Windows Messenger product and Windows XP. First one is PC-to-phone. Second one is PC-to-PC using voice and video. Third one is sending and receiving files. Fourth is whiteboard and application sharing. Fifth is Remote Assistance. Sixth is using Microsoft Hotmail and the Microsoft .NET Alerts (alerter notification). The next one is MSN® add-ins. Lastly, we have other features to talk about.

PC-to-phone (slide 6). Before you can make a phone call, you must either sign up with a voice service provider or call from a corporation that provides an account. To sign up with a voice service provider, unless you are calling from a corporation that pays for your phone service, you’ll need a voice service account to pay for your calls.

One, in the Phone window, click Get Started Here. To get there on the Messenger Actions menu, click Make a Phone Call. You can view this particular screen shot and this is generally the first screen that you will initially see when you try to perform this task.

Two, on the Select a Voice Service Provider page, click the provider you want.

Then three, each provider offers different plans. You may want to click the Learn More link to read more about each one before you decide.

Remember, you are signing up directly for a voice service with the provider who is rendering the service, not with Microsoft. For account status, contact them. You may not be able to place a call immediately. You will know your account is activated when you see the logo of your provider in the phone window. Click Make a Phone Call to open it. It could take as long as a day or two for the provider to activate your account.

Note, if you want to change voice service providers, you must cancel your existing account before signing up for a new one. After subscribing to a voice service provider and your account is activated, you can make a call by following these simple steps. First step is in the Main Messenger window, click Make a Phone Call under I want to or right-click the name of the person you want to call and then click Make a Phone Call and then choose from the numbers they have published.

Two, in the Phone window, type the phone number, including the area or city code, even for local calls, or choose the number from your list of previously called numbers. Be sure the country code for the country you’re calling is selected in the drop-down list to the left of the number. Do not type the country code or the out-of-country access code in the same box with the phone number.

Third step is to click Dial. To place a phone call it may take a moment for your call to go through, depending on network conditions.

Then the fourth step, click Hang Up to end the call.

Some additional notes: the first time you enter a phone number, type a name after it for easy identification on your list. You may be able to enter additional digits to reach extensions or to respond to prompts after your call goes through.

If you are on the local area network with a firewall, as you may be in a corporation, or if you are behind a network address translator, also known as NAT, you may not be able to make phone calls from your computer.

If I want to is not visible, click Show Actions Pane on the Messenger Tools menu.

We’ll now move on to PC-to-PC, using voice and video (slide 7). Very similar to using PC-to-phone, but we have some different procedures. To call a computer, you can call an online contact computer from your computer and talk using your microphone. You must both have a full duplex sound card with a headset or speakers and a microphone or a USB port with a USB headset.

You can also use video cameras to see each other when you talk. The main window, right-click the name of an online contact and click Start a Voice Conversation, or click Start a Voice Conversation under I want to. Select the contact you want to talk to and click on OK. Or in the conversation window, usually on the right-hand side, you’ll see Start Talking. If a contact does not accept your invitation, it may be because the person does not have the necessary sound hardware. To end the conversation, just click Stop Talking.

If you’re on a local area network behind a firewall for example, again on a corporate network, you can talk with someone who is behind the same firewall that you are, but you may not be able to connect on a computer-to-computer call with someone outside the firewall. If the I want to option is not visible, click Show Actions Pane on the Tools menu.

To call a computer using voice and video. You can call an online contact and use your microphone to call while using your cameras to see each other. You must also both be using Windows XP and have a full duplex sound card with a headset or speakers and a microphone or USB port with a USB headset. In the conversation window, click Start Camera in the sidebar to see your picture inset in your contact’s picture with options below the picture, make sure that Show My Video as Picture-in-Picture is checked.

To stop sending your video image, click Options and then click Stop Sending Video. You will continue to receive the other person’s image, but your image will freeze in your contact’s conversation window. If you do not see the sidebar, open it by clicking Show Sidebar on the View menu. If the contact does not accept your invitation, it may be because the person does not have, again, the necessary sound hardware. To end the conversation, click Stop Talking or Stop Camera.

If the person you are calling doesn’t have a camera and you do, then they will see you, but you won’t be able to see them. If you invite someone to a video conversation and you don’t have a camera, you will see them if they do have a camera. If the person you are calling doesn’t have Windows XP, they won’t be able to accept the invitation.

If you’re on a local area network behind a firewall, again, speaking on a corporate network, you can talk to someone who is behind the same firewall as you are, but you may not be able to connect to a computer-to-computer call with someone outside your firewall.

Moving along (slide 8). Sending and receiving files. Windows Messenger provides a convenient method of sending a file to another Passport user. Using Messenger to send files provides some advantages over sending files as e-mail attachments. Many e-mail client programs, including Microsoft Outlook®, make it impossible to send or receive files of certain types. This is a surefire way to prevent the spread of some viruses and worms, but it becomes a hassle when you and your correspondent know that you’re working with a safe file and would like a handy way to exchange it. Windows Messenger provides the handy way.

A caution, Windows Messenger doesn’t put up roadblocks to files the way Outlook does, but be aware of the extra risks and responsibility this incurs. With Messenger, you can send or receive a virus-infected file. It’s up to you to know the identity of the file sender, and more important, to scan each file you receive with a virus-scanning program. Even trustworthy and knowledgeable sources can inadvertently send you an infected file.

When you send a file as an e-mail attachment, the sender and the recipient both end up with two copies of the file: one that’s saved in a folder and one that’s saved with an e-mail message. By default, most e-mail programs save a copy of each message you send. The extra copy can be a problem, particularly if your messages are stored on a mail server, such as Hotmail or the one at your ISP that limits the amount of disk space you can use for stored messages. Windows Messenger copies a file directly from a folder on one computer to a folder on another computer without leaving extra copies lying about.

Some mail servers limit the size of attachments. Windows Messenger imposes no such limit. Note, you can’t send a file if a conversation includes more than one other person. Before you can send or receive files, you must be sure that your firewall or proxy server is configured properly. Windows Messenger uses Transmission Control Protocol (TCP) connections to ports 6891 through 6900; again, 6891 through 6900. Each port is used for transferring a single file. By opening all 10 ports, you can transfer up to 10 files concurrently.

To send a file, follow these steps. If you haven’t started a conversation, right-click the name of the contact you want to send to, and choose Send a file. If you already have a conversation window opened, click Send a file in the sidebar or choose File, Send a file in the menu. A standard File Open dialog box will appear. Navigate to the folder that contains the file you want to send, select the file, and click Open. Messenger displays an estimate of the file transfer time and, on the recipient’s computer, an invitation to accept the file. Lastly, the recipient must click the Accept link before the transfer is complete.

File transfer commences immediately and displays its progress in the status bar. Either the sender or the recipient can cancel the transfer at any time by clicking the Cancel link in the status bar. When the transfer is complete, Messenger displays a notification of the completion and a link to the file. The recipient can link the file so that it opens with its associated program.

By default, all files you receive are stored in %UserProfile%\My Documents\My Received Files. You can open the folder to work with your received files by choosing File, Open Received Files in any Windows Messenger window. If you want to change the location for received files, in the main Windows Messenger window, choose the Tools menu, then Options. Click the Preference tab, and then click Browse to navigate to the folder you want to use.

Whiteboard and application sharing (slide 9). Windows Messenger inherits two collaboration features that were previously available only in NetMeeting®. Whiteboard and application sharing. The whiteboard is an electronic equivalent of a whiteboard in a conference room. With it you can enter text and draw shapes as well as create freehand drawings. It also includes a feature that’s more akin to a conference room easel than a whiteboard: the ability to create multiple pages of drawings.

With application sharing, users in a meeting can view and control a program that’s running on one participant’s computer. With this capability, you can work together on a document or presentation for example. Note, you won’t find online help about either of these features by using the Help menu in Windows Messenger, nor in the Help and Support Center of Windows XP. It is available via a command prompt by typing the following command: hh conf.chm to display help on NetMeeting, the source of these two features.

To elaborate more on the whiteboard. It is a drawing program that functions superficially like Microsoft Paint except that it’s designed for sharing drawings, diagrams, screen shots, and other images with other Passport users. Anything you create in the Whiteboard window is visible to both the parties in the conversation, and either participant can modify the whiteboard contents at any time.

To run the whiteboard, use any of these methods. If you haven’t yet started a conversation, right-click the name of the contact you want to work with, and choose Invite, To Start Whiteboard. If you already have a conversation window open, click the Invite button and choose To Start Whiteboard. If the Sharing Session window is already open, click the Whiteboard button.

Application sharing. I'll elaborate more on that. Sharing programs allows meeting participants to view and work on files simultaneously. For example, you may have a Microsoft Word document that several people need to work on. You can open the document on your computer, share it, and then everyone can provide their comments directly in the document. Only the person who has opened the file is required to have the program on their computer. Other participants can work on the document without having the program. Only one person can be in control of a shared program at a time. If "controllable" appears on the title bar of the shared program window, the person who shared the program has control and is allowing others to work in the program. If the mouse pointer has a box with initials, then another meeting participant has control of the program. All meeting participants can share programs during a session. The shared programs of each participant appear in separate shared program windows on the other participants’ desktops.

Let's move along to Remote Assistance (slide 10). Remote Assistance allows you to team up with a friend for help. Sometimes the best way to fix a problem is to have someone show you how. The Remote Assistance feature in Windows XP is a convenient way to have a friend or computer expert walk you through a solution to your computer problem. After connecting to your computer, with your permission, the expert can view your screen or even take control of your computer by using his or her mouse and keyboard to work with you on your computer. Note, all sessions are encrypted and can be password protected. You can even chat online as you work through the problem.

The methods for sending the invitation via Windows Messenger. Users of the Windows Messenger service can invite a contact to help them by using Remote Assistance. Using Windows Messenger is the preferred method of sending a Remote Assistance invitation for the following reasons. Windows Messenger works in real time, which allows the novice to know if the expert is online. Windows Messenger provides additional ways for the novice and expert computers to find each other over the Internet. This is used when computers are not on the same network or are attempting to connect over the Internet through a firewall or a NAT machine.

When using Windows Messenger service, there is no need to open Help and Support Center. You can also send the invitation by opening Windows Messenger and then following these simple steps. On the Tools menu, click on the Send an Invitation option. Then click To Start Remote Assistance. Then lastly, click the desired contact for Remote Assistance. The selected contact receives a message requesting a Remote Assistance session and the expert can click Accept or Decline. A Remote Assistance session may also be initiated in Windows Messenger by right-clicking on a contact, clicking Invite and then clicking To Start Remote Assistance.

You might shudder at the thought of accessing another desktop over a dial-up connection. Surprisingly, the performance can be quite usable. You wouldn’t want to use this sort of connection for everyday work, but for troubleshooting it’s good enough.

You can maximize Remote Assistance performance over a dial-up link by observing these precautions. If possible, you want to try to connect at least 56 Kbps per second if possible. You want to also reduce the visual complexity of the novice machine as much as possible by reducing the display resolution to 800×600 and use only as many colors as are absolutely necessary. Remote Assistance automatically disables wallpaper and other nonessential graphics.

You may want to turn off desktop animations and other sophisticated visual effects and avoid opening windows that contain complex graphics, unless absolutely necessary. Close any unnecessary applications on the novice machine. Lastly, don’t move the mouse on the novice machine, if possible, when the expert is in control of the screen.

Moving along to the Hotmail and Microsoft .NET Alert Notifications (slide 11). Get Microsoft .NET Alerts as the ultimate way to stay in touch. You can choose to receive important information like stock alerts in our MSN Messenger, on your mobile device, or in your e-mail mailbox. .NET Alerts puts you in control. Choose the content you want to receive and tell us how you want to receive it with our easy setup process. All the alerts you have received in the last 24 hours will appear in your .NET Alerts tab, so you never have to worry about missing information.

It’s free. Setting up and configuring alerts. First step is to go the following Microsoft Web site. It’s http://alerts.microsoft.com/. What you’ll see is a "Welcome to Microsoft .NET Alerts Web page that will open. Second step is to sign in by using your Passport. Third step is to click Sign up for Microsoft® .NET Alerts. Fourth step is on the General Settings page, specify where you want your .NET Alerts to be delivered. Specify any of the following locations: your computer using Windows Messenger; your mobile device, such as a cell phone or PDA; and then thirdly your e-mail Inbox. The fifth step is to click Choose .NET Alerts Provider. Then six, click a name or logo to set up or to change alerts from that provider.

The providers to choose from are MSN Money, MSN Calendar, MSN Carpoint®, MSN Music, eBay, FYE (which is known as For Your Entertainment), uBid Online Auctions, and lastly McAfee.com. You then go to the provider that you choose and follow the instructions for setting up and changing .NET Alerts for that provider.

MSN Add-in (slide 12). Now you can get all the functionality of MSN Messenger. Again, you can get all the functionality of MSN Messenger inside Windows Messenger for Windows XP, beginning with Windows Messenger version 4.6. Many features are available only as an add-in instead of being included in Windows Messenger by default. For example, Hotmail access is integrated directly into Windows Messenger 4.5. However, to access your Hotmail Inbox from within Windows Messenger 4.6, you must first install the MSN Add-In for Windows Messenger.

The MSN Add-In for Windows Messenger includes the following features: e-mail integration, MSN Chat integration, MSN Profiles integration, MSN Mobile Paging integration, and lastly, MSN Headlines. You can install the MSN Add-In for Windows Messenger by using either of the following methods.

First method, if the MSN Add-In for Windows Messenger is not already installed on your computer, you are prompted to download it from the Add-In Web site, then you attempt to use a feature that is provided by MSN Add-In for Windows Messenger. Follow the instructions on the Add-In Web site to install the MSN Add-In for Windows Messenger.

The second method: in Windows Messenger 4.6, click Add-In Web site on the Tools menu. To download the add-in and to get more information, click on the Click here to learn more option, and then follow the instructions on how to install the MSN Add-In for Windows Messenger.

When you install the MSN Add-In for Windows Messenger, e-mail integration, MSN Chat, MSN Profiles, MSN Mobile Paging, and MSN Headlines are automatically enabled.

We’ll now move along to the other features (slide 13). Under the other features: we are allowed to invite friends to play a game, we provide emoticon drop-down lists, we arrange your contacts into groups, we change your display name, and we provide rich customization. To be more specific, let’s go through these again.

Invite friends to play a game. You can use Windows Messenger to invite your friends to play a DirectPlay® compatible game online. For example, you can have two or three or four or more buddies play Age of Empires II, by mainly just prompting them to invite them via the Windows Messenger.

Emoticon drop-down lists. You don’t have to remember the keystroke, just click the emoticon that you would like to send to a friend, such as a happy face, I’m sad face, or a heart shape, meaning that I love you.

For arranging your contacts into groups, get organized. Define your own groups for family members, friends, or the players from the soccer team.

You can change your display name. Switch your display name as often as you like. One minute you can be "john the triumphant", and the next you can be "john the recently humbled". Have fun. That’s what instant messaging is all about, to have fun.

Rich customization. Change the style, color, and size of your font. You can even apply the Windows color scheme to Windows Messenger. Designate special sounds that play when you receive an instant message or when a friend comes online. You can also designate Windows Messenger to appear in the foreground for constant access to its features.

On the new features and additions, here are some points to remember. Microsoft Windows Messenger for Windows XP provides the capabilities to host an Instant Message session from PC to phone, PC to PC with video and voice, able to send and receive messages and files, share applications to collaborate with others, receive Hotmail and Microsoft .NET alert notifications. Lastly, you can contact peers for help through the use of Remote Assistance.

That concludes our new features and we now are going to move along to troubleshooting common issues (slide 14). As you see here, we’re going to discuss some common issues that have been addressed by customers through our support channels. What we’re also going to provide are some possible solutions on how to resolve these issues. The main four that we’re going to talk about are firewalls and routers with or without Universal Plug and Play support, port configurations, virtual private network connections, and lastly, user account credentials.

Firewalls and routers. If you have a dial-up connection or a broadband connection and your computer connects directly to the cable without passing through a router, you’re probably using Internet Connection Firewall and Internet Connection Sharing to protect your network and share your Internet connection. If that is the case, you’re in great shape by using all of the features of Windows Messenger.

This combination deals perfectly with the dynamic port assignments and supports Universal Plug and Play, also known as UPnP. The computer is protected from the Internet by a router. Other than the built-in Internet Connection Sharing, the router must support Universal Plug and Play. You want to use Messenger features other than instant text messaging and file transfers.

On the other hand, if you use a router that was purchased before late 2001, it probably does not support UPnP and therefore won’t allow you to make voice calls and voice calls over the Internet. In addition, you might need to open some ports to enable certain other features. If you have such a setup, check with the manufacturer of your router. Many manufacturers have promised firmware upgrades that enable UPnP as well as incorporating the UPnP support in their new products.

One of the key jobs of a router is network address translation, also known as NAT, which converts the internal LAN address of a computer into a public IP address. NAT effectively shields your network computers from the Internet, but it also makes it difficult to connect computers on a separate private network in a peer-to-peer fashion.

UPnP is a new industry standard that makes it possible for computers to detect devices on a network and work with one another. When it comes to traversing NAT devices, UPnP enables applications such as Windows Messenger to navigate the gateway. You can find more information about UPnP at the following Web site http://www.microsoft.com/windowsxp/pro/techinfo/planning/networking/natfaq.asp. The other Web site is http://www.upnp.org/.

Let’s talk about port configurations. If you are using Internet Connection Sharing with or without Internet Connection Firewall, you don’t need to do any configuration, except as noted. For other firewalls, consult the devices’ documentation for information about opening ports.

Windows Messenger uses the following ports for the following:

• Instant Messaging. Windows Messenger uses a TCP connection to port 1863; again, that’s port 1863, if possible. If that port is not available, Messenger connects using the same connection the Web browser uses. If that’s the only available connection method, you will be limited to using Windows Messenger for Instant Messaging. If you’re using a proxy server, open the Tools menu in Windows Messenger and choose Options. Click the Connection tab and provide the requested information, which depends on the type of proxy server you have.
• Port configurations for file transfer. Windows Messenger allows up to 10 simultaneous file transfers, each on a separate port, using TCP connections to ports 6891 through 6900, again, 6891 through 6900. If you use Internet Connection Firewall, you need to add rules to open these ports.
• Port configurations for the whiteboard and application sharing. Like NetMeeting, Windows Messenger uses TCP connections to port 1503 for whiteboard and application sharing. Again, it uses port 1503 for whiteboard and application sharing.
• Then lastly for port configurations for voice and video. These services are dynamically assigned ports. If you’re curious, you can see the rules that Internet Connection Firewall uses by examining its settings while you have a voice or video conversation active. You’ll see a number of services with names that begin with "msmsgs." More important, they require UPnP support to get an IP address on the internal network.

Let’s talk about virtual private networking connections. You might encounter problems using Windows Messenger while you’re also using a virtual private network connection, also known as VPN. If you have a conversation open and then connect to a VPN server, your conversation might stop. You’ll receive no indication that the call has been interrupted other than the fact that the person that you’re talking with no longer responds to your messages. Similarly, the person at the other end of the conversation has no indication that you no longer are in the conversation.

The reason for this is that the default configuration of a VPN connection attempts to use the default gateway on the remote network, that is, the default gateway for the VPN Server for Internet connections while the VPN connection is active. This setup is useful in situations where you’re connecting to a corporate network and then using its ISP to connect to the Internet. If you have your own connection to the Internet, there is usually no reason to use such a setup.

Thereafter, you should be able to use Windows Messenger and any other applications to access the Internet, such as Internet Explorer, while your VPN connection is active.

To fix the problem, you can follow these steps: you can go to the Control Panel and open up the Network Connections option, right-click the VPN connection, and choose the Properties option. Click the Networking tab, select Internet Protocol (TCP/IP), and click Properties. In the Internet Protocols (TCP/IP) Properties dialog box, click Advanced. Then lastly, on the General tab of the Advanced TCP/IP Settings dialog box, clear the Use Default Gateway on Remote Network check box.

Lastly, user account privileges. When a user tries to run Windows Messenger, it may fail to start. In the Event Viewer, you may receive an Event ID 10010, which is pointing towards the service DCOM and is typically logged in the Event Viewer, which is going to reference the particular GUID of the Windows Messaging service.

Next, if the user tries to use anything that utilizes the Windows Messaging service, for example MSN or Hotmail Web sites, these Web sites may take forever to load and another Event ID 10010 is logged in the Event Viewer because the Windows Messenger service fails to start again.

This is caused by a user account not being an Administrator account to execute applications during the very first installation of Microsoft Windows XP Home or Professional Edition. In other words, these symptoms do not occur for user accounts specified as the Administrator account or for user accounts that had an Administrator account at one point in time and now it has been switched to a Limited account.

The resolution to this problem, which will allow Windows Messenger to run for all users, is to add a registry value. If you want to make the change in the registry, it’s strongly recommended that you back up your registry before making any changes in the registry. The resolution again is that you need to add the PrimaryService registry string value with the value data of .NET Messenger Service to the registry in the following location. Again that registry key is HKEY_CURRENT_USER\Software\Microsoft\MessengerService. Again, the particular value that you would add, the string value is known as PrimaryService (capitalization as shown) with the value data of .NET Messenger Service to the registry key mentioned above.

This leads us to some additional resources that we can look at for troubleshooting issues. Some of the resources that we use come from our very own Microsoft Knowledge Base articles (slide 15). These are some of the most common articles that will, in most cases, help you resolve your Windows Messaging issues dealing with connectivity, dealing with server issues, dealing with issues that we mentioned within the common issues, dealing with port configurations, dealing with firewalls and routers, dealing with virtual private networking. Then lastly, mentioning about the user account privileges.

Going down this list, the first article is Q307887, "HOW TO: Use Windows Messenger Instant Messaging." For general use of how to use the particular product, Windows Messenger for Windows XP.

Second article is Q307293, which is "'Server Not Responding' Error Message Appears When You Try to Sign In to Windows Messenger."

The next article is Q307294, which the title of it is "Common Solutions for Windows Messenger Account Logon Problems."

The next one is Q324214. The title of it is "You Cannot Make Phone Calls or Start Voice or Video Conversations with Windows Messenger."

The next one is Q306298, "Description of the Windows Messenger Reverse Connection Process Used by Remote Assistance" for those administrators who want to understand more intuitively how the Windows Messenger Reverse Connection process works.

The next article is Q306800, " HOW TO: Provide Remote Assistance in Response to Windows Messenger Invitation in Windows XP."

The next one is Q314353, "Description of the MSN Add-In for Windows Messenger."

Then the last article in our Microsoft Knowledge Base that is listed here, Q314381, "HOW TO: Receive Windows Messenger Messages and Alerts on Your Mobile Device."

We have some additional resources that talk more about Microsoft Windows Messenger for Windows XP on our next slide (16). The additional resources consist of two items. The first item is a book that you can read through that seems to have a lot of information about Windows XP. The title of it is Microsoft Windows XP Inside Out, particularly about Windows Messenger can be more found in chapter 23. The title of that chapter is, "Communicating Over the Internet." It is a Microsoft Press book and it was released in 2001.

The next particular resource, which is very helpful as well, is the Microsoft Windows Messenger Web site, to find out more information about Windows Messenger or if you have issues pertaining to the Messenger products for MSN. That Web site is http://messenger.msn.com/.

This pretty much leads to our conclusion (slide 17). In this presentation we talked about the system requirements, the new features, and combination use of Microsoft Windows Messenger for Windows XP. I hope that you have enjoyed the presentation today and at this present time I would like to turn it over to Otto for the Q&A session. Thank you.

Otto Cate: Great. Thank you very much for the presentation there. Definitely appreciate it. Before we move into the Q&A portion today of the Support WebCast, we just wanted to share a couple of program notes with everyone. If you’d like to have a copy of the PowerPoint® slides, be sure that you download the file from the Past Support WebCast page. To access all that information, including some details on upcoming Support WebCasts, an easy-to-remember URL is http://support.microsoft.com/webcasts/.

It looks like we’ve got a few questions here. Just a reminder for those of you who have joined us in the past, the Q&A portion of the Support WebCast is really intended to encourage further discussion of the topic that we’re addressing today. One-on-one product support issues are really outside the scope of what we’re able to address. So if you do happen to need some further technical assistance that requires some more one-on-one support, feel free to submit an incident on the Web or contact Product Support Services and speak to a Support Professional.

Okay. First question here, I know he addressed it during the presentation a little bit. Perhaps we can get some more clarification, I suppose. We’ve got a couple of customers who are curious about NAT configuration and that kind of thing. For instance a question here: Is there any way to get Messenger to work through a "double NAT" configuration? I can send and receive through my router when I’m on a dial-up connection from the outside, but not from another corporate site.

Juan: In most cases with "double NAT" configurations, this is pretty similar to (I guess you want to say in most cases), what applies toward configurations of a NAT configuration. In other words, in some cases you will have to open up certain ports for those particular configurations to occur. In other words, it has to be more transitive for the two NATs to allow it to be able to be on the receiving and sending end. If you’re looking for more specific information, I’ll be glad to answer that at a later time.

Otto: Okay. Another question surrounding this topic here: Did we mention which port is required for Remote Assistance?

Juan: No, we did not, but in most cases with Remote Assistance, it’s going to be based on the communication piece, pretty much with Instant Messaging. So in most cases it would be port 1863 for Remote Assistance as well.

Otto: Okay. Moving on to the next question here, we’ve got a couple of users who are curious: Is any public information available on plans for a unified version of the client that basically supports .NET and Exchange. Is there a reason that the Exchange IM and .NET Messenger are separate?

Juan: Well, I know that we didn’t mention too much about the Exchange client because this presentation of course was with the Windows Messaging for XP. But to answer the question, at this moment in time, there is really not too much public information towards a unified version of the Windows Messenger. The main thing I could suggest is to check our product Web site at http://www.microsoft.com/ and you can query on "Instant Messaging for Exchange" for any further information for that. As far as the Windows Messenger for XP, you can always go the http://messenger.msn.com/ Web site for more information. So that is the ideal thing; I think we are trying to see if we can collaborate, but at this moment in time there isn’t any confirmed information in doing so.

Otto: Okay. Is there a certain type of configuration you would recommend that could be run within a corporation’s firewall, not using the Internet? I’m not exactly sure what they’re referencing here. Does that make sense to you?

Juan: Somewhat, but they need to elaborate on their question as far as what they’re asking.

Otto: Okay. We have many work-at-home people and we’re curious about PC-to-phone and other tools. I know that you had mentioned some stuff about the inability to connect outside firewalls and that kind of thing. Do you have any recommendation about how you could easily set up that scenario to work through home routers and such?

Juan: Well with a PC-to-phone, first of all, make sure that you do sign up with a phone provider. That’s the first thing. The second recommendation would be, of course, in most cases with your specific manufacturer’s router, make sure that you have the most updated firmware with that router. Most particular manufacturers have been very cooperative to make sure that they have the most updated firmware so that it works with Windows XP as well as most of all, the Windows Messenger client.

In addition to that, you want to just make sure that for specific ports as far as Instant Messaging, again, make sure that 1863 is available for file transfers. You want to make sure that ports 6891 through 6900 are available and pretty much for voice and video again, you want to make sure that the router and its firmware is Universal Plug and Play supported so that you can get the IP address on your specific network.

Otto: Okay. We have another question concerning PC-to-phone here: We’re curious if when you sign up with one of these services if you’re able to call — for instance, if I’m just using DSL on my computer, can I call a regular phone using this technology or does it have to be another person that’s basically signed up with one of these services and that kind of thing?

Juan: No. The key goal or the key feature of using this particular function is so that you could make a phone call through that provider, as if you are on an additional phone line. For example, if I click to make a phone call to someone, say across the world, if that provider provides me the long distance service per se, I can actually make a phone call regardless of a dial-up connection or DSL or cable connection through Windows Messenger, so that I can actually make a phone call through this provider. So it’s not necessarily hardware dependent as far as whether it’s dial-up, DSL, or cable. The key thing is that the service provider that you sign up with gives you the capability so that you can make the phone call complete.

Otto: Okay. So I wouldn’t necessarily need to insert a phone line as if I were on a dial-up or I could basically just utilize that service and it would transfer the voice information?

Juan: That’s correct.

Otto: Okay. All right, next question here: We’ve experienced issues where the whiteboard would not show as an option on the XP Messenger client. It appears, though, that this user is using Exchange 2000 with an XP-to-XP connection. I’m not sure if they’re using Exchange IM or Messenger .NET Messenger here. Is this something that you’ve seen before, though?

Juan: I haven’t seen that particular issue personally. I’ve heard, in most cases, it may be more so if the clients are different. Again, most of these particular features are designed for the Messenger client with Windows XP. So if it’s a different client, some of the features, or particularly the whiteboard, may not appear. I’m pretty sure it’s something in that line.

Otto: Okay. Kind of along the same lines here, concerning voice conversation with video: Is it only possible in an XP to XP scenario or can I go XP to (Windows) 98, that kind of thing?

Juan: With voice, generally it’s XP to XP. Because the particular client is designed for XP and most of these features are Windows Messenger for XP compliant.

Otto: Okay. A question about the text conversation: When I’m communicating direct client to client, does it happen to go through any servers or is it basically just a direct connection between the two computers almost?

Juan: In most cases, it’s going authentication and verification through the Passport. So as long as you have the .NET Passport through its Passport servers, that’s how it’s allowing you to communicate from person to person.

Otto: Okay. If I have a mail address like blah@hotmail.com and my friends, they do have Messenger installed but they don’t have an account on Hotmail. Their current e-mail address is basically a different provider, someone@example.com for instance. Can we still talk and send files to each other directly between the two computers, and would it be required for the other user to simply link their address (example.com address) to a Passport account in order to do that?

Juan: Yes. With the Passport service, we allow you to link a Passport to any e-mail address. So it doesn’t have to be a hotmail.com or msn.com or passport.com e-mail address. Again, everything is configured through having a .NET Passport. So as long as within the account wizard, you have your specific e-mail address linked to a valid .NET Passport account, you should be able to transfer files and send Instant Messages between two different users with two different e-mail addresses that are not specifically using Hotmail or MSN or Passport.com.

Otto: Okay, excellent. Thanks for that clarification. Okay, next question here: Do you know if there is any public information on plans to include automatic virus scanning within Messenger?

Juan: Not at this time. Most of that information, if there is any, you can always check to see if there is updated information about such features. I mean, that’s a great idea, but I would check in the near future for any new features about the Messenger product for Windows XP at http://messenger.msn.com/.

Otto: Okay. Do we happen to have an article or some kind of reference that covers a listing of all the ports that are used by Messenger?

Juan: I don’t have an article, but I can give you the specific ports that we mentioned earlier in the presentation today that apply to Windows Messenger. Again, for Instant Messaging, Windows Messenger users TCP connection port 1863. For file transfers we use 10 simultaneous file transfer ports. The TCP connections are for ports 6891 through 6900. For whiteboard and application sharing, it’s very similar to how we used it in NetMeeting and it uses TCP port 1503. For voice and video, more importantly the ports are, particularly if you’re using Internet Connection Firewall, it uses ports that are generally dynamic, msmsgs.<whatever particular port and IP are assigned to it>.

Otto: Okay, great. Perhaps later on we can get that, you had mentioned there is an article that also covers a lot of this information. Yes, we can go ahead and add that to the supplemental reading section.

Juan: I was going to say, in addition, something to take a look at for additional resources are some of the particular KB articles, as well as the additional resources for supplemental reading, the Microsoft Windows XP Inside Out book may also provide that port configuration information.

Otto: Okay, great. Next question here: Early on you had mentioned a command-line command basically for online help, using application sharing in Messenger. Could you repeat that for us?

Juan: Sure. That particular command line, which you would have to type at a command prompt, is hh conf.chm (including the space). What that will do is display the help for NetMeeting that whiteboard and application sharing derive from.

Otto: Okay. The next question here as follows: What kind of integration is available as far as Messenger and NetMeeting is concerned?

Juan: Can you repeat that question again? I just want to make I understand it.

Otto: Sure. Although they’re two completely separate applications, we’re curious if there is any type of integration between Messenger and NetMeeting, or is Messenger more along the lines of a replacement, in a way to NetMeeting?

Juan: To answer that question, the main components that we were "taken" from NetMeeting or the ideas to include it in the Windows Messenger for Window XP is the application sharing and whiteboard. That would be the most integration, I would say, between the two products.

As far as Windows Messenger separately, I mean, it has the potential to pretty much be the collaboration tool that most home and business users need for future developments for communicating among their peers or family and so forth.

Otto: Okay. We’ve got a follow-up to one of the previous questions that basically concerns .NET Passport linking to e-mail addresses other than Hotmail.com and Passport.com, etc. We’re curious if this is the same for non-public addresses, basically like a fake e-mail address almost. Would that work or does it have to be a public e-mail address that is verifiable?

Juan: I would say if the particular e-mail address, say for example, it’s going to require a valid e-mail address in more cases than in others to acknowledge back a user. In other words, you can have as many Passport accounts as possible to different aliases, but as long as it recognizes it as being a valid one, generally it should work.

Otto: Okay, excellent. Next question here: Do you know if there is any public information on plans to have all P-to-P connectivity features, basically to have them all be Universal Plug and Play enabled, especially like file transfers? Is that something that you’re able to address at all?

Juan: Not at this time.

Otto: Okay. We’re curious what the reasoning behind it is for using dynamic ports for video instead of static ports, which would make firewall configurations a lot easier, instead of having to specify a range and such.

Juan: I don’t have a firm answer for that, but I would think that the reason behind it is probably be for security reasons. Say if you weren’t behind a firewall or a NAT router, I mean that still could lead to a possible or a potential security risk. So I think, in most cases, they changed it so that it stays dynamic, because in most cases you sign on, you sign off, and you don’t always have the same IP address per se, but it is a great idea. I’d be glad to forward it.

Otto: Okay. Next question here: Does Messenger still use ILS Servers as NetMeeting did?

Juan: As far as my understanding, Messenger uses their Passport service. So the use of ils.ils1.microsoft.com or ils.mycomputercompany.com doesn’t get used in Windows Messenger. Again, we rely on the .NET Passport to converse between the users that you have in your particular group that are online or offline in your group list.

Otto: Okay. I know that the range of this discussion is pretty much centered on MSN Messenger for XP and .NET Passport integration and such. We have a few users that have some questions about Exchange IM. Is there a resource we could possibly point these users to for support on Exchange IM?

Juan: I can follow up with them on that. Right offhand I don’t know the Web site off the top of my head, but there is a resource out there available; I just have to follow up.

Follow-up answer: The Exchange 2000 Instant Messaging Service Web site is available at http://www.microsoft.com/exchange/downloads/2000/imclient.asp.

Otto: Okay. In XP Messenger, we noticed that the "Start NetMeeting" feature has been removed in later versions here. Do you know what the overall reasoning for that is? Is it basically just to minimize confusion?

Juan: I believe it is to minimize the confusion in most cases, because they kind of do the same functions, except that in Windows Messenger we utilize Passport technology, and we integrate some of the MSN features of the product. Compared to NetMeeting, of course, we provide still the video and audio and the whiteboards and so forth. So to alleviate the confusion, I believe we just took it out, so that users don’t try to use two products that are very similar to each other, unless they choose to use it.

Otto: Okay. Do you know if there is any way to include a custom port configuration?

Juan: Could they elaborate on that?

Otto: Yes. If that user would like to go ahead and send some follow-up on that, that would be helpful. I just want to take a real quick break here to solicit some feedback from our audience. If anybody happens to have some suggestions for future topics or some general comments about this WebCast, or even the whole WebCast program as whole, we’d definitely love to hear from you. We absolutely value your feedback. You can e-mail us 24 hours a day at the alias, supweb@microsoft.com to send us some feedback at any time.

Okay. Can you give us an idea of what the security or privacy of information is, what the level of it is that’s sent across the public Internet when using Messenger?

Juan: Well, most of the private information, again, is all based on the Passport servers. In other words, it’s one-to-one unless you invite another person into the conversation that is online. So a lot of the privacy issues are handled from our back end on the Passport servers. Unfortunately, that’s pretty much all the information that I have for us today on that particular topic.

Otto: Okay. Is Windows XP, being used as a gateway to the Internet, capable of supporting all the features of MSN Messenger 4.7? I’m not exactly sure what they’re referencing there, but I wanted to throw it out just in case, if that made sense to you.

Juan: I mean, the only versions that we are currently supporting, as far as actual releases, is version 4.6 that is downloadable from the http://messenger.msn.com/. So any references of 4.7, if there is a 4.7, I wouldn’t know about it.

Otto: Okay. Do you know if there are any automatic settings or easy straightforward settings you can use to get some of the advanced features like "file sending" and such configured through ICS? Is there an article or something that we could point to?

Juan: Well, a lot of the information pertaining to ICS can be utilized through the Help and Support Center. Another area that we can look at as far as more information that can be utilized is within the Windows Messenger Help file as well. I guess a third reference, of course, you could utilize, if you have access to or if you have a chance to browse through it, would be the Windows Inside Out book (Microsoft Windows XP Inside Out) that’s mentioned on slides 16, as an additional reference.

Otto: Okay. We’re curious about multiparty audio and video in Messenger. Do you know if there is any public information on plans to set up an MCU (Multipoint Control Unit) server or something of that nature?

Juan: Not that I know of, to be perfectly honest with you. I mean, as of right now, video and voice is pretty much person to person.

Otto: Okay. Do you know if an admin of a network could set restrictions on Messenger? Are there any policies or anything like that that can be set?

Juan: I’m pretty sure there are some policies that you probably can set for Windows Messenger. The main information, as far as restrictions, would rely more on the type of connection you have. I know that we mentioned before about the network connections dealing with routers and firewalls. So for example, I know you can restrict certain ports from being used by others, and I’m pretty sure within resource kits, as well as our Microsoft Knowledge Base, there are ways in which you can restrict different users from accessing the Windows Messenger or for configuring the functions of Microsoft Windows Messenger.

Otto: Okay, great. Next question here: As far as a home LAN is concerned, basically a small home LAN network, what settings would you use overall? Evidently it’s not necessarily using the Internet, simply communicating between each user on the LAN. Is that something that Messenger is capable of handling or does it require an Internet connection through the Passport server?

Juan: You generally need an Internet connection. Without an Internet connection, granted, you will not be able to utilize Windows Messenger to sign on to the Passport server.

Otto: Okay, thanks for that clarification. Next question: Do we have any kind of reference, as far as routers that work with UPnP that have been tested etc.? I know you did mention earlier that it generally looked for routers that are later than 2001 and that some older ones can be updated with firmware upgrade, but do we have some kind of a list, possibly in a KB article, that could give us a little more information about this, or is just best to simply contact the various vendors?

Juan: It would probably be best to contact the various vendors to see if their particular routers or product or their firmware is UPnP compliant. I know that earlier I mentioned, under the "troubleshooting common issues" topic, a particular Web site that talks about finding more information about UPnP.

The second Web site that I would like to mention is http://www.upnp.org/. A lot of vendors are making sure that their routers or particular products are UPnP compliant, and in most cases they may have a preferable list of vendors up there that are trying to be as compliant as possible to the UPnP standards that are listed on this Web site. So that would probably be my best recommendation: One, to contact the individual vendor; and two, to go to this particular Web site for more information about UPnP.

Otto: Okay. Next question here: I currently maintain a block list for people that are basically adding me without asking. The block feature works great and I’m curious how I can actually delete them from my list completely.

Juan: If possible, can we table that particular question? I would love to follow up on that.

Follow-up answer: You can refer to the Microsoft Knowledge Base article Q313976, "Can Still See Blocked Contact Who Signs On and Off in Messenger 4.6."

Otto: Okay. Do you have any tips or tricks concerning making the video window larger or possibly just increasing the overall quality of the video in Messenger here?

Juan: Well, as far as the quality, quality is going to be based on the type of camera you have as well as the connection speed that you have. In most cases, we know that FireWire cameras usually provide a faster frame per second quality, as well as some of your newer USB cameras. But in most cases there is a video and audio wizard that you can use to try to adjust the particular setting for that separately within the Windows XP product, or the adjustments of trying to enhance the quality or making it better. As far as the screen size, unfortunately I don’t believe there is a way to increase the screen size as how we used to have it within NetMeeting.

Otto: Okay. Next question here. Apparently a couple of users have had problems with Messenger when the user name has "Web cam" in it or next to their name. Is that something that you have seen before? Is that a known issue?

Juan: I haven’t seen it before, to be perfectly honest with you. So I wouldn’t be able to give you a firm answer to your question unfortunately.

Otto: Okay. Perhaps that user, it would probably be a good idea to follow up with PSS, perhaps open an incident or something of that nature, and find out if there is some kind of workaround for that scenario.

Okay. A couple more questions here: Do I understand correctly that "voice and video" is the only piece of Messenger that utilized UPnP dynamic port functions, and that everything else must be mapped statically? Is that accurate?

Juan: Well, the UPnP support in most cases, again, deals more with the firewalls and routers. As far as the voice and video, you are correct; they are dynamically assigned ports. Whereas the other functionalities of the products, they use a specific port designated to them. So for example, the Instant Messaging again is port 1863. The File Transfer function uses ports 6891 through 6900. The whiteboard and application sharing uses port 1503. Again, the voice and video, these services use dynamically assigned ports.

Otto: All right, next question here: Currently is there any feature that can actually show whether another user has a Web cam or not, so video would be available in that case?

Juan: At this moment in time there isn’t. I would suggest that preferably as a great feature for a future version of the Window Messenger. But at this current time, there isn’t a way of doing so. So I would definitely suggest that as a new feature for future versions of this product.

Otto: Okay. Does the http://messenger.microsoft.com/ Web site have some kind of a contact or e-mail address or something like that that users can submit wishes to, or would it be better to utilize, say, the mswish@microsoft.com alias for instance?

Juan: You can use the mswish@microsoft.com and just by checking their particular Web site, there is some information under the Help for that http://messenger.microsoft.com/ Web site that they can easily point to.

Otto: Okay, excellent. Next question here: Do you know if there is any available workaround to utilize static ports versus dynamic ports, or is it pretty much set in stone?

Juan: At this moment in time, from my understanding, it’s pretty set in stone. Again, the dynamic ports are only in use of when you’re using voice and video. The other specific static ports are used when you want to use just straight Instant Messaging to perform a file transfer or if you want to utilize the whiteboard in the process of application sharing.

Otto: Okay. We may have touched base on this a little earlier. A couple of the users are just asking for some further clarification. Do messages and other communications, like voice and video, go directly peer-to-peer or does it go peer-to-server-to-peer?

Juan: Everything’s being transferred through a Passport server, the same as your identification and authentication for you to actually communicate to a user in your online list. So again, everything’s being negotiated and sent through a portal through the Passport server to your user. But to the users is virtually looks as if it’s peer-to-peer, but in actuality it’s your user being authenticated through a Passport server to also be able to authenticate the user you’re communicating with.

Otto: Okay, excellent. We’re also kind of curious if there is currently any support for third-party IM service connectivity awareness like ICQ or Yahoo, etc.? We know it’s capable of messaging to those providers, but we can’t really detect at this point, unless there is some kind of workaround, whether those contacts are online. Is that probably another feature request?

Juan: That would be more so a feature request, because the ideal thing is that you want to communicate with as many people as possible that don’t utilize, say, the MSN Messenger service or the Windows Messenger service, say with AOL Messenger or ICQ or what have you. So again, that would be more a feature request that we can possibly look into for future product releases.

Otto: Okay, excellent. We have some follow-up information to one of the previous questions concerning video quality. This user evidently is using a FireWire camera and a cable modem and is curious what the optimal speed for both the up and down transfer rate would be for high-quality video. Evidently they’re saying that the video codec that’s used for NetMeeting occasionally performs better. Is this something you’re able to address?

Juan: Not at this time. I wouldn’t know the actual values at this moment in time.

Otto: Is this something that we might be able to obtain?

Juan: That information is going to vary from camera to camera; the functionality varies if it provides a higher frame-per-second variation. So it’s going to definitely differ from camera to camera, so I don’t think there is actually a benchmark, per se.

Otto: A golden rule.

Juan: Right.

Otto: Okay. A couple of users just want to clarify where they can send feature requests. It appears that under the Help section there is some information on http://messenger.microsoft.com/ and as an alternative, you can also e-mail your product feature request, etc., to mswish@microsoft.com.

Juan: That’s correct.

Otto: Okay, wonderful. Well, it appears that we’ve addressed all of the questions that came in. I wanted to definitely Juan for coming out and giving us a great presentation and giving us some excellent information. I definitely wanted to thank you, the audience, for joining us, and hope that everyone has the opportunity to tune in again the near future. I hope that this information was useful to you.

Thanks, everyone, and have a great day.

Juan: Thank you, Otto, and thanks to the audience.