I've been testing a few things with public IM connectivity to Windows Live, and I've managed to get a conversation going between two users, but not without some problems. It appears that if I add my Live account in Communicator, I can send an IM to it and have it pop up in Messenger. I can then add my OCS account to the Messenger contact list in the conversation. The issue seems to be adding contacts the other way-if I add my OCS account (e.g. user@ocsdomain.com) in MSN, the address shows up as offline and only lets me send email. Some other things I tried:
-Add user@ocsdomain.com as a contact in both MSN, and user@live.com as a contact in OC. In MSN, OC user shows as offline. IM MSN user from OC, and the conversation appears, but with an offline user. There is no option to add a contact. -Delete user@ocsdomain.com from the MSN contacts list, but leave the OC contact. Start an IM session from OC-this time in the conversation window you have the option to add a contact for the OCS user.
In the second case, the contact for the OCS user that I created based on the IM session looked exactly the same as the one I created manually (just the IM address filled in), so I have to ask-what's different in this case? Is there no way for an MSN user to add an OCS user to their contact list, or does the request have to initiate from OCS and go out to MSN?
Either user should be able to add the other's SIP address and contact them initially. From your description I'd guess that you've only recently (within last 30 days) requested PIC access and although you have OCS configured (why SIP traffic reaches MSN) Microsoft may not have yet fully completed your request and the MSN/Live environment is no configured with your OCS Access Edge server details. This would explain MSN users not being able to initiate a connection as your SIP domain is not yet know to that system.Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
Since Yahoo, AIM, and MSN are compeltely different systems there is no way to know which systems will configure your specific request, so it's pretty normal to see communications start to work for one provider and not yet with others. That is way Microsoft states that it may take up to 30 days for all providers to complete the requests.Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
Either user should be able to add the other's SIP address and contact them initially. From your description I'd guess that you've only recently (within last 30 days) requested PIC access and although you have OCS configured (why SIP traffic reaches MSN) Microsoft may not have yet fully completed your request and the MSN/Live environment is no configured with your OCS Access Edge server details. This would explain MSN users not being able to initiate a connection as your SIP domain is not yet know to that system.Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
Thanks Jeff-that makes sense. It was pretty recently (maybe a week and a half ago) that we got provisioned for PIC, so that might explain what's going on. Is there any way to track what has and hasn't been provisioned?
What's strange is that adding contacts on our domain in Yahoo messenger worked-I was able to generate an invitation to an OCS address via the yahoo client. I'll keep an eye on things on MSN though and see whether it starts working.
Since Yahoo, AIM, and MSN are compeltely different systems there is no way to know which systems will configure your specific request, so it's pretty normal to see communications start to work for one provider and not yet with others. That is way Microsoft states that it may take up to 30 days for all providers to complete the requests.Jeff Schertz, PointBridge | MVP | MCITP: Enterprise Messaging | MCTS: OCS
