Hi All, I have tracked down our issue to a parameter in the Freeswitch Sofia module. In the sip profile it must have <param name="rtp-timer-name" value="soft"/>. The Freeswitch default value is none. This will cause non rtcp mux (firefox by default) to fail. After setting this timer Firefox worked as it should. The sample config that is provided by Freeswitch includes this variable and sets it to soft. I hope this helps.
On Friday, August 2, 2013 9:57:39 AM UTC-4, [email protected] wrote: > Hi Karl, > > > > I am having the exact same issue. However I think that the issue is on the > freeswitch side. I have been trying to debug it from freeswitch and think I > may be close in the switch_rtp.c file. > > > > On Wednesday, July 31, 2013 5:04:55 PM UTC-4, [email protected] wrote: > > > On Friday, July 5, 2013 7:27:07 AM UTC-5, Randell Jesup wrote: > > > > > > > On 7/5/2013 3:54 AM, Iwan Budi Kusnanto wrote: > > > > > > > > > > > > > > > On Fri, Jul 5, 2013 at 11:01 AM, Eric Rescorla <[email protected]> wrote: > > > > > > > > > > > > > > >> Also, please add "timestamp" to the list of NSPR_LOG_MODULES > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I attached firefox log with timestamp. Please wait for pcap files. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I found another error message on both logs. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > In FS (freeswitch) log, there is no message that it has received RTCP > > > > > > > > > > > > > > > packet. There is such message with chrome. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > There are also error messages regarding RTCP in FF (firefox) log: > > > > > > > > > > > > > > > - Error unprotecting SRTCP packet > > > > > > > > > > > > > > > - Couldn't write RTCP packet; SRTCP not set up yet > > > > > > > > > > > > > > > > > > > > > > > > > > > > The RTCP DTLS-SRTP flow is eventually ready ready (around 2.5 seconds > > > > > > > > > > > > > > after createAnswer()/etc), and we start trying to deliver them. But, as > > > > > > > > > > > > > > you note, they fail to be decoded, which implies either a bug in their > > > > > > > > > > > > > > DTLS-SRTP key extraction code (like using the SDES key by mistake), or > > > > > > > > > > > > > > incorrect settings for SRTP (auth tag size, etc). We are sending RTCP > > > > > > > > > > > > > > packets; the problems suggested above would likely mean they'd fail to > > > > > > > > > > > > > > decrypt ours, but they may not log it. > > > > > > > > > > > > > > > > > > > > > > > > > > > > Equally worrisome is that I don't see the rtp DTLS connection finish > > > > > > > > > > > > > > opening (no SSL handshake completed log message). > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > > Randell Jesup > > > > > > > > > > > > Randell, All: > > > > > > > > > > > > Was there a final resolution to this issue? I am seeing a similar issue > > and it seems that the DTLS client (Firefox) is never initiating the DTLS > > 'Client Hello' towards the DTLS server (Freeswitch). I am using sipML5 as > > the SOW for my WebRTC client. Any help would be appreciated. > > > > > > > > > > > > Karl _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
