Unnecessary error messages with Microsoft Office Communications Server contacts

[spil.oss@…]

When chatting with a user on a Microsoft Office Communications Server you get messages

[&bitlbee] /msg -bitlbee MeAtCorp Test OCS at work
[15:07] <@       root> | msn - The MSN servers could not deliver one of your messages to firstname.lastname@corporation.com.

 firstname.lastname@corporation.com (bitlbee)
[15:08]            --- | Query: Starting query with MeAtCorp on bitlbee
[15:08] <     Barnerd> | Test OCS at work
[15:08]            --- | MeAtPhilips is away: User is offline
[15:13] < MeAtCorp> | I'm here!

The "could not deliver one of your messages" usually happens for every line you send

[wilmer]

But otherwise things actually arrive? What's this Communications Server thing? I thought MS' Intranet IM system was SIP-based?

[spil.oss@…]

The messages are just a nuisance, I haven't had any issues with chat-sessions. It would thus be beautyfying the service to work correctly with

Dunno if OCS (Office Communications Server) uses SIP. It has it's own client (Office Communicator 2007) and I believe that you can integrate it into your VoIP infra as well. I do already use the client to for Audio (Video forbidden :x). ​http://www.microsoft.com/communicationsserver/en/us/default.aspx

What happened was that all personnel that was using their user@… email address on Windows Live was notified that these accounts would be (deleted|migrated) from Windows Live. We are now using the user@… internally using OCS and it's possible to connect to external Messenger users (potentially to other OCS instances as well, I'll try and test that)

Unfortunately, our setup uses ssl only. I do 'own' some of mycorp's ssl keys, but definately not this one so I can't really check what protocol is used. I guess that our OCS acts as the gateway to MS' Messenger service.

My bitlbee connects to 2 ip-addresses that are in MSFT owned range when I have a session open (irssi -> bitlbee -> MS Messenger Service -> mycorp OCS -> Office Communicator client) 207.46.111.91:1863 and 64.4.36.19:1863. The 207 seems to be my login, the 64 seems to be the chat.

[dx]

Formatting fixes to the description

No idea if this bug is still relevant.

[dx]

Replacing this one with the newer #943, which is more relevant for MSNP18 and might even be fixed in MSNP21