#453 closed defect (duplicate)

Unnecessary error messages with Microsoft Office Communications Server contacts

Reported by: spil.oss@… Owned by: wilmer
Priority: normal Milestone:
Component: MSN Version: 1.2.2
Keywords: Office Communication Server Error Cc:
IRC client+version: Client-independent Operating System: FreeBSD
OS version/distro: FreeBSD 7.0-RELEASE-p3

Description (last modified by dx)

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 (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

Attachments (0)

Change History (4)

comment:1 Changed at 2008-11-04T23:14:50Z by wilmer

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

comment:2 Changed at 2008-11-07T11:11:23Z by 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).

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) and The 207 seems to be my login, the 64 seems to be the chat.

comment:3 Changed at 2014-02-04T07:24:43Z by dx

Description: modified (diff)

Formatting fixes to the description

No idea if this bug is still relevant.

comment:4 Changed at 2015-03-16T03:09:17Z by dx

Resolution: duplicate
Status: newclosed

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

Modify Ticket

as closed The owner will remain wilmer.
The resolution will be deleted.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.