[SFLphone] python CLI client

Emmanuel Milou emmanuel.milou at savoirfairelinux.com
Wed May 6 17:27:09 EDT 2009


Juan M. Sanchez a écrit :
> Hello Manu,
>
> Not having the daemon call list accesible from the client is 
> being a problem. Too much work to implement a feature that will 
> not be needed when you implement the method to access the call list via
> dbus.
>
> The script is almost finished (I'm now only doing code cleanups and
> optimizations), but it will not be complete as a softphone until 
> I can get the real list of calls.
>
>   
This feature is planned for the 0.9.6 version, I will do it as soon as 
possible. The related ticket is 
http://projects.savoirfairelinux.net/issues/show/1312
You may update it with your request. I will implement a DBUS method so 
that the client could retrieve the list of the call ID's from the 
daemon. Will it be enough for you?

> As for now, it is able to execute all account and call actions
> from command line arguments, and it has a "daemon" mode, where it prints
> to stdout the events received from incomingCall and callStateChanged.
>
> Tell me if you want me to send you this initial version for running your
> tests against the daemon.
>   

Yes of course I would like to test it !  Great job by the way, thank you 
for your contribution.
> Cheers
>
>
> On Tue, May 05, 2009 at 01:32:41PM -0400, Emmanuel Milou wrote:
>   
>> Juan M. Sanchez a écrit :
>>     
>>> Hello Emmanuel, 
>>>
>>> Problem solved. It was a typo in my python code, sorry :).
>>>
>>> Two more questions:
>>> 	- The client is supposed to manage the list of active calls, not the
>>> 	  daemon, correct? I mean, there is no dbus method to get the list
>>> 	  of current callIDs, right? I can see with qdbusviewer that
>>> 	  getCurrentCallID returns a table containing only the CallID of the
>>> 	  active call, and in python I'm only getting a string with the 	  
>>> CallID of the active call.
>>>   
>>>       
>> We will implement for the next release a method to retrieve the complete  
>> list of calls. The list of calls is managed by the daemon. As for now,  
>> we just have a method to get information about one specific call, or  
>> about the current call.
>>     
>>> 	- I see in sflphonectrlsimple.py: TODO: handle signals. Can I
>>> 	  continue my work with the python client knowing that noone of you
>>> 	  are writing the same code at the same time? :P
>>>
>>>   
>>>       
>> We haven't been working on this for a while.
>> However, we are very interested in that part of code, because a CLI  
>> client would be a great feature to run tests on the daemon for instance.
>> So I would be glad to integrate your work in one of our next release.
>>
>>     
>>> Thanks.
>>>
>>>
>>> On Tue, May 05, 2009 at 11:30:52AM -0400, Emmanuel Milou wrote:
>>>   
>>>       
>
>   



More information about the SFLphone mailing list