ef24d2050b
This is a feature of WebRTC that's [not standardized][1] and only supported by libwebrtc. Since there's no support in jingle for passing this capability from one peer to another, we're currently hard-coding this option into both the local candidate and also the remote candidate so they can use it. But I'm trying to call a user that isn't using WebRTC, and renomination is causing the call to stay in "connecting..." state for 10 or 20 seconds, sometimes longer, while both sides wait for the other to nominate something based on their individual beliefs about the standards they're using. Removing this seems to make connecting relatively instantaneous. If we want to reintroduce this feature, we should probably make a XEP so the peers can negotiate honestly about it, and only use it if both sides truely support the feature. [1]: https://datatracker.ietf.org/doc/html/draft-thatcher-ice-renomination-01 |
||
|---|---|---|
| .. | ||
| compat/java/eu/siacs/conversations | ||
| conversations | ||
| conversationsFree/java/eu/siacs/conversations/utils | ||
| conversationsPlaystore/java/eu/siacs/conversations/utils | ||
| free/java/eu/siacs/conversations/services | ||
| freeCompat/java/eu/siacs/conversations/ui/service | ||
| main | ||
| playstore | ||
| playstoreCompat | ||
| quicksy | ||
| quicksyFree/java/eu/siacs/conversations/utils | ||
| quicksyPlaystore/java/eu/siacs/conversations/utils | ||
| system/java/eu/siacs/conversations | ||