<div dir="ltr">Hi Daniel,<div><br></div><div>My clients don't do anything when IP change occurs.From what I inspect, it is because of rtpproxy does not accept the 2nd IP change.</div><div>The the rtpproxy protocol document <a href="http://www.rtpproxy.org/wiki/RTPproxy/Protocol">http://www.rtpproxy.org/wiki/RTPproxy/Protocol</a>, the Update and Lookup command have [arg] parameters. </div>
<div><span style="color:rgb(0,0,0);font-family:monospace;font-size:13px">U[args] callid addr port from_tag [to_tag [notify_socket [notify_args]]]</span><br></div><div><span style="color:rgb(0,0,0);font-family:monospace;font-size:13px">L[args] callid addr port from_tag to_tag</span><span style="color:rgb(0,0,0);font-family:monospace;font-size:13px"><br>
</span></div><div><span style="color:rgb(0,0,0);font-family:monospace;font-size:13px"><br></span></div><div><font color="#000000" face="monospace">I see Kamailio often send Uc and Lc to rtpproxy. I still can't find out what these arg mean, but maybe it's the point</font></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Aug 14, 2013 at 3:31 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 text="#000000" bgcolor="#FFFFFF">
    Hello,<div><div class="h5"><br>
    <br>
    <div>On 8/13/13 5:56 AM, Khoa Pham wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr">
        <p>
          I have SIP proxy (Kamailio) works in conjunction with <a href="http://www.rtpproxy.org/" rel="nofollow" style="margin:0px;padding:0px;border:0px;vertical-align:baseline;background-color:transparent;color:rgb(74,107,130);text-decoration:none" target="_blank">rtpproxy</a> to
          support client communication. When SIP proxy sends command to
          rtpproxy to create new session, rtpproxy will create 2 ports
          (let's called them port1 and port2). rtpproxy has 1 listen
          interface</p>
        <p>
          Supposed A and B are 2 clients that use rtpproxy to relay RTP
          stream, and works fine.</p>
        <blockquote>
          <p style="margin:0px 0px 1em;padding:0px;border:0px;vertical-align:baseline;background-color:transparent;clear:both;word-wrap:break-word">A
            <---> port1 [<strong style="margin:0px;padding:0px;border:0px;vertical-align:baseline;background-color:transparent">rtpproxy</strong>]
            port2 <---> B</p>
        </blockquote>
        <p>
          Now that A loses his current network, and enter network2
          (imagine a network handover) to become A2. In this case, I see
          rtpproxy still works fine by relaying stream between A2 and B</p>
        <blockquote>
          <p style="margin:0px 0px 1em;padding:0px;border:0px;vertical-align:baseline;background-color:transparent;clear:both;word-wrap:break-word">A2
            <---> port1 [<strong style="margin:0px;padding:0px;border:0px;vertical-align:baseline;background-color:transparent">rtpproxy</strong>]
            port2 <---> B</p>
        </blockquote>
        <p>
          But when A2 lose his network2 and enters network3 to become
          A3, rtpproxy stills relay stream between A2 and B. It seems
          that A can change his network only once.</p>
        <blockquote>
          <p style="margin:0px 0px 1em;padding:0px;border:0px;vertical-align:baseline;background-color:transparent;clear:both;word-wrap:break-word">A2
            <---> port1 [<strong style="margin:0px;padding:0px;border:0px;vertical-align:baseline;background-color:transparent">rtpproxy</strong>]
            port2 <---> B</p>
          <p style="margin:0px 0px 1em;padding:0px;border:0px;vertical-align:baseline;background-color:transparent;clear:both;word-wrap:break-word">A3</p>
        </blockquote>
        <p>
          Why did the first handover succeed? How can I change rtpproxy
          behavior to support many handovers ?</p>
      </div>
    </blockquote></div></div>
    what I expect that happened between A and A2 is that the client
    application sent a re-INVITE with its new IP address. But then it
    didn't happen when going to A3. Rtpproxy itself can do nothing here.
    You should look at sip traffic to see what happens.<br>
    <br>
    Cheers,<br>
    Daniel<span class="HOEnZb"><font color="#888888"><br>
    <pre cols="72">-- 
Daniel-Constantin Mierla - <a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a>
<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>
  </font></span></div>

<br>_______________________________________________<br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list<br>
<a href="mailto:sr-users@lists.sip-router.org">sr-users@lists.sip-router.org</a><br>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><span style="color:rgb(0,0,0)">Khoa Pham</span><div>HCMC University of Science<br style="color:rgb(0,0,0)"><span style="color:rgb(0,0,0)"><a href="http://www.fantageek.com" target="_blank">www.fantageek.com</a></span><br>
</div></div>
</div>