<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 12, 2015 at 5:52 PM, Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000"><span class="">
    <br>
    <div>On 12/01/15 11:14, aft wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr"><br>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Fri, Jan 9, 2015 at 12:37 AM,
            Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span> wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
              <div>
                <div><br>
                  On 01/01/15 08:29, aft wrote:<br>
                  > Hi,<br>
                  ><br>
                  > Is it possible to make the rtp stream appear
                  unidirectional?<br>
                  ><br>
                  > By that i mean,<br>
                  ><br>
                  > The rtp stream from client to proxy will go
                  through one rtpproxy and<br>
                  > proxy to client stream will go through another
                  rtpproxy instance?<br>
                  ><br>
                  > If not, is it possible to mimic something like
                  that by running<br>
                  > rtpproxy in bridge mode where both IPs in bridge
                  mode will be public IP?<br>
                  <br>
                </div>
              </div>
              in typical deployment rtpproxy needs to know from where to
              receive and<br>
              where to send. You may get that working if the caller and
              callee are on<br>
              public internet, if they are behind the nat, it will be
              hard.<br>
              <br>
              Using bridge mode should work. Also you can try to chain
              two rtpproxy<br>
              instances (with two kamailio proxy).<br>
            </blockquote>
            <div><br>
            </div>
            <div>How can i achieve this chaining?</div>
          </div>
        </div>
      </div>
    </blockquote></span>
    Install two kamailios with two rtpproxies and forward the messages
    between them. The second can be on the same system, different port
    (or even IP, if you want so).</div></blockquote><div><br></div><div>I'm still not clear how to do this.</div><div><br></div><div>INVITE is usually processed by invoking route[RTPPROXY]. Now if i want to forward it to another kamailio, what should i do?<br><br>Is the idea is like this :<br><br>INVITE--->kamailio1-----forward--->kamailio2--->route[RTPPROXY]--->Next Sip endpoint</div><div><br></div><div>Client <---- route[RTPPROXY]<--------kamailio1<------forward-----kamailio2<---- reply with SDP</div><div><br></div><div>If these scheme is correct, then i need to find how to do the "forward" appropriately?<br><br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div bgcolor="#FFFFFF" text="#000000"><span class="">
    Cheers,<br>
    Daniel<br>
    <pre cols="72">-- 
Daniel-Constantin Mierla
<a href="http://twitter.com/#!/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a></pre>
  </span></div>

</blockquote></div><br></div></div>