WebRTC data channels between older devices with chrome 38 support and new browsers.

[Robert Daniel Burlacu (SNP)]

I am currently working on an app that is designed to be used on TVs as a webapp. My current test environment is LG WebOS. In order to use the app on older TVs, such as WebOS 3.0, I am using adapter.js because WebOS 3.0 runs on top of the chrome 38 engine. LG with chrome 38 has WebRTC included in WebKit but does not have native function support. However, the adapter is working well and the WebRTC data channels are functioning perfectly on the same browsers. I am able to transfer files between my TV with chrome 38 and a sandbox windows chrome 38 without any issues, but when I try to establish a connection between chrome 38 and a newer chrome, such as chrome 109, it is not working. The webpage is the same, but the SDP is different.

I have tried to solve this problem by setting the following offerOptions:
```offerToReceiveVideo: false, offerToReceiveAudio: false, offerExtmapAllowMixed: false };```
This was done because the older version was providing a lot of SDP for audio and video which I do not need. I also removed extmap-allow-mixed because I hit the error:
```Failed to parse SessionDescription. a=extmap-allow-mixed Expects at least 2 fields.```
 And then:
```error Failed to parse SessionDescription. m=application 9 UDP/DTLS/SCTP webrtc-datachannel Invalid value: webrtc-datachannel.```
I have tried to modify the SDP to make it exactly how the browser accepts it, but I have not been successful. I am looking for ideas on where to start or how to solve this issue. Any suggestions would be greatly appreciated.