I'm a little confused about the setting you are describing. It sounds like you're terminating the call at your gateway, in which case you basically have two calls. If that's right, can you look at your gateway and determine what it's seeing as far as media?
In any case, if you send me the traces offline I can take a look. -Ekr On Fri, Sep 27, 2013 at 5:20 PM, Rajarshi Chaudhuri <[email protected]>wrote: > Hello - > > We use our own WebRTC Gateway - that acts for signaling, media relay and > also for transcoding if needed. Currently Chrome to Chrome call is working > fine thru our gateway. > > However, when FireFox in the picture and it initiates the call (to another > FF instance or Chorme) there are issues after the signaling is over. The > failure behavior is random - that sometimes audio is heard on the caller > side - but no video - and sometimes no media at all. On the callee side - > no media. > > However, when we make a call from Chrome thru our gateway to FF - things > work fine - audio/video in both sides are available. > > I first thought if it's a DTLS issue - but apparently not. We are using > openssl 1.0.1e in our gateway for DTLS. > > I have FF log for both bad case (when FF calls Chrome) and good case > (Chrome to FF). > > Any help would be greatly appreciated. > > For FF logging I used the following - > > NSPR_LOG_FILE=c:\tmp\log.txt > NSPR_LOG_MODULES=signaling:9,mtransport:9,mediapipeline:9 > R_LOG_LEVEL=9 > R_LOG_DESTINATION=stderr > R_LOG_VERBOSE=1 > > Thx > Rajarshi > _______________________________________________ > dev-media mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-media > _______________________________________________ dev-media mailing list [email protected] https://lists.mozilla.org/listinfo/dev-media
