qt mobility messaging problems

[GreatGonzo]

Hi,

I am working on an application which sends SMS messages to a service which then replies. I am using QMessageService.
When I look at these messages in conversation they are flagged as delivered and not sent as the ones send through Conversation itself.
They also do not seem to be delivered immediately and looking at the dbus-monitor, I seem to get a reply from the service center

dict entry(
string "sms-failure-cause"
variant uint32 0
)

Sometimes the expected reply arrives with a long delay. I can force the reply to arrive immediately by sending another message via conversation. I then get the first reply and the second.
Has anybody seen this before?

[GreatGonzo]

Could somebody please confirm if sending SMS messages (including prompt delivery) works using Qt mobility under harmattan.

And if not what workaround there is.

[nicolai]

This code works for me:

QMessage message;
message.setBody("message helo");
message.setParentAccountId(QMessageAccount::defaul tAccount(QMessage::Sms));
message.setTo(QMessageAddress(QMessageAddress::Pho ne, "PHONENUMBER"));
qmessageservice->send(message);


And it gets send immediately. No need to send a message through
the conversion app.

By the way, I couldn't find a way to send InstantMessages (jabber for
example), as well. It seems QMessageManager doesn't even
know about any chat account.


QMessageManager* qma = new QMessageManager(this);
foreach (const QMessageAccountId &id, qma->queryAccounts()) {
qWarning() << "account " << id.toString();
}



Only lists "ring/tel/ring" and "QMF_3"(thats the email account).

nicolai

[GreatGonzo]

Turns out that this seems to be a carrier problem. The question still remains. What is different between qmessageservice and conversation....