[Telepathy] telepathy-rakia not working (Was: ANNOUNCE: telepathy-rakia 0.7.2)
Hi, -Original Message- From: ext Mystilleef [mailto:mystill...@gmail.com] Sent: 26 October, 2011 17:39 To: Zabaluev Mikhail (Nokia-MP/Helsinki) Cc: telepathy@lists.freedesktop.org; ftp-rele...@lists.freedesktop.org Subject: Re: [Telepathy] ANNOUNCE: telepathy-rakia 0.7.2 Fedora rawhide now uses telepathy-rakia version 0.7.2 Since the change from sofia to rakia my app has stopped working. It's always offline. It turns out Mission Control is not starting the telepathy- rakia process. Or the process is timing out. Starting the process manually results in the following error. lateef@submission ~/D/teletest /usr/libexec/telepathy-rakia tp-glib-DEBUG: started version 0.7.2 (telepathy-glib version 0.16.0) tp-glib-DEBUG: no connections, and timed out tp-glib-Message: Exiting You can make it run persistently by exporting RAKIA_PERSIST=1. Also export RAKIA_DEBUG=all for more information in the log. You can also see the logs in the debug window in Empathy, if you select the rakia component (or it might still be listed as sofiasip, I did not check yet). Hope this helps, Mikhail smime.p7s Description: S/MIME cryptographic signature ___ telepathy mailing list telepathy@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] telepathy-rakia not working (Was: ANNOUNCE: telepathy-rakia 0.7.2)
Thanks, with your help, I enabled debugging and got the rakia process to persist. My app is still offline. Here is the pertinent debug information. In particular, the following line looks strange. Any ideas? ** DEBUG: outbound(0x8c20620): FAILED to validate sip:1295977e0@174.109.174.240:43327;transport=udp ** DEBUG: outbound(0x8c20620): FAILED with 200 OK = ** DEBUG: rakia_base_connection_sofia_callback: event nua_i_outbound: 101 NAT detected ** DEBUG: rakia_base_connection_sofia_callback: connection 0x8c1b058, refcount 1 ** DEBUG: rakia_base_connection_sofia_callback: dispatching to target 0x8c1b058 (handle 0x8c20620) ** DEBUG: rakia_base_connection_sofia_callback: event nua_i_outbound for target 0x8c1b058 was not consumed ** DEBUG: rakia_base_connection_sofia_callback: exit ** DEBUG: rakia_base_connection_sofia_callback: event nua_r_register: 401 Unauthorized ** DEBUG: rakia_base_connection_sofia_callback: connection 0x8c1b058, refcount 1 ** DEBUG: rakia_base_connection_sofia_callback: dispatching to target 0x8c1b058 (handle 0x8c20620) ** DEBUG: priv_handle_auth: response presents an authentication challenge ** DEBUG: priv_handle_auth: using the primary auth credentials ** DEBUG: priv_handle_auth_continue: Digest-authenticating user='1295977e0' realm=sipgate.com ** DEBUG: rakia_base_connection_sofia_callback: exit ** DEBUG: rakia_base_connection_sofia_callback: event nua_r_register: 200 OK ** DEBUG: rakia_base_connection_sofia_callback: connection 0x8c1b058, refcount 1 ** DEBUG: rakia_base_connection_sofia_callback: dispatching to target 0x8c1b058 (handle 0x8c20620) ** DEBUG: rakia_connection_nua_r_register_cb: successfully registered to the network tp-glib/connection-DEBUG: tp_base_connection_change_status: was 1, now 0, for reason 1 tp-glib/connection-DEBUG: tp_base_connection_change_status: emitting status-changed to 0, for reason 1 ** DEBUG: rakia_base_connection_sofia_callback: exit ** DEBUG: conn_get_alias: handle 1 got alias 129597...@sipgate.com ** DEBUG: rakia_connection_set_aliases: setting alias for self: 1295977e0 Gtk-WARNING **: Unknown property: GtkGrid.n-rows ** DEBUG: outbound(0x8c20620): FAILED to validate sip:1295977e0@174.109.174.240:43327;transport=udp ** DEBUG: outbound(0x8c20620): FAILED with 200 OK ** DEBUG: rakia_base_connection_sofia_callback: event nua_i_outbound: 200 OK ** DEBUG: rakia_base_connection_sofia_callback: connection 0x8c1b058, refcount 1 ** DEBUG: rakia_base_connection_sofia_callback: dispatching to target 0x8c1b058 (handle 0x8c20620) ** DEBUG: rakia_base_connection_sofia_callback: event nua_i_outbound for target 0x8c1b058 was not consumed ** DEBUG: rakia_base_connection_sofia_callback: exit ** DEBUG: nta_agent: tport: Bad message ** DEBUG: nta_agent: tport: Bad message ** DEBUG: outbound(0x8c20620): FAILED to validate sip:1295977e0@174.109.174.240:43327;transport=udp ** DEBUG: outbound(0x8c20620): FAILED with 200 OK ** DEBUG: rakia_base_connection_sofia_callback: event nua_i_outbound: 200 OK ** DEBUG: rakia_base_connection_sofia_callback: connection 0x8c1b058, refcount 1 ** DEBUG: rakia_base_connection_sofia_callback: dispatching to target 0x8c1b058 (handle 0x8c20620) ** DEBUG: rakia_base_connection_sofia_callback: event nua_i_outbound for target 0x8c1b058 was not consumed ** DEBUG: rakia_base_connection_sofia_callback: exit = On Wednesday, October 26, 2011, wrote: Hi, -Original Message- From: ext Mystilleef [mailto:mystill...@gmail.com javascript:;] Sent: 26 October, 2011 17:39 To: Zabaluev Mikhail (Nokia-MP/Helsinki) Cc: telepathy@lists.freedesktop.org javascript:;; ftp-rele...@lists.freedesktop.org javascript:; Subject: Re: [Telepathy] ANNOUNCE: telepathy-rakia 0.7.2 Fedora rawhide now uses telepathy-rakia version 0.7.2 Since the change from sofia to rakia my app has stopped working. It's always offline. It turns out Mission Control is not starting the telepathy- rakia process. Or the process is timing out. Starting the process manually results in the following error. lateef@submission ~/D/teletest /usr/libexec/telepathy-rakia tp-glib-DEBUG: started version 0.7.2 (telepathy-glib version 0.16.0) tp-glib-DEBUG: no connections, and timed out tp-glib-Message: Exiting You can make it run persistently by exporting RAKIA_PERSIST=1. Also export RAKIA_DEBUG=all for more information in the log. You can also see the logs in the debug window in Empathy, if you select the rakia component (or it might still be listed as sofiasip, I did not check yet). Hope this helps, Mikhail ___ telepathy mailing list telepathy@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] telepathy-rakia not working (Was: ANNOUNCE: telepathy-rakia 0.7.2)
Hi, -Original Message- From: ext Mystilleef [mailto:mystill...@gmail.com] Sent: 26 October, 2011 18:57 To: Zabaluev Mikhail (Nokia-MP/Helsinki) Cc: telepathy@lists.freedesktop.org Subject: Re: [Telepathy] telepathy-rakia not working (Was: ANNOUNCE: telepathy-rakia 0.7.2) Thanks, with your help, I enabled debugging and got the rakia process to persist. My app is still offline. Here is the pertinent debug information. In particular, the following line looks strange. Any ideas? ** DEBUG: outbound(0x8c20620): FAILED to validate sip:1295977e0@174.109.174.240:43327;transport=udp ** DEBUG: outbound(0x8c20620): FAILED with 200 OK This is harmless. In fact this log shows that telepathy-rakia has successfully connected. Can you capture the dbus log with dbus-monitor --session (filtering irrelevant traffic if needed for privacy reasons) and send it to me? Best regards, Mikhail smime.p7s Description: S/MIME cryptographic signature ___ telepathy mailing list telepathy@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/telepathy
Re: [Telepathy] telepathy-rakia not working (Was: ANNOUNCE: telepathy-rakia 0.7.2)
variant uint32 1 ) dict entry( string ConnectionErrorDetails variant array [ ] ) dict entry( string ConnectionError variant string ) ] signal sender=org.freedesktop.DBus - dest=(null destination) serial=76 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string :1.139 string string :1.139 method call sender=:1.139 - dest=org.freedesktop.DBus serial=1 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=Hello method call sender=:1.139 - dest=org.freedesktop.DBus serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=RequestName string org.freedesktop.Telepathy.ConnectionManager.sofiasip uint32 4 signal sender=org.freedesktop.DBus - dest=(null destination) serial=77 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string :1.139 string :1.139 string signal sender=:1.125 - dest=(null destination) serial=150 path=/org/freedesktop/Telepathy/Account/rakia/sip/_31295977e0_40sipgate_2ecom0; interface=org.freedesktop.Telepathy.Account; member=AccountPropertyChanged array [ dict entry( string Connection variant object path / ) dict entry( string ConnectionStatusReason variant uint32 2 ) dict entry( string ConnectionStatus variant uint32 2 ) dict entry( string ConnectionErrorDetails variant array [ ] ) dict entry( string ConnectionError variant string ) ] signal sender=:1.125 - dest=(null destination) serial=151 path=/com/nokia/MissionControl/requests/r1; interface=org.freedesktop.Telepathy.ChannelRequest; member=Failed string org.freedesktop.Telepathy.Error.Disconnected string Account rakia/sip/_31295977e0_40sipgate_2ecom0 disconnected with reason 2 method call sender=:1.134 - dest=org.freedesktop.DBus serial=58 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=RemoveMatch string type='signal',sender=':1.125',path='/com/nokia/MissionControl/requests/r1',interface='org.freedesktop.Telepathy.ChannelRequest' method call sender=:1.134 - dest=org.freedesktop.DBus serial=59 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=RemoveMatch string type='signal',sender='org.freedesktop.DBus',path='/org/freedesktop/DBus',interface='org.freedesktop.DBus',member='NameOwnerChanged',arg0=':1.125' === On Wed, Oct 26, 2011 at 12:11 PM, mikhail.zabal...@nokia.com wrote: Hi, -Original Message- From: ext Mystilleef [mailto:mystill...@gmail.com] Sent: 26 October, 2011 18:57 To: Zabaluev Mikhail (Nokia-MP/Helsinki) Cc: telepathy@lists.freedesktop.org Subject: Re: [Telepathy] telepathy-rakia not working (Was: ANNOUNCE: telepathy-rakia 0.7.2) Thanks, with your help, I enabled debugging and got the rakia process to persist. My app is still offline. Here is the pertinent debug information. In particular, the following line looks strange. Any ideas? ** DEBUG: outbound(0x8c20620): FAILED to validate sip:1295977e0@174.109.174.240:43327;transport=udp ** DEBUG: outbound(0x8c20620): FAILED with 200 OK This is harmless. In fact this log shows that telepathy-rakia has successfully connected. Can you capture the dbus log with dbus-monitor --session (filtering irrelevant traffic if needed for privacy reasons) and send it to me? Best regards, Mikhail ___ telepathy mailing list telepathy@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/telepathy
