I use Gizmo service with Google Voice. Twinkle is my benchmark SIP client, since I've found it to be very reliable compared to other clients available in the Ubuntu repos, especially "on the go" connected to random NATed wireless access points. I would like to use Telepathy/Farsight/Empathy for SIP calls since it integrates well with the Gnome desktop and unifies my realtime communications. In previous releases SIP registration and call connection were broken, but now these issues are resolved. Unfortunately, audio during calls is garbled (syllables seem to appear out of order, drop etc), while in Twinkle with the exact same setup, audio is solid. I've tested on a variety of networks, including both fast, public IP connections and behind NAT, with the same results: Twinkle voice quality is solid, Empathy voice quality is unusably glitchy. The empathy log and twinkle log both show the codec negotiated as PCMU/A. Since this is a quality issue, not one that is easily traced, I would suggest other interested users test with both Empathy/sofiasip and Twinkle (or other solid client) and post results.
btw, I'm using telepathy-sofiasip 0.6.2-1 on Ubuntu Lucid downstream bug: https://bugs.launchpad.net/ubuntu/+source/telepathy-sofiasip/+bug/578009
Sounds like an issue for Farsight.
Maybe twinkle has a dynamic jitterbuffer (we don't yet) or something like that. Can you make a tcpdump of a call in a situation where twinkle sounds fine and we don't ?
I can confirm Erics bug. My sip works perfectly with ekiga ( not a ekiga.net account), but with empathy/telepathy the sound is "garbled"
Can someone make a tcpdump when the problem appears ?
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/farstream/farstream/issues/10.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.