@stefanb2, yes the plugin still works fine on our various Unix/Linux systems.
2012-05-27 06:45:04 PDT by psfales
@psfales: as far as I remember you use pidgin-sipe also on UNIX/Linux systems. Does the TCP connection work with pidgin-sipe 1.13.1 on those systems in your OCS2005 environment? Just to make sure that the TCP transport code path isn't broken completely...
2012-05-27 00:09:44 PDT by stefanb2
File transer is supported. I would see the complete log to see what pidgin-sipe considers as "Not implemented".
2012-05-24 11:05:03 PDT by stefanb2
@psfales: then I can only assume that this is some Windows thing, maybe related to the fact the binaries are cross-compiled. I can only suggest to compile 1.13.1 on Windows yourself and try again.
2012-05-24 11:03:35 PDT by stefanb2
Hi, I'm using the latest Pidgin-sipe plugin, and while I can send files from Pidgin to Lync, transfers from Lync Client to Pidgin fail. The error on the client is: Cannot send file to <user>. SIP logs show Pidgin sending SIP/2.0 501 Not Implemented. Is this supported? What should I do to make it work? Thanks. Thanks.
2012-05-24 10:03:19 PDT by rjtd
Nevermind on that last message guys. I had a plugin called AutoTranslate installed (we have some employees in Mexico) and that was causing problems with Communicator. Just removed that plugin and I am golden now. Thanks again for all of the help!
2012-05-24 08:26:34 PDT by unforgivnn
OY! Okay, I guess I'm not quite done yet........I can see my entire contact list. When somebody sends me a message I get notified. I can send a message to other people........but I CANNOT see the messages they send to me. Go figure! My Pidgin window only shows my messages to them. I can even seen when they are typing. But their message never appears. Looking in the debug window (in debug mode)
2012-05-24 08:21:04 PDT by unforgivnn
@psfales: Thank you VERY much. Both for the DLL and for the tips in general. That absolutely worked for me. Found oconv.dll and libxml2.dll and got those added and boom! Communicator works through Pidgin like a charm now. @stefanb2: I had planned to try out Wireshark next week. We have customers in the office all week this week so I haven't had much time for experimenting. Looks like psfales...
2012-05-24 07:59:47 PDT by unforgivnn
@stefanb2: Wireshark shows an initial handshake: client sends SYN server sends ACK, SYN client sends ACK then 10 to 30 seconds later, the server times out and sends RST. However, the "write error" message is printed immediately on attempting the connection (i.e. it does not wait for the timeout)
2012-05-24 07:14:18 PDT by psfales
@stefanb2: yes, we are also using TCP.
2012-05-24 06:36:52 PDT by psfales