Firefox Nightly (as of 06/04/13) and Chrome M25 Beta and later are interoperable, but currently require a small degree of adaptation on the part of the calling site.
Firefox and Chrome both prefix their interfaces and are likely to continue to do so until the standard is more finalised. The following table shows the relevant names:
Firefox and Chrome use different syntax for attaching media streams to video/audio tags.
Firefox uses either:
Firefox does not implement
Chrome does not yet do DTLS-SRTP by default whereas Firefox only does DTLS-SRTP. In order to get interoperability, you must supply Chrome with a PC constructor constraint to enable DTLS:
Finally, Firefox offers a data channel on every offer by default (this is a stopgap till the data channel APIs are complete). Chrome mishandles the data channel m-line. In order to suppress the Firefox data channel offer, you need to supply a mandatory media constraint to Firefox on CreateOffer. E.g.,
All of these issues are expected to be fixed in the near future.
Even in DTLS-SRTP mode, Chrome will not accept offers that do not contain
a=crypto lines. In order to call Chrome from Firefox you need to supply a dummy
a=crypto line for every m-line.
The code to do this is as follows:
IMPORTANT: Do not add an extra
a=crypto line to offers provided by
Chrome. This is only necessary on offers from Firefox, not on answers (but it
won’t hurt to add it). This issue is expected to be fixed in Chrome in the near