Open Source Telephony
 help / color / mirror / Atom feed
From: Guillaume Zajac <guillaume.zajac@linux.intel.com>
To: ofono@ofono.org
Subject: Re: [PATCH_v3 2/2] test: Add hangup-call script for GCF testing
Date: Mon, 06 Aug 2012 10:26:40 +0200	[thread overview]
Message-ID: <501F7FC0.5050603@linux.intel.com> (raw)
In-Reply-To: <1344013087.2083.25.camel@aeonflux>

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

Hi Marcel,

On 03/08/2012 18:58, Marcel Holtmann wrote:
> Hi Guillaume,
>
>>   Makefile.am      |    3 ++-
>>   test/hangup-call |   36 ++++++++++++++++++++++++++++++++++++
>>   2 files changed, 38 insertions(+), 1 deletions(-)
>>   create mode 100755 test/hangup-call
>>
>> diff --git a/Makefile.am b/Makefile.am
>> index 7e8f12c..8cf6920 100644
>> --- a/Makefile.am
>> +++ b/Makefile.am
>> @@ -625,7 +625,8 @@ test_scripts = test/backtrace \
>>   		test/swap-calls \
>>   		test/release-and-answer \
>>   		test/hold-and-answer \
>> -		test/hangup-multiparty
>> +		test/hangup-multiparty \
>> +		test/hangup-call
>>   
>>   if TEST
>>   testdir = $(pkglibdir)/test
>> diff --git a/test/hangup-call b/test/hangup-call
>> new file mode 100755
>> index 0000000..bc77acf
>> --- /dev/null
>> +++ b/test/hangup-call
>> @@ -0,0 +1,36 @@
>> +#!/usr/bin/python
>> +
>> +import sys
>> +import dbus
>> +
>> +bus = dbus.SystemBus()
>> +
>> +manager = dbus.Interface(bus.get_object('org.ofono', '/'),
>> +						'org.ofono.Manager')
>> +
>> +modems = manager.GetModems()
>> +path = modems[0][0]
>> +
>> +manager = dbus.Interface(bus.get_object('org.ofono', path),
>> +						'org.ofono.VoiceCallManager')
>> +
>> +calls = manager.GetCalls()
>> +if (len(calls) == 0):
>> +	print "No calls available"
>> +	sys.exit(1)
>> +
>> +if (len(sys.argv) < 2):
>> +	i = 0
>> +	for path, properties in calls:
>> +		multi = properties["Multiparty"]
>> +		print "Call Path [ %s ] Multiparty %d" % (path, multi)
>> +		print
>> +		i += 1
>> +
>> +	print "Usage: %s [ Call Path ]" % (sys.argv[0])
>> +	print
>> +	sys.exit(1)
> we have list-calls for this. So why not make this really simple and and
> require the call object path as input.

Ok, I will only check if there is an argument and don't list the call.

Kind regards,
Guillaume

      reply	other threads:[~2012-08-06  8:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-03 14:50 [PATCH_v3 0/2] Add scripts for GCF testing Guillaume Zajac
2012-08-03 14:50 ` [PATCH_v3 1/2] test: Add hangup-multiparty script " Guillaume Zajac
2012-08-03 16:57   ` Marcel Holtmann
2012-08-03 14:50 ` [PATCH_v3 2/2] test: Add hangup-call " Guillaume Zajac
2012-08-03 16:58   ` Marcel Holtmann
2012-08-06  8:26     ` Guillaume Zajac [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=501F7FC0.5050603@linux.intel.com \
    --to=guillaume.zajac@linux.intel.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