----- Original Message -----
> From: "Dave Kimble" <[email protected]>
> To: "Tristan Matthews" <[email protected]>, 
> [email protected]
> Sent: Monday, October 15, 2012 5:14:24 PM
> Subject: Re: [SFLphone] calls instantly fail - no diagnostics
> 
> Thanks for your help.
> The daemon was already running, so this probably wasn't going to
> work, but what it did was odd:
> =======
> dk@desktop:~$ sflphoned -d -c

Sorry, sflphoned is not in your path, assuming you installed from a package 
you'll have to do
/usr/lib/sflphoned -d -c

> No command 'sflphoned' found, did you mean:
> Command 'sflphone' from package 'sflphone-gnome' (universe)
> sflphoned: command not found
> =======
> 
> This on start up of client:
> =======
> dk@desktop:~$ sflphone-client-gnome --debug
> sflphone-client-gnome 1.2.0
> 
> Copyright (c) 2005 - 2012 Savoir-faire Linux Inc.
> [...]
> as that of the covered work.
> 
> <debug> dbus.c:648: Connect to message bus: org.sflphone.SFLphone
> <debug> dbus.c:649: object instance: /org/sflphone/SFLphone/Instance
> <debug> dbus.c:650: dbus interface: org.sflphone.SFLphone.Instance
> <debug> dbus.c:658: Connect to object instance:
> /org/sflphone/SFLphone/CallManager
> <debug> dbus.c:659: dbus interface: org.sflphone.SFLphone.CallManager
> <debug> dbus.c:724: Adding callmanager Dbus signals
> <debug> dbus.c:848: Adding configurationmanager Dbus signals
> <debug> dbus.c:624: Connected to gnome session manager
> <error> uimanager.c:1653: Could not get /ToolbarActions/Voicemail
> action
> <debug> sliders.c:151: Set value no update for speaker: 1.000000
> 
> <debug> sliders.c:155: Set value no update for mic: 1.000000
> [DK: there are no volume controls on this simple device]
> <debug> calltree.c:226: Active calltree is current_calls
> <debug> statusicon.c:71: Hide Hangup in Systray
> <debug> shortcuts.c:408: Shortcuts: Initialize bindings
> <debug> dbus.c:590: Session manager connection callback
> <debug> dbus.c:420: DBus: Registration state changed to Trying... for
> account Account:1350194261
> <debug> dbus.c:420: DBus: Registration state changed to Registered
> for account Account:1350194261
> ======
> 
> I did have (Using STUN = off) and (Same as local parameters = on).
> I now have both off and (Published Address = myfixedIP) .
> The NAT translates myfixedIP:5060 to 192.168.0.4:5060 .
> Now on calling my landline it rings and a call seems to be
> established, but the USB-phone is silent:
> ======
> <debug> uimanager.c:581: New call button pressed
> <debug> calllist.c:120: Adding call with callID 247067151 to tab
> current_calls
> <debug> calllist.c:122: Tab current_calls has 1 calls
> <debug> calltree.c:774: Added call key exchange is (null)
> <debug> calltree.c:226: Active calltree is current_calls
> <debug> calltree.c:132: Selected a call
> <debug> calltab.c:57: Select call 247067151
> <debug> uimanager.c:144: Update actions for call 247067151
> <debug> uimanager.c:205: Call State Dialing
> <debug> uimanager.c:144: Update actions for call 247067151
> <debug> uimanager.c:205: Call State Dialing
> <error> dbus.c:2100:
> GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name
> "org.gnome.SessionManager" does not exist
This is suspicious.

> <debug> calltree.c:226: Active calltree is current_calls
> <debug> calltree.c:234: AccountID
> <debug> calltree.c:244: IP2IP displaysasonce false
> <debug> calltree.c:268: Single click but no action
> <debug> calltree.c:643: Receiving in state 4
> <debug> uimanager.c:144: Update actions for call 247067151
> <debug> uimanager.c:205: Call State Dialing
> <debug> calltree.c:643: Receiving in state 4
> <debug> uimanager.c:144: Update actions for call 247067151
> <debug> uimanager.c:205: Call State Dialing
> <debug> calltree.c:643: Receiving in state 4
> <debug> uimanager.c:144: Update actions for call 247067151
> <debug> uimanager.c:205: Call State Dialing
> <debug> calltree.c:643: Receiving in state 4
> <debug> uimanager.c:144: Update actions for call 247067151
> <debug> uimanager.c:205: Call State Dialing
> <debug> calltree.c:643: Receiving in state 4
> <debug> uimanager.c:144: Update actions for call 247067151
> <debug> uimanager.c:205: Call State Dialing
> <debug> calltree.c:643: Receiving in state 4
> <debug> uimanager.c:144: Update actions for call 247067151
> <debug> uimanager.c:205: Call State Dialing
> <debug> calltree.c:643: Receiving in state 4
> <debug> uimanager.c:144: Update actions for call 247067151
> <debug> uimanager.c:205: Call State Dialing
> <debug> calltree.c:643: Receiving in state 4
> <debug> uimanager.c:144: Update actions for call 247067151
> <debug> uimanager.c:205: Call State Dialing
> <debug> calltree.c:643: Receiving in state 4
> <debug> uimanager.c:144: Update actions for call 247067151
> <debug> uimanager.c:205: Call State Dialing
> <debug> calltree.c:643: Receiving in state 4
> <debug> uimanager.c:144: Update actions for call 247067151
> <debug> uimanager.c:205: Call State Dialing
> <debug> uimanager.c:707: Pick up
> <debug> actions.c:730: Placing call from to 0740689270 using account
> <debug> actions.c:747: No account set for this call, use first of the
> list
> <debug> dbus.c:555: Sip call state changed 247067151
> <debug> actions.c:1037: Call State changed Session Progress
> <error> dbus.c:81: Message did not receive a reply (timeout by
> message bus)

This means the daemon has crashed...

> <debug> calltree.c:643: Receiving in state 4
> <debug> uimanager.c:144: Update actions for call 247067151
> <debug> uimanager.c:205: Call State Dialing
> <debug> uimanager.c:144: Update actions for call 247067151
> <debug> uimanager.c:205: Call State Dialing
> <debug> calltree.c:643: Receiving in state 2
> <debug> uimanager.c:144: Update actions for call 247067151
> <debug> uimanager.c:195: Call State Ringing
> <debug> uimanager.c:144: Update actions for call 247067151
> <debug> uimanager.c:195: Call State Ringing
> <debug> dbus.c:420: DBus: Registration state changed to Trying... for
> account Account:1350194261
> <debug> dbus.c:420: DBus: Registration state changed to Registered
> for account Account:1350194261
> <debug> accountlistconfigdialog.c:151: Account is enabled :true
> <debug> accountlistconfigdialog.c:151: Account is enabled :true
> <debug> accountlistconfigdialog.c:224: Selected account has accountID
> IP2IP
> <debug> accountlistconfigdialog.c:224: Selected account has accountID
> Account:1350194261
> <debug> audioconf.c:91: GSM is active
> <debug> audioconf.c:91: G722 is active
> <debug> audioconf.c:91: PCMU is active
> <debug> audioconf.c:91: PCMA is active
> <debug> audioconf.c:91: speex is active
> <debug> audioconf.c:91: speex is active
> <debug> audioconf.c:91: speex is active
> <debug> accountconfigdialog.c:1018: Build advanced tab
> <debug> accountconfigdialog.c:556: getInterfaceAddrFromName use
> default interface (0.0.0.0)
> 
> <debug> accountconfigdialog.c:592: Showing manual publishing options
> <debug> accountconfigdialog.c:625: disabling stun options, showing
> Local/Published info
> <debug> accountconfigdialog.c:592: Showing manual publishing options
> ======
> 
> It seems to have used the IP2IP account, when it should have used my
> SIP provider account.
> The status line in the GUI shows: "Using account Pennytel(SIP)".

At this point the GUI is no longer telling you anything useful. FYI: In the 
next release 
of SFLphone, the GUI will quit as soon as it realizes that the daemon has 
crashed.

Could you please file a bug report and in particular, create a stack trace of 
the daemon?
See https://projects.savoirfairelinux.com/projects/sflphone/wiki/BugReports

Thanks,
Tristan 

> 
> Dave
> 
> 
> On 16/10/12 01:03, Tristan Matthews wrote:
> 
> 
> Hi Dave,
> 
> ----- Original Message -----
> 
> From: "Dave Kimble" <[email protected]> To: [email protected] ,
> [email protected] Sent: Sunday, October 14, 2012
> 5:08:34 PM
> Subject: [SFLphone] calls instantly fail - no diagnostics
> 
> From the terminal:
> dk@desktop:~$ sflphone
> <error> uimanager.c:1653: Could not get /ToolbarActions/Voicemail
> action
> <error> calllist.c:197: Could not find call 265668630 in tab
> current_calls
> <warning> dbus.c:250: Call does not exist
> 
> Just in case "265668630" is supposed to be the number dialled , it
> isn't
> what I dialled. The identifier "265668630" is a label to uniquely
> identify the call, it's
> just used internally by SFLphone and doesn't have anything to do with
> the
> number that was dialled.
> 
> To get more debug info, could you launch sflphone daemon and client
> processes
> separately?
> 
> In on terminal, do:
> 
> dk@desktop:~$ sflphoned -d -c
> 
> And in another:
> 
> dk@desktop:~$ sflphone-client-gnome --debug
> 
> Best,
> Tristan
> 
> Dave
> _______________________________________________
> 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