How to add Peer Connection constraints other than iceServers using quickconnect

[warrenjmcdonald]

Hi,

to avoid a range of connection difficulties introduced by IPv6 candidates from Chrome 42 onwards, we want to add the constraint which disables IPv6 candidates in WebRTC in the peerconnection constraints. At a low level with a peerconnection configuration object, we would just include
googIPv6: "false"

It is not obvious from the examples or our usage to-date, if any valid constraint other than iceServers can be handed into quickconnect or exactly how.

.

[silviapfeiffer]

The peerconnection constraints are all handed through to the RTCPeerConnection constructor API of the browser. It's done here: https://github.com/rtc-io/rtc-tools/blob/master/index.js . So, you should just be able to add the googIPv6 parameter as you would to a RTCPeerConnection constraint in the same way that you do iceServers. Might be worth adding an example though.

[DamonOehlman]

@warrenjmcdonald my understanding is that you managed to get this to work, but it took a slight variation to get it to go. So it sounds like it's probably worth us documenting or potentially making simpler - any suggestions?

[warrenjmcdonald]

@DamonOehlman sorry for delay. I have been off work for a few weeks

The additional quickconnect config option required was

constraints: {"optional": [ {'googIPv6': 'false'} ] }

I think updating the docs to say that a "constraints:" option is required, and that it must contains a valid RTCConstraints object. That would more specific and less confusing. Indicating what the options preference order is would also be good. This would clarify if the constraints: object values override defaults already within the code, or only add to those etc.