After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 361326 - Speex 8K codec does not work
Speex 8K codec does not work
Status: RESOLVED INCOMPLETE
Product: ekiga
Classification: Applications
Component: general
GIT master
Other All
: Normal normal
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-11 03:07 UTC by Simon Wood
Modified: 2008-05-06 13:07 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
debug log (20.71 KB, text/plain)
2006-10-11 03:08 UTC, Simon Wood 		Details

Description Simon Wood 2006-10-11 03:07:56 UTC 
Please describe the problem:
Speex 8K codec does not work

Steps to reproduce:
Two machines (IP calls without registered accounts).

Caller has all codec enabled, callee has only one (Speex 8K).

When call is answered, it immediately terminates with 'Abnormal Termination' reported in comment field at bottom of main window.

Actual results:


Expected results:
Call to start/complete with Speex 8K codec.

Does this happen every time?
Yes. Both to i386 and PPC

Other information:
Comment 1 Simon Wood 2006-10-11 03:08:30 UTC 
Created attachment 74456 [details]
debug log
Comment 2 Damien Sandras 2006-11-01 18:28:00 UTC 
It has been reported upstream as bug #1588774.

See the openh323 bugtracker on http://www.sf.net/projects/openh323
Comment 3 Fabrice Alphonso 2007-02-11 11:09:40 UTC 
Seems to have been closed upstream on 20-11-2006 (FIXED by csoutheren).
Do we close here too ?
Comment 4 Damien Sandras 2007-02-11 14:11:52 UTC 
Perhaps somebody can first test that HEAD works with 2.0.3 and Speex NarrowBand/WideBand. If it works, then it can be closed.
Comment 5 Pavel Šefránek 2008-02-14 16:16:43 UTC 
Setting to NEEDINFO until someone provides relevant informations.
Comment 6 Snark 2008-05-06 13:07:34 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!