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 491316 - Incorrect handling of Speex packets
Incorrect handling of Speex packets
Status: RESOLVED NOTGNOME
Product: ekiga
Classification: Applications
Component: OPAL
2.0.x
Other All
: Normal normal
: ---
Assigned To: Ekiga maintainers
Ekiga maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-29 10:00 UTC by Jean-Marc Valin
Modified: 2008-04-03 07:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Jean-Marc Valin 2007-10-29 10:00:59 UTC 
Please describe the problem:
I've been writing a SIP VoIP application that is compatible with Ekiga. I've noticed that whenever I try sending Ekiga Speex wideband at 27.8 kbps, the sound becomes terrible and libspeex (as called by Ekiga) prints errors messages saying the packets are corrupted. This does not happen when I'm sending at 20.6 kbps. Seems like Ekiga expects that rate and mis-handles the rest. This is bad for compatibility -- especially considering that the SDP doesn't indicate a preferred rate.

Steps to reproduce:
1. Ekiga calls client XYZ, advertising all its codecs (SDP)
2. Client XYZ answers with SPEEX/16000
3. Client XYZ starts sending SPEEX/16000 at 27.8 kbps


Actual results:
Ekiga outputs garbled sound, prints error messages

Expected results:
Ekiga should just play the Speex packets, not matter what the bitrate is

Does this happen every time?
Yes

Other information:
Note: I'm the Speex author. I know for sure that the message I see from libspeex can only mean Ekiga is not handling the packets properly.
Comment 1 Damien Sandras 2008-04-02 19:25:37 UTC 
Bug reported to the OPAL bugtracker:
https://sourceforge.net/tracker/index.php?func=detail&aid=1932551&group_id=204472&atid=989748

Marking as NOTGNOME as it is an OPAL bug and it is put in their bugracker.
Comment 2 Damien Sandras 2008-04-03 07:30:26 UTC 
Please subscribe to notifications for the bug on the sourceforge.net bugtracker. More information is needed from you.