1. Ubuntu -> MacOSX:
No audio or video call possible. The MacOSX client accepts the call, but
it keeps ringing (unfortunately no obvious logging entries).
If the *.log.* and *.pcap files in the ~/Library/Application
Support/SIP Communicator/log don't show the cause, could you please
create a full Wireshark dump of the whole session and a heap dump and
a thread dump when SIP Communicator/Jitsi keeps on ringing?
2. MacOSX -> Ubuntu:
Audio and video call are possible, but the video has a delay of about
2-3 seconds and the audio has a delay of about 1-2 seconds.
Too big a delay on the side of Mac OS X is not what I've experienced.
Is it possible that the delay occurs while or after it is received on
the side of Ubuntu?
does not occur with a windows jitsi client.
Is the Windows side the sender or the receiver?
As soon as i change the codecs to H263-1998 the delay gets better, but
the video itself has a bad quality.
The H.264 implementation in use should generally be more CPU intensive
than the H.263 one so no surprises the delay gets better after the
switch. And, of course, one cannot practically get any better than
H.264 so there are again no surprises that the video quality gets
worse after the switch.
Again a wider range of codecs would
Could you please list the codecs that you consider better in terms of
quality and performance than the current H.263 implementation? Is
their encoding and decoding supported by FFmpeg? If not, do they have
open-source implementations that we can use? Of course, contributing
their integration in SIP Communicator/Jitsi will speed up their
adoption in comparison to submitting a feature request
3. Bad error message with incompatible video codecs
Ubuntu codec settings: H264 only
MacOSX codec settings: H263-1998 only
Error while trying to call: "Call ended by remote side. Reason:
incompatible-parameters. Error: null"
The message should at least contain something like "no supported video
I guess an enhancement request may be submitted in our issue tracker.
Please be sure to attach patches that implement the requested
enhancement in order to make sure that your request is handled sooner
rather than later.
On Tue, Mar 15, 2011 at 2:01 PM, Ben <firstname.lastname@example.org> wrote: