<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix"><tt>Hi, Ali!<br>
        <br>
        For the initial branch (in request route) are you using
        engage_rtpproxy()? If so, try to use rtpproxy_offer().<br>
        <br>
        Best regards,<br>
      </tt>
      <pre class="moz-signature" cols="72">Răzvan Crainea
OpenSIPS Solutions
<a class="moz-txt-link-abbreviated" href="http://www.opensips-solutions.com">www.opensips-solutions.com</a></pre>
      On 10/09/2014 12:06 AM, Ali Pey wrote:<br>
    </div>
    <blockquote
cite="mid:CA+q4kRK0Hzj-kfeHvmQ9Xf-d_kACpT7x0gTYZQsPWdOKp-0Dog@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">Hello Salman,</div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">Can you please elaborate on how you got
          this working? I have the same problem and can't get it to
          work.</div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">In failure route, I do:</div>
        <div class="gmail_extra">unforce_rtp_proxy()<br>
        </div>
        <div class="gmail_extra">Then when I have a new destination, I
          do:</div>
        <div class="gmail_extra">rtpproxy_offer("rocie");<br>
        </div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">However, I end up with messed up SDP,
          in my second invite. It doesn't remove the old IP addresses
          and only adds the IP addresses again:</div>
        <div class="gmail_extra">
          <div class="gmail_extra">o=Sonus_UAC 9216 20203 IN IP4
            10.160.11.16210.160.11.162a Capabilities </div>
          <div class="gmail_extra">c=IN IP4
            10.160.11.16210.160.11.162udio 2311822970AVP 0 8 100 </div>
        </div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">Please let me know how I can fix this.</div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">Thanks.</div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Mon, Jan 6, 2014 at 10:26 AM,
            Salman Zafar <span dir="ltr">&lt;<a moz-do-not-send="true"
                href="mailto:msalman212@gmail.com" target="_blank">msalman212@gmail.com</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
              <div dir="ltr">
                <div>
                  <div>Hi Razvan,<br>
                  </div>
                          I got it working without branching, after
                  banging head a lot I got to learn unforcing drops the
                  media ports for previous rtpproxy offer/answer and
                  after that directing the new flow though rtpproxy
                  flags,IP media works. I am able to traverse from
                  eternal to internal play media and then on failure do
                  external to external with media flowing between public
                  interfaces. Just wondering if you know this method or
                  certify.<br>
                </div>
                <div><br>
                </div>
              </div>
              <div class="gmail_extra">
                <div>
                  <div class="h5"><br>
                    <br>
                    <div class="gmail_quote">On Mon, Jan 6, 2014 at 4:35
                      PM, Răzvan Crainea <span dir="ltr">&lt;<a
                          moz-do-not-send="true"
                          href="mailto:razvan@opensips.org"
                          target="_blank">razvan@opensips.org</a>&gt;</span>
                      wrote:<br>
                      <blockquote class="gmail_quote" style="margin:0px
                        0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi,
                        Salman!<br>
                        <br>
                        The sockets used by RTPProxy are created when
                        the session is started (the first offer) and
                        cannot be updated afterwards. Therefore the only
                        solution I can see is to configure a per branch
                        scenario, as you mentioned.<br>
                        <br>
                        Best regards,<br>
                        <br>
                        Razvan Crainea<br>
                        OpenSIPS Core Developer<br>
                        <a moz-do-not-send="true"
href="https://contactmonkey.com/api/v1/tracker?cm_session=66f49ebf-f052-47c3-adee-bf8dd17afa5d&amp;cm_type=link&amp;cm_link=c1574c01-908b-4910-aaff-83f9f8f63efd&amp;cm_destination=http://www.opensips-solutions.com"
                          target="_blank">http://www.opensips-solutions.com</a>
                        <div>
                          <div><br>
                            <br>
                            On 12/30/2013 01:11 PM, Salman Zafar wrote:<br>
                          </div>
                        </div>
                        <blockquote class="gmail_quote"
                          style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
                          <div>
                            <div>
                              Hi,<br>
                                  I have a scenario of playing media at
                              a private-ip media server and<br>
                              send BUSY, next in failure route bridge
                              call to a public IP. (SIP to SIP).<br>
                              <br>
                              So the scenario is as follows:<br>
                              <br>
                              UA(Phone1) -&gt; OpenSIPS/RTpProxy(ei)
                              -&gt; Media-Server (Private IP) -&gt; BUSY<br>
                              -&gt; OpenSIPS(failure route) -&gt;
                              RTpProxy(ee) -&gt; lookup -&gt; (UA
                              Phone2)<br>
                              <br>
                              Now the problem is RtpProxy is being
                              offered (EI flags) in first case<br>
                              where routing to Media sever at private
                              IP, after failure it is again<br>
                              used with (EE flags), also in
                              corresponding replies.<br>
                              <br>
                              The second time RTpProxy does not effect
                              SDP c= and ports in a way to<br>
                              build media communication. SDP fix
                              directly does not effect rtp ports.<br>
                              <br>
                              Is there any way of using RtpProxy
                              differently in fail-over, or I have<br>
                              to go for rtpproxy per branch?.<br>
                              <br>
                              <br>
                              Thanks in advance.<br>
                              <br>
                              --<br>
                              Regards<br>
                              <br>
                              Salman<br>
                              <br>
                              <br>
                              <br>
                            </div>
                          </div>
                          _______________________________________________<br>
                          Users mailing list<br>
                          <a moz-do-not-send="true"
                            href="mailto:Users@lists.opensips.org"
                            target="_blank">Users@lists.opensips.org</a><br>
                          <a moz-do-not-send="true"
href="https://contactmonkey.com/api/v1/tracker?cm_session=66f49ebf-f052-47c3-adee-bf8dd17afa5d&amp;cm_type=link&amp;cm_link=0138242a-38a8-4160-8e04-9e778d8a3ff2&amp;cm_destination=http://lists.opensips.org/cgi-">http://lists.opensips.org/cgi-</a>bin/mailman/listinfo/users<br>
                          <br>
                        </blockquote>
                        <br>
                        _______________________________________________<br>
                        Users mailing list<br>
                        <a moz-do-not-send="true"
                          href="mailto:Users@lists.opensips.org"
                          target="_blank">Users@lists.opensips.org</a><br>
                        <a moz-do-not-send="true"
href="https://contactmonkey.com/api/v1/tracker?cm_session=66f49ebf-f052-47c3-adee-bf8dd17afa5d&amp;cm_type=link&amp;cm_link=39ab01b6-8245-48af-9ab5-ed7494a6765b&amp;cm_destination=http://lists.opensips.org/cgi-">http://lists.opensips.org/cgi-</a>bin/mailman/listinfo/users<br>
                      </blockquote>
                    </div>
                    <br>
                    <br clear="all">
                    <br>
                  </div>
                </div>
                <span class=""><font color="#888888">-- <br>
                    <div dir="ltr"><font face="'times new roman', serif">Regards</font>
                      <div><font face="'times new roman', serif"><br>
                        </font>
                        <div>
                          <pre cols="72"><font face="'times new roman', serif">M. Salman Zafar

VoIP Professional
</font>
</pre>
                        </div>
                      </div>
                    </div>
                  </font></span></div>
              <br>
              _______________________________________________<br>
              Users mailing list<br>
              <a moz-do-not-send="true"
                href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
              <a moz-do-not-send="true"
href="https://contactmonkey.com/api/v1/tracker?cm_session=66f49ebf-f052-47c3-adee-bf8dd17afa5d&amp;cm_type=link&amp;cm_link=8efee758-5809-4052-89d5-9190de57c58c&amp;cm_destination=http://lists.opensips.org/cgi-bin/mailman/listinfo/users"
                target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
              <br>
            </blockquote>
          </div>
          <br>
        </div>
        <img moz-do-not-send="true" class="cm-tracker"
src="https://contactmonkey.com/api/v1/tracker?cm_session=66f49ebf-f052-47c3-adee-bf8dd17afa5d&amp;cm_type=open&amp;cm_user_email=alipey@gmail.com"
          style="border:0; width:0px; height:0px;" height="0" width="0"><img
          moz-do-not-send="true" class="cm-tracker"
src="https://contactmonkey.com/api/v1/tracker?cm_session=66f49ebf-f052-47c3-adee-bf8dd17afa5d&amp;cm_type=open&amp;cm_user_email=alipey@gmail.com"
          style="border:0; width:0px; height:0px;" height="0" width="0"></div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>