Bug 828025

Summary:	Empathy unable to ring contact on Google Talk
Product:	[Fedora] Fedora	Reporter:	Aram Agajanian <agajan>
Component:	empathy	Assignee:	Brian Pepple <bdpepple>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	CC:	bdpepple
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-31 18:46:18 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Aram Agajanian 2012-06-04 03:25:45 UTC

Description of problem:
Sometimes when you try to call a Google Talk contact, Empathy is unable to ring the contact's Empathy.  It seems to ring twice on the local Empathy and then there is a Disconnect message at the bottom of the window.  The contact never hears any rings.

This problem seems to go away when the receiver logs out and then logs back in.

Version-Release number of selected component (if applicable):
telepathy-salut-0.8.0-1.fc17.x86_64
telepathy-haze-0.6.0-1.fc17.x86_64
telepathy-gabble-0.16.0-1.fc17.x86_64
telepathy-glib-0.18.1-1.fc17.x86_64
telepathy-farstream-0.4.0-2.fc17.x86_64
telepathy-filesystem-0.0.2-3.fc17.noarch
telepathy-idle-0.1.11-2.fc17.x86_64
empathy-3.4.2-1.fc17.x86_64
telepathy-logger-0.4.0-2.fc17.x86_64
telepathy-mission-control-5.12.0-1.fc17.x86_64


How reproducible:
This problem happens often but I don't know how to trigger it.  


Steps to Reproduce:
1.  Voice call Google Talk contact with Empathy.
  
Actual results:
There is a disconnect message on the caller's Empathy shortly after initiating the call.  The contact being called never hears any rings.

Expected results:
The contact being called should hear rings and be given the option to answer the call.

Comment 1 Fedora End Of Life 2013-07-03 19:49:39 UTC

This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2013-07-31 18:46:22 UTC

Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.