First off, -1 for requiring me to register in order to submit a bug report.  -10 for not providing a way to have the activation code re-sent for when it doesn’t get received the first time, thus requiring me to register a 2nd time.

Anyway.

There is a private jabber server that I connect to on a regular basis, using iChat.  In iChat’s settings, my jabber id is “myname@foo.net”, and server is “talk.foo.net”, with use SSL (port 5223).  The specific (group) chat room I connect to is “roomname@conference.bar.com” connecting with the above account (notice the account is on a different domain than the room).  In iChat (and Adium) this works beautifully.

In OneTeam for iPhone, though…not so much.  I have configured OneTeam exactly the same, except for using a unique nickname.  The problem is, instead of connecting to the room “roomname@conference.bar.com”, it actually connects to “roomname@conference.foo.net”.  That is actually a valid room, as it is the back-up room for the one I actually want to get into, but regardless, is the wrong room, given my actual configuration.  It appears to be conflating my account info with the desired room information.

Bottom line, I ask to connect to room A, and it connects to room B instead.

This is using the latest version available from the store, v3.3.1.  Any suggestions on fixing this?

We did not manage to reproduce the problem. From ProcessOne domain, I do add room (+) then enter manually, then use conference.jabber.org then add room name and I join the room on jabber.org.
Do you use the same process ? Do you use another path in the app?

Ok, I *think* the problem occurs when you enter a room name in for the “name of the group chat service you wish to use”.  I reset the app settings, and re-configured, and was finally able to get to do the right thing, and of course, now, I cannot reproduce today what I managed to do a half-dozen times yesterday.  Of course, I’m less motivated to figure out what happened yesterday now that I have it working, but I have some friends that will probably be setting this up on iPad soon (for WWDC), so perhaps they’ll run into the same problem I did.  At least now I can coach them through the process.

Thanks for your quick reply yesterday.

You are welcome.

Please, let us know if you have other feedback or feature requests.