<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
    <title></title>
  </head>
  <body bgcolor="#ffffff" text="#000000">
    <tt>Hi all,<br>
      <br>
      Following some debugging, it turned out that the "auto_bridging"
      option from the rtpproxy module does not properly function when
      doing parallel forking - this will be updated on the docs and code
      (a warning will be fired at startup).<br>
      <br>
      The solution is to manually do the bridging control, via the I and
      E flags when doing the offer and answer interaction with RTPProxy.<br>
      <br>
      Regards,</tt>
    <pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
    <br>
    On 07/16/2012 12:24 PM, Nick Altmann wrote:
    <blockquote
cite="mid:CAJOe1EOJPr0ao12kkKee=weykwgGv3k9_nWQDeLoZim4xqXmdw@mail.gmail.com"
      type="cite">I do it in the main route. Dump sent via private mail.
      <div><br clear="all">
        --<br>
        Nick<br>
        <br>
        <div class="gmail_quote">2012/7/16 Bogdan-Andrei Iancu <span
            dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:bogdan@opensips.org" target="_blank">bogdan@opensips.org</a>&gt;</span><br>
          <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
            0.8ex; border-left: 1px solid rgb(204, 204, 204);
            padding-left: 1ex;">
            <div bgcolor="#ffffff" text="#000000"> <tt>Maybe you are
                doing the RTPproxy stuff in branch route ? If not, could
                you post a SIP capture showing the incoming INVITE and
                the outgoing INVITEs ?<br>
                <br>
                Regards,<br>
              </tt>
              <div class="im">
                <pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre>
                <br>
              </div>
              <div>
                <div class="h5"> On 07/16/2012 12:07 PM, Nick Altmann
                  wrote:
                  <blockquote type="cite">Yes, it is.
                    <div><br clear="all">
                      --<br>
                      Nick<br>
                      <br>
                      <div class="gmail_quote">2012/7/16 Bogdan-Andrei
                        Iancu <span dir="ltr">&lt;<a
                            moz-do-not-send="true"
                            href="mailto:bogdan@opensips.org"
                            target="_blank">bogdan@opensips.org</a>&gt;</span><br>
                        <blockquote class="gmail_quote" style="margin:
                          0pt 0pt 0pt 0.8ex; border-left: 1px solid
                          rgb(204, 204, 204); padding-left: 1ex;">
                          <div bgcolor="#ffffff" text="#000000"> <tt>Hi
                              Nick,<br>
                              <br>
                              So, what you say is when doing parallel
                              forking (based on usrloc) and when in
                              request route, before relay, you do
                              rtpproxy_offer(), you get changed only the
                              INVITE for the first branch ?<br>
                              <br>
                              Regards,<br>
                              Bogdan<br>
                            </tt>
                            <pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre>
                            <div>
                              <div> <br>
                                On 07/16/2012 11:11 AM, Nick Altmann
                                wrote: </div>
                            </div>
                            <blockquote type="cite">
                              <div>
                                <div>Hello!
                                  <div><br>
                                  </div>
                                  <div>I call rtpproxy_offer("cof")
                                    before t_relay in my config. When
                                    INVITE passes through this rules, I
                                    see ip address of my rtpproxy in
                                    SDP. It's okay.</div>
                                  <div><br>
                                  </div>
                                  <div>Another situation:</div>
                                  <div>Client registered on opensips and
                                    have _two_ registrations with the
                                    same name.</div>
                                  <div>So, when I do t_relay of INVITE,
                                    it forks to _two_ INVITES. It's also
                                    okay.</div>
                                  <div><br>
                                  </div>
                                  <div>Before t_relay, I also
                                    call rtpproxy_offer("cof").</div>
                                  <div><br>
                                  </div>
                                  <div>But why in the first INVITE I see
                                    the ip address of my rtpproxy, but
                                    in the second INVITE I see original
                                    (source) ip address in SDP?</div>
                                  <div><br>
                                  </div>
                                  <div>--<br>
                                    Nick </div>
                                </div>
                              </div>
                              <pre><fieldset></fieldset>
_______________________________________________
Users mailing list
<a moz-do-not-send="true" href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a moz-do-not-send="true" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
                            </blockquote>
                          </div>
                        </blockquote>
                      </div>
                      <br>
                    </div>
                    <pre><fieldset></fieldset>
_______________________________________________
Users mailing list
<a moz-do-not-send="true" href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a moz-do-not-send="true" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
                  </blockquote>
                </div>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
  </body>
</html>