Actually, mediaproxy-ng plays no role in an SEMS SBC installation.
Both work pretty independent from each other: mediaproxy-ng is
triggered from Kamailio and SEMS as a B2BUA is triggered using bare
SIP (most likely also from Kamailio). mediaproxy-ng will notify SEMS
directly, if an RTP-Timeout occu
Carsten Bock wrote:
currently mediaproxy-ng only does timeout notifications only towards a
SEMS-SBC, not towards Kamailio. :-(
what role does mediaproxy-ng play in sems sbc installation? is
mediaproxy-ng used because sems does not support RTP/SAVPF or are there
some other use cases as well?
Hi Camille,
currently mediaproxy-ng only does timeout notifications only towards a
SEMS-SBC, not towards Kamailio. :-(
Adding support for notificating Kamailio on RTP-Timeout could probably
be added as well, but is not yet available.
Kind regards,
Carsten
2013/8/6 Camille Oudot :
> Hi Carsten,
>
Hi Carsten,
Thanks for the response,
> i wrote the patch quite long ago (2years+?). Back then, i posted the
> patch both on the rtpproxy-devel list and i even asked, if there was a
> tracker for patches; but i never ever received ANY reply... :-(
Ok, I've successfully applied it on an older vers
Hi Camille,
i wrote the patch quite long ago (2years+?). Back then, i posted the
patch both on the rtpproxy-devel list and i even asked, if there was a
tracker for patches; but i never ever received ANY reply... :-(
Since then, i never worked on that patch again and i replaced almost
every install
Hi All,
do someone know how to apply the rtpproxy patch
(modules/rtpproxy/test/rtpproxy.patch) on the rtpproxy server source
code? The notifications on media inactivity is done through
kamailio's XMLRPC interface, and this patch is needed by the rtpproxy
server to do so.
I fetched the code from
