XSF Discussion - 2023-08-31

  1. kurisu

    https://xmpp.org/extensions/xep-0167.html#sdp says `<description xmlns='urn:xmpp:jingle:apps:rtp:1' media='audio'> <payload-type id="13" name="CN"/> </description>` would be mapped to `m=audio 9999 RTP/AVP 13` Where does 9999 come from?

  2. kurisu

    the only place where jingle xml seems to mention ports is in `<candidate/>`, but that does to `a=candidate ...`

  3. singpolyma

    If you find an sdp spec does it say what that number (the 9999) means?

  4. kurisu

    it's supposed to be "port"

  5. kurisu

    m=<media> <port> <proto> <fmt>

  6. singpolyma

    As in udp port? Because that doesn't make any sense they all go over the same negotiated-by-ice port

  7. singpolyma

    Maybe it's historical and unused?

  8. kurisu

    yeah it doesn't make any sense, that's why im wondering

  9. kurisu

    then further in the XEP it specifies as seemingly random value again <description xmlns='urn:xmpp:jingle:apps:rtp:1' media='video'> <payload-type id='98' name='theora' clockrate='90000'> <parameter name='height' value='600'/> <parameter name='width' value='800'/> <parameter name='delivery-method' value='inline'/> <parameter name='configuration' value='somebase16string'/> <parameter name='sampling' value='YCbCr-4:2:2'/> </payload-type> </description> m=video 49170 RTP/AVP 98 ...

  10. kurisu

    I would assume it's unused if the xep at least specified 9999 consistently

  11. singpolyma


  12. singpolyma

    You could check what conversations does. Does it use these numbers or something else?

  13. kurisu

    It hardcodes it to 9. Apparently unused in practice. If so, it would help if the XEP was more explicit about it.