Firefox is working on improving functionality with Telegram tracked in bug https://bugzilla.mozilla.org/show_bug.cgi?id=1903659 but could use changes in the Telegram code to assist with this endeavor.
There is an issue with id: +attribute.key which works on an extmap with no directionality specified such as a=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level it will properly convert the id to be 1. However if directionality is present such as you would see in Firefox 2/recvonly urn:ietf:params:rtp-hdrext:csrc-audio-level you end up with null for the id and send and SDP with a=extmap:null urn:ietf:params:rtp-hdrext:csrc-audio-level. This causes a parsing error in other browsers and the telegram app preventing the call from working.
Doing something likeid: +attribute.key.split('/', 1)[0],instead would resolve this issue.
Firefox is working on improving functionality with Telegram tracked in bug https://bugzilla.mozilla.org/show_bug.cgi?id=1903659 but could use changes in the Telegram code to assist with this endeavor.
tweb/src/lib/calls/helpers/parseSignalingData.ts
Line 43 in eb08384
There is an issue with
id: +attribute.keywhich works on an extmap with no directionality specified such asa=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-levelit will properly convert the id to be 1. However if directionality is present such as you would see in Firefox2/recvonly urn:ietf:params:rtp-hdrext:csrc-audio-levelyou end up with null for the id and send and SDP witha=extmap:null urn:ietf:params:rtp-hdrext:csrc-audio-level. This causes a parsing error in other browsers and the telegram app preventing the call from working.Doing something like
id: +attribute.key.split('/', 1)[0],instead would resolve this issue.