A fix for this Jira is deemed to be mandatory for the 4.2 release.
Problem has nothing to do with the number of recipients.

Here is what is happening

1) CMC connects to Freeswitch conference with G722 codec. CMC has G722
first the SDP it sends so FS provides G722 in its response
2) FS internally sets its "read codec" to be L16 so that is can easily
mix the media from each participant
3) user presses the "Start my Video" button
4) CMC sends another SDP but this time BroadVoice 32 is the first audio
codec and G722 is the 6th codec. It also includes H263 video in the SDP
5) Freeswitch accepts Broadvoice 32 audio codec and rejects the video
codec (since FS doesn't have any video codecs enabled)

So at this point the codec has changed but the conference doesn't know
about it and continues to mix voice assumine L16 (hence the motor boat
Sound). 

To fix this (without a risky Freeswich code change) I would like to make
two changes in sipX_profile.xml

A) inbound-codec-negotiation = scrooge (was generous)
B) change the codec-prefs order to have G722 first

The first change tells Freeswitch to use its codec ordering instead of
the clients when trying to find the first matching codec.
For example, if the client sends A,B,C and Freeswitch has C,B,A then C
will be chosen. With 'generous' A would have been chosen.

The net result of this is that the codec will not change when the video
button is pressed. 
The second change (codec ordering) is too ensure G722 is chosen when the
client supports it. 

Btw .. Freeswitch does support video conferencing if a video codec is
loaded and enabled (a bit buggy at this point). It does this by
sending the video of the loudest speaker to all other participants. Have
not played with it much (just enough to know there is at least one bug).


Thoughts?

Peter 
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to