This all looks quite normal. "Message is not STUN" means that it's probably data and we are going to deliver it upward.
Please turn on the logging for mediapipeline as well, i.e., "mediapipeline:9" -Ekr On Fri, Oct 25, 2013 at 3:02 AM, <[email protected]> wrote: > Thanks for help, but we've faced a new problem. > Now DTLS handshake is done successfully, but we can't get audio in browser. > We see SRTP packets in Wireshark, however in FF log we have this: > 8552[260f530]: Flow[4372791e4e34780c:1,rtp(none)]; Layer[ice]: > PacketReceived(4372791e4e34780c/stream1/audio,1,252) > 8552[260f530]: Flow[4372791e4e34780c:1,rtp(none)]; Layer[dtls]: > PacketReceived(252) > 8552[260f530]: Flow[4372791e4e34780c:1,rtp(none)]; Layer[dtls]: Would have > blocked > 8552[260f530]: Flow[4372791e4e34780c:1,rtp(none)]; Layer[ice]: > PacketReceived(4372791e4e34780c/stream1/audio,1,252) > 8552[260f530]: Flow[4372791e4e34780c:1,rtp(none)]; Layer[dtls]: > PacketReceived(252) > 8552[260f530]: Flow[4372791e4e34780c:1,rtp(none)]; Layer[dtls]: Would have > blocked > > and a lot of messages like this: > > (ice/DEBUG) ICE(PC:4372791e4e34780c): Message is not STUN > (ice/DEBUG) ICE-PEER(PC:4372791e4e34780c:default): Delivering data > (ice/DEBUG) ICE(PC:4372791e4e34780c): Socket ready to read > (ice/DEBUG) ICE(PC:4372791e4e34780c): Read 252 bytes > (ice/DEBUG) ICE(PC:4372791e4e34780c): Message is not STUN > (ice/DEBUG) ICE-PEER(PC:4372791e4e34780c:default): Delivering data > (ice/DEBUG) ICE(PC:4372791e4e34780c): Socket ready to read > (ice/DEBUG) ICE(PC:4372791e4e34780c): Read 252 bytes > (ice/DEBUG) ICE(PC:4372791e4e34780c): Message is not STUN > > Before this line there is a message: > (ice/DEBUG) ICE-PEER(PC:4372791e4e34780c:default): stream > 4372791e4e34780c/stream1/audio state ACTIVE->COMPLETED > (ice/DEBUG) ICE-PEER(PC:4372791e4e34780c:default): 0 active streams > > May be this is the reason, why FF doesn't play audio stream? > Here you can take a look at full logs: > https://dl.dropboxusercontent.com/u/556956/ff/ff_log_2510.txt > https://dl.dropboxusercontent.com/u/556956/ff/ff_log_full2510.txt > > > That's good news. Firefox 26 should release on Dec 10th according to the > > > > release calendar - https://wiki.mozilla.org/RapidRelease/Calendar - so > all > > > > users should get this fix then. > > > > > > > > -EH > _______________________________________________ > 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
