|Subject:||Re: [osip-dev] is ortp transport independent|
|Date:||Thu, 25 Feb 2016 22:17:44 +0100|
For my project, I (as antisip.com) use forked version of ortp and mediastreamer which I maintain and improve myself. I have renamed the project a-ortp and a-mediastreamer2: I guess you are refering to belledonne's original versions?
I can't give any info about belledonne's versions...
In my versions, srtp is still there but it's not a transport any more: more like a plugin. As in osip, there can be only one transport (responsible for sending/receiving): srtp is a module used before or after the "transport" layer. I also have a plugin for zrtp which I'm not using at all, bit if I remember correctly my code, it's a mediastreamer plugin that insert a "module" into a-ortp.
I want to use ORTP in my application. I just looked at examples. Ortp expects to take socket fd and call send/recv apis of socket internally in ortp code.
Due to some constraint, I will not be able to pass socket fd to ortp.
I want to know
1) Can we use ortp in transport independent way (how osip works), meaning I will pass a handle to ortp, while ortp wants to send data out, call my callback and pass back handle to me
2) I see support for srtp and zrtp etc are removed from ortp-25 (latest version), whereas these were there in ortp-23 version. Why these are removed, is there any particular reason why it was done?
osip-dev mailing list
|[Prev in Thread]||Current Thread||[Next in Thread]|