Bug 790644 - no audio on linphonec calls
Summary: no audio on linphonec calls
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: linphone
Version: 16
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-15 02:04 UTC by Janina Sajka
Modified: 2013-02-13 19:29 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 19:29:45 UTC
Type: ---


Attachments (Terms of Use)

Description Janina Sajka 2012-02-15 02:04:54 UTC
Description of problem:linphonec loads with the following error:
linphonec> ortp-error-getaddrinfo() failed for REGISTER:3478 : Name or service not known
It behaves as though it were working, but there is simply no audio in either direction
Version-Release number of selected component (if applicable):3.5.0-2.fc16


How reproducible:Always


Steps to Reproduce:Launch linphonec, watch it register,
1.try placing a call. On screen looks OK, but no audio.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 nucleo 2012-02-15 02:25:51 UTC
Did you tried to setup Linphone GUI (Audio/Video RTP ports, Internet connection, audio devices), is it works for you?

Comment 2 nucleo 2012-02-15 03:06:45 UTC
Also can you check what ortp version installed?
You also can try temporary replace .linphonerc configuration file and check is it works with clean config.
Anyway, it works here for me on installed system and on F16 livecd image.

Comment 3 Janina Sajka 2012-02-15 04:03:37 UTC
I started from a fresh .linphonerc and tweaked from there for soundcard, port,
and registration/authentication. That did the trick. All is good now!
Sorry for the noise, but I'm so accustomed to the old .linphonerc just working on upgrades.
Thanks for the quick assist. My work depends on linphonec and my Sennheiser headset.

Comment 4 nucleo 2012-02-15 21:01:46 UTC
I tested it before submitting to updates. It worked for me with old config but maybe there was no some options that probably changed in new release.
New release 3.5.1 maybe will be available soon. Can I ask you to test it when it will be submitted to upsates-testing?

Comment 5 Fedora End Of Life 2013-01-16 17:06:10 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16'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 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Fedora End Of Life 2013-02-13 19:29:48 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.


Note You need to log in before you can comment on or make changes to this bug.