Hi, I use gentoo amd64 with kde-4.9.1 and kde-telepathy 0.5. Unfortunately I can't authenticate to my asterisk sip server, I get "Wrong password" in the asterisk CLI. If I create an account without password it does connect flawlessly. Reproducible: Always
It's not easy to help you because it works for me, so it might be related to the sip server you are using. Are you sure it is a kde-telepathy problem? Did you try with another client? If it does not work it's a problem in your server Did you try with Empathy? If it does not work it's a problem in telepathy-rakia If both work then it's our fault! Then please post the output of "/usr/lib/kde4/libexec/ktp-auth-handler --persist --debug" when you try to set the sip account online...
I have lots of SNOM phones which work, also ekiga did work too. I'm emerging empathy...
If I create the account with empaty then it works even with kde-telepathy! There is no output from "/usr/lib/kde4/libexec/ktp-auth-handler --persist --debug"
If I edit the password of the account created by empathy it does no longer work!
If I edit the account created by kde-telepathy with empathy it seems like if there is no password set for the account!
probably you have the debug disabled run "kdebugdialog" and enable debug for ktp-auth-handler and try again... Also check in your wallet if you have a password stored for that account and if it is correct
I emerged net-im/ktp-auth-handler with the debug use flag but there are still no debug info. I can see the password in kwallet. Also even when the sip account is connected, as soon as I start ktp-dialout-ui I get "No capable accounts found. Please make sure that you are online and that the accounts that you have configured support audio and/or video calls"
We need some debug output otherwise we can't do anything. Please run ktp-debugger (0.5.2 onwards) shortly after trying to connect, and attach any output from the mission-control and rakia tabs.
Jan 18 21:27:48 tux asterisk[3374]: NOTICE[3392]: chan_sip.c:27726 in handle_request_register: Registration from '<sip:vladi-lt@sip.aresgate.net>' failed for '75.80.173.129:54420' - Wrong password Jan 18 21:27:48 tux asterisk[3374]: NOTICE[3392]: chan_sip.c:27726 in handle_request_register: Registration from '<sip:vladi-lt@sip.aresgate.net>' failed for '75.80.173.129:54420' - Wrong password KDE Telepathy debug: 01/18/2013 18:27:48.153712 - [mcd] get_mcddbusprop: org.freedesktop.Telepathy.Account, DisplayName 01/18/2013 18:27:48.153788 - [mcd] set_display_name: called for sofiasip/sip/vladi_2dlt_40sip_2earesgate_2enet0 01/18/2013 18:27:48.629798 - [mcd] on_connection_status_changed: status_changed called from tp (2) 01/18/2013 18:27:48.630002 - [mcd] mcd_connection_invalidated_cb: Proxy destroyed (Unknown disconnection reason)! 01/18/2013 18:27:48.630103 - [mcd] _mcd_connection_release_tp_connection: 0x1a46cc0 01/18/2013 18:27:48.630222 - [mcd] _mcd_account_set_connection_status: sofiasip/sip/vladi_2dlt_40sip_2earesgate_2enet0: 2 because 3 01/18/2013 18:27:48.630314 - [mcd] mcd_account_freeze_properties: sofiasip/sip/vladi_2dlt_40sip_2earesgate_2enet0 01/18/2013 18:27:48.630402 - [mcd] _mcd_account_set_connection_status: changing error details 01/18/2013 18:27:48.630518 - [mcd] _mcd_account_set_connection_status: changing connection status from 1 to 2 01/18/2013 18:27:48.630609 - [mcd] _mcd_account_set_connection_status: changing connection status reason from 1 to 3 01/18/2013 18:27:48.630702 - [mcd] mcd_account_changed_property: called: Connection 01/18/2013 18:27:48.630789 - [mcd] mcd_account_changed_property: First changed property 01/18/2013 18:27:48.631227 - [mcd] mcd_account_changed_property: called: ConnectionStatus 01/18/2013 18:27:48.631335 - [mcd] mcd_account_changed_property: called: ConnectionStatusReason 01/18/2013 18:27:48.631963 - [mcd] mcd_account_changed_property: called: ConnectionError 01/18/2013 18:27:48.632100 - [mcd] mcd_account_changed_property: called: ConnectionErrorDetails 01/18/2013 18:27:48.632209 - [mcd] mcd_account_thaw_properties: sofiasip/sip/vladi_2dlt_40sip_2earesgate_2enet0 01/18/2013 18:27:48.632298 - [mcd] emit_property_changed: called 01/18/2013 18:27:48.632602 - [mcd] _mcd_operation_abort: Operation abort received, aborting all children 01/18/2013 18:27:48.632703 - [mcd] on_connection_abort: called (0x1a46cc0, account sofiasip/sip/vladi_2dlt_40sip_2earesgate_2enet0) 01/18/2013 18:27:48.632817 - [mcd] _mcd_mission_set_parent: child = 0x1a46cc0, parent = (nil) 01/18/2013 18:27:48.632919 - [mcd] _mcd_operation_remove_mission: removing mission: 0x1a46cc0 01/18/2013 18:27:48.633013 - [mcd] _mcd_connection_dispose: called for object 0x1a46cc0 01/18/2013 18:27:48.633104 - [mcd] _mcd_connection_release_tp_connection: 0x1a46cc0 01/18/2013 18:27:48.633250 - [mcd] _mcd_operation_dispose: operation disposed 01/18/2013 18:27:48.633363 - [mcd] _mcd_mission_dispose: mission disposed 0x1a46cc0 01/18/2013 18:27:48.633517 - [mcd] mcd_dispatcher_lost_connection: 0x1a40030: 0x1a46cc0 01/18/2013 18:27:48.633615 - [mcd] _mcd_mission_finalize: mission finalized 0x1a46cc0 01/18/2013 18:27:48.633717 - [mcd] on_connection_ready: got error: Unknown disconnection reason
Does comment #9 provide the requested information?
Setting status, please check comment #9.
Sorry for the delay: I know what's causing this. Trace shows no mention of authentication. SofiaISP uses the old authentication mechanism that we don't support. In the legacy system passwords were stored in gnome-keyring and all handled by Telepathy itself. This is why it works when you set the password in empathy. We store the password in kwallet (and actually remove any password from MC) but this requires the connection manager to be updated. I'm confirming this bug but I'm not sure how we can fix this properly. There's no way to tell which CMs support which authentication mechanism. The correct way to fix that is upstream. darkbasic@linuxsystems.it can you confirm what versions of telepathy-sofiaisp and/or telepathy-rakia and which one you're using. It should be rakia. It /seems/ the new password interface is implemented in rakia 0.7.1
I have both installed, sofia is at version 1.12.11 and rakia 0.6.8. niko@laptop ~ $ eix sofia [I] net-libs/sofia-sip Available versions: 1.12.10^t 1.12.11^t {{ssl static-libs}} Installed versions: 1.12.11^t(16:04:59 15/03/2013)(ssl -static-libs) Homepage: http://sofia-sip.sourceforge.net/ Description: RFC3261 compliant SIP User-Agent library niko@laptop ~ $ eix rakia [I] net-voip/telepathy-rakia Available versions: 0.6.6 0.6.8 ~0.7.4 {{test}} Installed versions: 0.6.8(01:57:48 16/03/2013)(-test) Homepage: http://telepathy.freedesktop.org/ Description: A SIP connection manager for Telepathy based around the Sofia-SIP library niko@laptop ~ $ equery depends net-voip/telepathy-rakia * These packages depend on net-voip/telepathy-rakia: net-im/telepathy-connection-managers-1 (sip ? >=net-voip/telepathy-rakia-0.5.18) niko@laptop ~ $ equery depends net-libs/sofia-sip * These packages depend on net-libs/sofia-sip: net-voip/telepathy-rakia-0.6.8 (>=net-libs/sofia-sip-1.12.11) niko@laptop ~ $ eix net-im/telepathy-connection-managers [I] net-im/telepathy-connection-managers Available versions: 1 ~2 {{icq irc jabber msn sip yahoo zeroconf}} Installed versions: 1(13:47:34 15/03/2013)(jabber sip zeroconf -icq -irc -msn -yahoo) Homepage: http://telepathy.freedesktop.org/ Description: Meta-package for Telepathy Connection Managers niko@laptop ~ $ equery depends net-im/telepathy-connection-managers * These packages depend on net-im/telepathy-connection-managers: net-im/kde-telepathy-meta-0.5.80 (net-im/telepathy-connection-managers) I don't know why it needs both. I will try updating rakia to 0.7.4 anyway (hoping it doesn't use sofia).
I don't know either, I was under the impression Rakia replaced SofiaISP. If you can't manage to update using "mc-tool update accountId password:myPassword" should work. where accountId is the ID from mc-tool list, and myPassword is your password.
As there has been no reaction over a year and comment #12 says newer Rakia is needed, I'm closing this bug under the impression that newer Rakia fixed the problem.