On 04/19/2012 06:21 PM, Klaus Darilion wrote:
+1
I would have needed this feature some time ago when I played around with
v4/v6 bridging
We're using this feature together with ngcp-mediaproxy-ng
(
http://deb.sipwise.com/spce/2.5/pool/main/n/ngcp-mediaproxy-ng/) since
SPCE v2.5.
The thing here is that to take full advantage of it, rtpproxy needs to
support it in more detail. It basically works fine because the call-id
will be "callid;viabranch", so the via-branch is considered part of the
call-id in rtpproxy, but if you do unforce_rtp_proxy() without a
via-branch, it won't find the call, so you need to use
unfoce_rtp_proxy("2") if you did rtpproxy_offer("1") or
rtpproxy_answer("2").
In ngcp_mediaproxy_ng, we whipe out all branches if no via-branch is
passed in unforce_rtp_proxy(). If the stock rtpproxy wants to take
advantage of that as well, it should check for a via-branch token in the
call-id also and act accordingly.
JFYI,
Andreas