Thanks for replying.
What I am looking for is creating a self-contained component of signalling and media (let’s call it SMLIB) that can be used as part of other, higher-level, components.
As one hypothetical example SMLIB could be used to power a softphone that “talks webrtc”,
Or inside a conference server allowing both legacy SIP and WebRTC-browser clients.
Following your suggestion I should say that OpenSIPS is not a webrtc frontend, it is a medialess (deals only with SIP) component, although in more recent versions it brings WebSockets as a new SIP transport (adding to UDP, TCP, TLS).
Asterisk really supports WebRTC but I suppose I would need to rip-off the webrtc parts of its source code base to use in my Lib, that could be challenging.
Any other thoughts?
_______________________________________________ Visit our blog: http://blog.pjsip.org pjsip mailing list -- pjsip@xxxxxxxxxxxxxxx To unsubscribe send an email to pjsip-leave@xxxxxxxxxxxxxxx
