Microsoft Office Communicator Portable
.How to report SIPE problems Where do I report bugs?Link to the What information do I need to include?You MUST provide a debug log from Pidgin/Adium. Without the debug log nobody will be able to help you and the developers will most likely ignore your post on the Help forum.You need to provide an extended debug log, not the default output or the contents of the debug window.Client - -Pidgin You MUST start Pidgin with the -debug option from the command line Please make sure that you have disabled all other accounts in Pidgin when taking the log fileAdium Miranda ???Please do not cut anything from the start or end of the log. You may replace your name, addresses and domain names in the log.
Please make sure that you don't reveal any of your passwords in the log.Please attach the log to the bug report. If you are posting to the help form then please don't include the log in your posting, but instead put it up on a pastebin-like page and provide an URL to that page. If you don't feel comfortable to post the log in public, then email it to the developers directly. SIPE crashes.
What information do I need to include?Please make sure that the debug information for pidgin, pidgin-sipe (if you didn't compile it yourself) and glib2 are installed on your system.You'll need the debug log (see above) and the backtrace from a debugger. Run Pidgin under gdb control, reproduce the crash and then enter bt at the gdb prompt. The backtrace information will be more usable if you can recompile SIPE without optimization, i.e. With -g -O0 After upgrading to SIPE X.Y.Z. After upgrading to SIPE 1.17.1 Most of my IM message cause an ' Undelivered message' errorPlease update to SIPE 1.17.2 or newer.
After upgrading to SIPE 1.15.1 (or newer) Pidgin fails with ' The specified member name is either invalid or empty'Your account was updated to an account and the value you have entered into the Login field in the Basic tab of the account setting is no longer valid. Please clear the Login field. After upgrading to SIPE 1.15.0 (or newer) Pidgin fails with ' Failed to authenticate to server'Please make sure to check the setting of the flag in the Advanced tab of the account settings.
If your environment does not support SSO then you must disable SSO, otherwise SIPE will the ignore Login and Password settings. Older versions of SIPE enabled this flag by default for new accounts. After upgrading to SIPE 1.14.1 (or newer) Empathy can no longer connect, although the same account still works fine with Pidgintelepathy-haze can no longer or does not provide the password for accounts without selected. As SIPE requires a password the connection setup gets 'stuck' until it times out.
See also.A possible work-around might be to manually add a password entry for the sipe account in the GNOME password manager (seahorse). After upgrading to SIPE 1.14.0 Pidgin no longer asks for a password Pidgin fails to connect with ' Password required' errorPlease update to SIPE 1.14.1 or newer. Connection problems SIPE can't find any server to connect to SIPE connects to the wrong serverThis should only happen if the OCS installation you are trying to connect to is really non-standard, as SIPE tries the same order as the Microsoft Client.One common problem is that there is a clash between the auto-discovery for OCS and VoIP servers and VoIP has the higher priority.If you run Pidgin with the -debug option then you'll be able to see which names & ports SIPE tries to look up. On a Linux/UNIX machine you can manually check using the following commands (replace.company.com with your domain). $ host -tSRV sipinternaltls.tcp.company.com$ host -tSRV sipinternal.tcp.company.com$ host -tSRV sip.tls.company.com$ host -tSRV sip.tcp.company.com$ host -tA sipinternal.company.com$ host -tA sipexternal.company.com$ host -tA sip.company.com$ host -tA company.comIf none of those return the correct server, then you need to enter the correct one into the Server:Port field on the Advanced tab of the account configuration. Connection refused with error message ' You are currently not using the recommended version of the client' ' You have been rejected by the server: means your server is configured to accept only particular types of clients. Copy one of the following lines to the User Agent field in the Advanced tab of the account configuration and save.
Then try to connect to the server again. Https: // login. Com / getuserrealm. Login =& xml = 1If the returned XML text contains a non-empty node STSAuthURL then your installation uses ADFS. Login to my Microsoft Office 365 account is rejected with ' The SIP URI in the claim type requirements of the web ticket request does not match the SIP URI associated with the presented credentials'Your user name and Office365 account name are different. You'll need to update to SIPE 1.15.1 (or newer), then you can enter the Office 365 account name into the Login field. After upgrading to NSS 3.13.1 (or newer).
Windows Pidgin 2.10.7. Mac OS X 10.9.
Login fails with ' Read Error'This problem is caused by the for. There is an ongoing how this fix affects SSL connections to various SSL servers.
Setting the environment variable NSSSSLCBCRANDOMIV=0 when running Pidgin fixes the problem. $ export NSSSSLCBCRANDOMIV = 0$ pidgin$ NSSSSLCBCRANDOMIV = 0 pidginUPDATE Nov-2012: it seems that Microsoft has finally fixed their SSL code. Connection to an Office 365 account now works also with this variable set to 1, i.e. Enabling the NSS security fix by hand.UPDATE Feb-2013: Pidgin project has updated their NSS package for the Windows Pidgin build to 3.13.6.
Thus Windows users are now also experiencing this problem. You will have to use the environment variable.
Please consult the Windows help how to set environment variables for your system or user account.UPDATE Oct-2013: will no longer disable the NSS BEAST security fix by default as they did in earlier releases. You will have to use the environment variable.UPDATE Nov-2013: Apple has enabled the SSL BEAST fix by default in. Thus Adium users are now also experiencing this problem. Currently the only known workaround is to to disable the SSL BEAST fix for SIPE SSL connections.
Setup problems Where do I get the login credentials for my Microsoft Online (BPOS) account?On a Windows machine, where you have used the official Office Communicator client, go toControl Panel- User Accounts- Credentials Managerand expand the arrow for.ocslabs.microsoft.com. The User Name from the certificate will be your Login Name in the Basic tab of the account settings. For User Name use your company email address and for Password your company Windows password.It has been reported that the Server:Port setting in the Advanced tab of the account settings has to be pool1.oconline.microsoftonline.com:443 for BPOS accounts. Operating Systems Windows Why is there no Windows MSI installer package?None of the developers has a Windows development system at his disposal. The only way to create Windows release packages at the moment is by cross-compiling the code on a Linux system. That approach only supports the creation of NSIS installer packages.Official Windows release package maintainer missing, please consider to volunteer The plugin crashes when used with Windows Pidgin PortableThe reason for that is still unknown, but the best guess is that Pidgin Portable is not binary compatible with the official Pidgin Windows release. It would help if someone familiar with Windows Pidgin Portable could explain the differences.
How do I get logs from the official Microsoft client?The official client stores its log files under C:Documents and SettingsTracing.Version - -Lync there is a to turn on logging.OCS 2007 there is a to turn on logging. (BROKEN LINK)OCS 2005 follow these to turn on logging After upgrading to Windows Pidgin 2.10.7 login fails with ' Read Error'See Mac How do I get Office Communicator support working on a Mac?There are two options. use or. use (follow the instructions )Adium 1.5.6 (or older): connection fails with ' Read error'This is caused. Please update to Adium 1.5.7 or newer.
After upgrading to Mac OS X 10.9 login fails with ' Read Error'See Linux/.BSD/UNIX/. Although I have configured my machine to use pamwinbind, SIPE continue to ask for my NTLM passwordWhile the NTLM Single Sign-On support offered by works fine for Firefox, Evolution, libsoup., it doesn't support generation & verification, which is required by.Please check this for the details. After upgrading to XXX login fails with ' Read Error'See Other All my buddies are shown as offline from one day to the next Changes to my buddy list aren't savedYour account or installation has been upgraded to Lync 2013. It has a new feature called Unified Contact Store (UCS) and your contact list has been migrated to it.Please update to SIPE 1.17.0 or newer. I get the error message ' 488 Encryption Levels not compatible' when trying to set up an audio/video call(formerly known as Farsight) doesn't support SRTP and therefore SIPE is unable to create encrypted calls.
The encryption must be disabled in the client you are trying to call. Please check the file contrib/media-patches/README.txt in the source code release for the details. By default the information from my calendar is published. How do I disable this feature?Go to the account settings and switch to the Advanced tab. Then enter a non-existing URL into the Email services URL field, e.g. The connection to this URL will fail and SIPE then disables the calendar integration feature.UPDATE version 1.15.0: Go to the account settings, switch to the Advanced tab and then tick the Don't publish my calendar information box.
Microsoft Office Communicator Aol
Why do I have to use Pidgin and not Empathy/KDE Telepathy/. Why does Empathy/KDE Telepathy/.
Not show Office Communcator in the account setup? Can I use SIPE with Empathy/KDE Telepathy/.?Empathy is based on the. SIPE is a Pidgin protocol plugin, i.e. It is based on the libpurple API. Code for one framework is incompatible with the other.
But there is a telepathy communication manager, called telepathy-haze that implements an adaptor to the libpurple API. If you install the telepathy-haze package then you'll see (most of) the Pidgin protocol plugins also in Empathy.Please be sure to read up on the issue of certificate handling for telepathy-haze, because that will require manual intervention by the user if you want to connect to your Office Communication account from Empathy.NOTE: a native telepathy backend for SIPE is under development. But at the time of this writing it is too incomplete to be usable by end users.