Took me a long time to figure it out!
Finaly, when i invited my Gtalk ID to OVI, even after 10 minutes, i received no invite. Then, on checking the invite dialogue again, i found out that you were sending the invites to @googlemail.com . Whereas, Google Accouns have @gmail.com id.
Hope this is rectified in the next release :)
OK, thanks. Terribly sorry about this. In some countries, the domain is different. We'll fix this as soon as possible.
-Kristian
This may have happened to me. I had the following experience last night...
Having seen mentions of the possibility of using a desktop XMPP client to log in and establish a transport for my Gmail contacts, I hooked up Kopete (the KDE messaging client) and attempted to do so. Observations: 1) Jabber service discovery on chat.ovi.com fails without providing any error message. So I registered with programmer-art.org's XMPP server, and registered their transport to/from Gtalk/Gmail. Contacts, status updates, and messaging now propagated correctly to and from Gmail into programmer-art.org. I now added username@gtalk.programmer-art.org as a transport in the Ovi.com account. We seemed to get propagation into the Ovi.com XMPP server and thence to the client. Ovi.com got an authorisation request from programmer-art.org and programmer-art.org got one from ovi.com, both were accepted.
I now fired up CoO on my Nokia E71 and observed that my username@gtalk.programmer-art.org had been added as a friend, but was showing "waiting for accpt". No other contacts or messages propagated to the device, but changes of status on the device did echo to username@programmer-art.org. Further, transport into the ovi account only worked while I stayed logged in to programmer-art from the PC - obviously not ideal. It may be that the invite to me via the transport was dropped due to the gmail/googlemail issue - looking at the Ovi account from Kopete, the transport never went green. I also experimented with adjusting the XMPP resource priority settings, thinking this was the problem, but no, it wasn't.
Please note that going by country will not work; I'm in a country where Google issues googlemail.com addresses, but because I was an early adopter I have a gmail.com from before the lawsuit...
Just to update this, I've just logged in on ovi.com from the desktop client. Nothing was propagated into ovi until I logged in to programmer-art.org, at which point status and messages were transmitted. Gmail message notifications appear as coming from alex.harrowell@ovi.com, which I take to mean it is the ovi account I'm watching.
OK, I've just logged in from the E71. f15d (CoO's resource name) is set with higher priority than Kopete, so correctly Kopete relinquished the lock and the programmer-art.org account showed me coming back up from ovi.com. On the device screen, it's showing two contacts, "My profile" and the transport, but it's not treating the transport as a transport - nothing is being propagated to the device.
Our client doesn't have a transport support inbuilt, but I've heard people being able to complete the transport configuration with other clients (e.g. PSI) to get 'em working. After the configuration you should be able to communicate through the transports just fine.
Not sure what's exactly wrong in the scenario you describe above, but again as said, I've heard it can be done.
-kristian