I recently installed the IM+ application on my Blackberry. Everything seems to work really well and I can send and receive messages just fine.
However, if I connect to my Openfire server and leave the client to idle, I get kicked off my connection. This seems to happen after 10-15 minutes everytime. Once I get kicked off, I’m unalbe to reconnect. If I look at the server, I can see my Blackberry IM client connect to the server in the active sessions and I can see it drop off, as soon as the server boots me. If I’m actively sending or receiving messages, the application stays connected and works fine until I stop sending messages.
I’m able to connect to a different Jabber account at Jabber.org just fine and it stays connected the entire time. I don’t get disconnected at all and have been connected for over 10 hours on that connection. Also, I’m able to connect to my Openfire server with Spark just fine and it stays connected the entire time.
This leads me to beleive that there is something odd with the configuration on my Openfire server, since the IM+ application is actually able to function correctly on a different Jabber server. Either it hates the mobile connection for some reason, or it is kicking it when it goes to idle.
Adding the xmpp.client.idle key didn’t seem to fix the problem.
However, my BB bit the dust and I’m currently waiting on a replacement, so I haven’t been able to test if further.
I am not running it on BES.
I did upgrade our OpenFire to the latest version I we were running 3.4.2 or something like that. It appears that a ping response was added in version 3.6.0 (I think) which may be the issue. I think IM+ is looking for a ping response and when it doesn’t get it, drops the connection.
If I get it working, I will post it here. The weird thing is that a previous version of the IM+ beta worked just fine, but the newest release does not. Nothing on our OpenFire server changed over that time, but it is possible the IM+ did.
Well, I tired to connect with IM+ again, and now I keep getting the error that it can’t login. Says my login information is wrong. I’ve triplechecked my login info and can login from my PC client just fine.
I have been using IM+ on iphone with several users on our openfire server, and I too began experiencing the problem of not being able to login starting yesterday. Apparently the company that makes it is German, and they are very hard to communicate with, only email links on their site. I did get a dm on twitter finally today stating that they have made changes on their server side, but they wouldn’t elaborate. I have several users that have paid for the full version of the app so I am pressing them to get it fixed.
I found out they have recently submitted a new version to the app store and I suspect they implemented some changes on their server side which is causing our problems.
Let me know if you hear anything and I will do the same.
Man, thanks so much for your reply. I’ve been so frustrated with this today.
I was able to get the demo connected before, but it was constantly dropping my Openfire connection every 10 minutes or so, as long as it was idle. I read something about it possibly being related to expecting a server ping and I upgraded the version of Openfire we use to get that feature.
I purchased the IM+ app because I got it for half off and figured the upgrade to the newest Openfire would get everything sorted out. Then I tried to connect today and couldn’t even get logged into the server.
Right now I can’t even connect to the test Jabber service they have setup…
I hope they get this fixed soon. I just read today that all the connections pass through their servers first. I thought they were all direct connections before, but that explains why it might not be working today.
I really wish someone would write a better Jabber client for the Blackberry and apparently you could use one for the iPhone.
Ever since the client has had the ability for you to go offline, but get message notifications pushed to you, all connections go through their server.
I do have one blackberry user, but he would just open it and then close it so he would get the pushed notifications, I don’t think he had any problems until now.
There are about five or so jabber clients for iphone that I know of, but only one other besides im+; beejive, that supports push notifications and it is $10 and we have already paid $10 im+ so…
I haven’t been able to get IM+ working as yet and my trial license has now run out. I emailed IM+ a yesterday but have yet to hear anything.
I have been looking around and found WebMessenger to work as is (although I’m not keen on the ui) and currently trying Vayusphere which seems ok, howver IM+ looks like it has a better UI.
Have also just downloaded BeeJive/JiveTalk but also having problems with connectivity.
I can only assume that there isn’t much demand for this seen as there doesn’t appear to be any up-to-date apps which are supported…
still broken…their support emailed me back, but it was just the canned response about checking my settings etc… I am testing beejive and it works good so far…
I am out of the office on paternity leave until September 15th. I will be unable to access email messages or any voice mail during this time. If you need IT support during this time, please contact Bill McNelis (484-450-0108) or Mary Yanocha (610-853-3589).
I will be responding to all messages when I return. Please give me a couple days to respond due to the volume of email/phone calls I am likely to receive.
I am out of the office on paternity leave until September 15th. I will be unable to access email messages or any voice mail during this time. If you need IT support during this time, please contact Bill McNelis (484-450-0108) or Mary Yanocha (610-853-3589).
I will be responding to all messages when I return. Please give me a couple days to respond due to the volume of email/phone calls I am likely to receive.
Huh, didn’t know that my email would be able to post back to the forum. Never seen that before.
I haven’t tried IM+ since then, but I’ll fire it up today and see how it works for me. I’m hoping the constant disconnect issue I had before is gone now.