[jitsi-issues] [JIRA] Commented: (JITSI-950) MSN Fails to connect
jira-no-reply at java.net
Mon Aug 1 19:01:38 CEST 2011
[ http://java.net/jira/browse/JITSI-950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318060#action_318060 ]
carragom commented on JITSI-950:
I've the same problem here, and this is what i do to make it work.
Log in to the hotmail site, log in to the messenger from there and then set the msn account to Available on jitsi, give it around 30 secs and it works, after you do this you won't be able to use the hotmail site anymore and the message "Messenger isn't available now" will be displayed on it. This works 100% of the time for me but it's extremely annoying.
So to summarize whenever i have the possibility of signing in from the hotmail site to messenger, jitsi does not work. After following the steps above in the hotmail site i get "Messenger isn't available now" and jitsi works.
So my guess, there is a problem with the managing of multiple sessions. The weird part of all this is that i tried a simple example as provided here http://sourceforge.net/apps/trac/java-jml/wiki/BasicMessenger.java, which is AFAIK the library jitsi uses to connect to msn and i can login and logout with not problem when jitsi can't. I would like to try to fix this but jitsi has quite a large code base and i have no idea where to start. Anyone knows which method gets called when i set my account to Available ?
> MSN Fails to connect
> Key: JITSI-950
> URL: http://java.net/jira/browse/JITSI-950
> Project: jitsi
> Issue Type: Bug
> Affects Versions: current
> Environment: Ubuntu 11.04, Sun Java 1.6.0_24, Open JDK 1.6.0_22-b22
> Reporter: bernmeister
> Attachments: sip-communicator0.log.2
> When I check/tick my MSN account to connect Jitsi appears to try to connect (the spinning wheel or whatever spins in the status menu next to my MSN account) and then nothing - no connection.
> I am able to connect with other accounts (ICQ, GTalk, AIM, Yahoo).
> I use Pidgin and my MSN account DOES connect.
> I have been unable to obtain a useful stack trace; I decided to try with OpenJDK and got what looks like an interesting series of exceptions. See the attached log file.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://java.net/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the issues