Open Source Telephony
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: ofono@ofono.org
Subject: Re: Error in setting "VoiceNoReplyTimeout" property in call-forwarding
Date: Tue, 05 Oct 2010 19:44:27 -0500	[thread overview]
Message-ID: <4CABC66B.8040208@gmail.com> (raw)
In-Reply-To: <AANLkTinv1TVbNL0-vzgm+UN8mV_HUq5xbfjBX69QaUsi@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]

Hi Sai,

On 10/05/2010 09:49 AM, sai koushik wrote:
> Hi,
> 
> we are working on use-case to activate call-forwarding rule when no
> reply , but ofono is returning error "Invalid arguments in method
> call" when trying to set the reply-timeout value.
> 
> below is the code for the use-case
> 
> GValue val={0,{{0}}};
> g_value_init(&val,G_TYPE_UINT);
> 
> uint value=30;
> g_value_set_uint(&val,value);
> 
> GError *error=NULL;
> dbus_g_proxy_call (proxy,"SetProperty", &error,
> G_TYPE_STRING,"VoiceNoReplyTimeout", G_TYPE_VALUE,&val,
> G_TYPE_INVALID, G_TYPE_INVALID);
> 
> 
> in our observation , when preparing DBusMessage, it is taking uint32
> as basic type for uint ,
> and in ofono after receiving DBusMessage it is expecting for value of
> type DBUS_TYPE_UINT16 but the message contains DBUS_TYPE_UINT32 type
> value.
> 
> is there is any specific reason to expect the time-out value as uint16 type.

You need to be constructing the message with the type that oFono
expects.  In this particular case it is a uint16.

Just as a heads up, this API will change to use 'byte' instead of
'uint16' since the Timeout value can only be between 1 and 30.

Regards,
-Denis

      reply	other threads:[~2010-10-06  0:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05 14:49 Error in setting "VoiceNoReplyTimeout" property in call-forwarding sai koushik
2010-10-06  0:44 ` Denis Kenzior [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CABC66B.8040208@gmail.com \
    --to=denkenz@gmail.com \
    --cc=ofono@ofono.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox