MORE INFORMATION
This issue occurs if the contact has a Session Initiation Protocol (SIP) Uniform Resource Identifier (URI) that is different from the contact's e-mail address.
For example, this issue occurs if the contact has a SIP URI of sip:
userName@contoso.com and a primary e-mail address of
userName@domain.contoso.com.
The following information describes how Outlook 2003 and Windows SharePoint Services look up presence information for Windows Messenger contacts.
Outlook 2003
Outlook 2003 uses the
proxyAddresses attribute in the Active Directory directory service to resolve SIP addresses.
Note The information in the
proxyAddresses attribute appears on the
E-mail Addresses tab of the
Username Properties dialog box for that user.
If the user is mail-enabled or mailbox-enabled before you enable the user for Live Communications, the code that handles Live Communications Server 2003 provisioning automatically adds a SIP address to that user's
proxyAddresses attribute. In this scenario, the new SIP address appears on the
E-mail Addresses tab of the
Username Properties dialog box for that user.
Consider the following scenario:
- You have a user (User1) who has an e-mail address of user1@domain.contoso.com.
- User1 has a SIP URI of sip:user1@contoso.com.
- You configure Outlook to display Messenger status for your contacts. To configure this option, follow these steps:
- Start Microsoft Outlook.
- On the Tools menu, click Options.
- Click the Other tab, and then click to select the Display Messenger Status in the From field check box.
- User1 sends you an e-mail message.
In this scenario, the
From field of the e-mail message shows an e-mail address of User1@domain.contoso.com. This address is different from User1's SIP URI of user1@contoso.com. However, Outlook uses the User1's
proxyAddresses attribute to resolve User1's presence information. In effect, Outlook requests the SIP URI of the user who has User1@domain.contoso.com as one of that user's proxy addresses. When Outlook receives this information, Outlook requests the presence information for User1 and then updates the display in Outlook.
Windows SharePoint Services
Windows SharePoint Services can look up presence information for a contact only by using that contact's SIP URI. Therefore, if you receive an e-mail message from a contact who has an e-mail address that is different from their SIP URI, and if you try to use a Windows SharePoint Services Web part to view the presence information of that contact, you are unsuccessful.
Live Communications Server 2003 provisioning
If you enable a user for Live Communications Server 2003 before the user is mail-enabled or mailbox-enabled, the Live Communications Server 2003 provisioning code does not add a SIP URI to that user's list of e-mail addresses. This behavior occurs because the user's
proxyAddresses attribute has not been enabled. Therefore, if the user has an e-mail address that differs from their SIP URI, you cannot view the presence information of that user.
To resolve this issue, follow these steps:
- Deprovision the user for Live Communications Server 2003.
- Mail-enable or mailbox-enable the user if this has not already been performed.
- Enable the user for Live Communications Server 2003.
How to confiqure status information queries
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
A registry value is available to configure how Outlook queries for a contact's presence information. You can configure this registry value to determine how Outlook retrieves the online status for contacts who are not on your Windows Messenger contact list.
To modify this behavior, change the QueryServiceForStatus value in the following registry subkey:
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common\PersonaMenu
To do this, follow these steps:
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry subkey:
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Common\PersonaMenu
- Right-click Common, point to New, and then click Key.
- In the New Key # 1 box, type PersonaMenu, and then press ENTER.
- Right-click PersonaMenu, point to New, and then click DWORD Value.
- In the New Value # 1 box, type QueryServiceForStatus, and then press ENTER.
- Right-click QueryServiceForStatus, and then click Modify.
- In the Value data box, type one of the following values:
- 0
If you type a value of zero, you receive status information only about people who are on your contact list. In this scenario, Outlook does not request status information about people who are not on your contact list. - 1
If you type a value of one, Outlook requests status information from the Microsoft Exchange Instant Messaging (IM) service about people who may or may not be on your contact list. - 2
If you type a value of two, Outlook requests status information from the Real-Time Communications (RTC) service about people who may or may not be on your contact list.
- Click OK, and then quit Registry Editor.
Note You cannot configure this registry value to cause Outlook to request status information from the Exchange Instant Messaging service and the Real-Time Communications IM service at the same time. Additionally, the .NET Messenger Service together with a Microsoft .NET Passport account does not allow status information queries for people who are not on your "buddy" list.
To view the status information of a contact who is added to a Web part in a Windows SharePoint Services-based Web site, both the following conditions must be true:
- You must have the QueryServiceForStatus registry value configured.
- The contact's SIP URI must be the same as their Simple Mail Transfer Protocol (SMTP) e-mail address.