Binary / text data transfer between bareSIP clients
Jim Bell
We're looking to transfer text or binary data along with audio & video between two bareSIP clients. More than a few bytes, but much less than the UDP MTU. A data conversation of sorts, with a message every few seconds.
Does such a mechanism already exist? Is anyone working on this?
If not, these approaches come to mind, with pros & cons:
Implement SDP's m=text or m=application.Pros:
- Close cohesion with audio & video. Timestamps for recording, etc.
- Leverage all transports available to audio & video, including SDP bundling.
Cons:
- Biggest potential impact to code base, cutting across many layers.
Pros:
- Possibly smaller impact to code base, more modular implementation.
- Leverages existing mechanisms.
Cons:
- Still seems like a big effort.
- Forces us to use WebRTC exclusively (not SIP).
Pros:
- Minimal impact on existing code.
Cons:
- Codecs or filtering would corrupt the data very easily.
Pros:
- Minimal impact to existing code.
Cons:
- Disconnected from audio & video streams.
Of course, the approach requiring the least effort, and leveraging existing mechanisms (already well tested) is most appealing. We can handle lost packets at the application layer.
Vitalii Orazov
Hello,
Jim Bell
Hello,may be the transfer of small data via DTMF is suitable for you?вторник, 26 сентября 2023 г. в 06:14:21 UTC+3, j...@jc-bell.com:
We're looking to transfer text or binary data along with audio & video between two bareSIP clients. More than a few bytes, but much less than the UDP MTU. A data conversation of sorts, with a message every few seconds.
Does such a mechanism already exist? Is anyone working on this?
...
