Hello Florian,

SFLPhone is actually two process, a daemon and a client. The client log you 
sent loop fine:
(the call not found in tree warnings are normal, sflphone-kde make sure the 
call have been removed
as many time as there is a change to prevent ghost call from being added if an 
event happen (by
mistake or buggy registrar implementation) after the call end.

# Sequence 1
> Calling action  0  on call with state  "Dialing" . Become  "Initialization" 
> <-- Press enter
> Call State Changed for call   "984411720"  . New state :  "FAILURE" <-- Fail
> Calling action  1  on call with state  "Failed" . Become  "Over" <-- Press 
> escape
> Canceling call. callId :  "729243532" ConfId: "729243532" <-- Cancel = remove 
> from list before the timer start, so far so good
> HangUp failed, the call was probably already over <-- Notify the daemon again 
> that the client don't want to ear about this call ever again, technically 
> redundant with the failure notification, again to prevent ghost calls.

# Sequence 2
> Call is created as dialing, no log message (I should add one)
> Calling action  1  on call with state  "Dialing" . Become  "Over" <-- "1" is 
> "REFUSE" (escape), so this tell me escape have been pressed again, not enter
> Call State Changed for call   "729243532"  . New state :  "HUNGUP" <-- The 
> call end as it has been refused, are you sure you pressed enter or pickup?

So from the client side, this look pretty normal. That one, however, is not:

> Call doesn't exist in this client. Might have been initialized by another 
> client instance before this one started.

So the client got an answer from a call it never heard of, or dismissed for 
some reasons. This is sent from the "callStateChanged" daemon signal and is not 
in the client known call list (m_sPrivateCallList_callId). It only happen if 
the daemon explicitly ask the client to do it _or_ if there is a fatal error 
with the call. The the former case, its a bug and in the latter one, there 
would be a message in the log about it.

So given this, I need more information about the sequence to know how it 
happened. To do this, I will need the other log, here is how to generate it:

killall sflphone-client-kde
killall sflphoned
/usr/lib/sflphone/sflphoned -c -d

# In an other terminal
sflphone-client-kde

The sflphoned log is the most important

Regards,
Emmanuel Lepage
----- Original Message -----
From: "Florian Auer" <[email protected]>
To: [email protected]
Sent: Thursday, August 7, 2014 11:49:16 AM
Subject: [SFLphone] SFLphone won't hangup (Cannot remove call: call not found 
in tree)

Hi guys,

I face a bug which sounds very similar to an older one:

http://lists.savoirfairelinux.net/pipermail/sflphone/2013-September/003308.html

Steps to reproduce:

- Dial a non-existing number
→ SIP server (here: Starface) replies "Unknown", busy 

- Hit Esc key or click "Hangup"
→ SFLphone keeps playing the buys tone

- Dial some random numbers and hit Esc key
→ SFLphone stops playing busy tone

Furthermore I cannot accept any incoming calls. SFLphone pretends to accept 
the call and stops playing the ringtone, but it doesn't pick up actually.

This is what I get as output in the terminal:

-- 8< --
Calling  ""  with account  Account(0x23887a0, name = "Account:864217638") . 
callId :  "984411720" ConfId: "984411720" 
Calling action  0  on call with state  "Dialing" . Become  "Initialization" 
Call State Changed for call   "984411720"  . New state :  "FAILURE" 
Call found Call(0x275df60, name = "Call:984411720") "Initialization" 
Warning : call  "984411720"  had an unexpected transition of state.( "Failed" 
) 
Stoping call. callId :  "984411720" ConfId: "984411720" 
Calling stateChanged  "FAILURE"  ->  5  on call with state  "Initialization" . 
Become  "Failed" 
Cannot remove call: call not found in tree 
Cannot remove call: call not found in tree 
Cannot remove call: call not found in tree 
Calling action  1  on call with state  "Failed" . Become  "Over" 
Cannot remove call: call not found in tree 
Canceling call. callId :  "729243532" ConfId: "729243532" 
HangUp failed, the call was probably already over 
Cannot remove call: call not found in tree 
Cannot remove call: call not found in tree 
Calling action  1  on call with state  "Dialing" . Become  "Over" 
Call State Changed for call   "729243532"  . New state :  "HUNGUP" 
Call not found 
Call doesn't exist in this client. Might have been initialized by another 
client instance before this one started.
-- 8< --

_Additional Info_

$ lsb_release -drc
Description:    Ubuntu 14.04.1 LTS
Release:        14.04
Codename:       trusty

$ uname -a
Linux OXPS-FA-E7440 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 
2014 x86_64 x86_64 x86_64 GNU/Linux

SFLPhone-KDE
Version 1.4.0
Using KDE Development Platform 4.13.2

sflphone-kde 1.4.0~ppa2~trusty amd64
sflphone-daemon-video 1.4.0~ppa2~trusty amd64


Any hints?


Best,
Florian
_______________________________________________
SFLphone mailing list
[email protected]
http://lists.savoirfairelinux.net/mailman/listinfo/sflphone
_______________________________________________
SFLphone mailing list
[email protected]
http://lists.savoirfairelinux.net/mailman/listinfo/sflphone

Reply via email to