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 occurs; this is the only time, when both components speak directly with each other.

SEMS could do RTP-Relaying itself (without mediaproxy-ng), but is less efficient.

mediaproxy-ng works perfectly together with SEMS; but both components are independent from each other.

Kind regards, Carsten

2013/8/7 Juha Heinanen jh@tutpro.com:

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?

-- juha

---

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users