<div dir="ltr">sorry,I have not expressed clearly.<div><br><div>kamailio will recive two REGISTER at a time.In first 200 OK to REGISTER, Server will tell Linphone the Linphone Nat Ip and Port.</div><div>like this:</div><div>Via:SIP/2.0/TCP 30.9.2.1:50691;received=42.1.7.1;alias;branch=z9hG4bK.kmhC2L9Rf;rport=33746</div><div>and Linphone will know it's outside nat Ip and port, Linphone while use this Ip and Port in second REGISTER.</div><div>like this:</div><div>REGSITER </div><div>Contact:<sip: 42.1.7.1:33746;transport=tcp></div><div><br></div><div>So kamailio server know Linphone's nated ip and port and save in DB(contact field).</div><div><br></div><div><br></div><div>my question is <span style="font-size:14px">KA_</span><span style="font-size:14px">EDGE receive sip from </span><span style="font-size:14px">KA_</span><span style="font-size:14px">REGISTER already have right nat ip and port like</span></div><div><span style="font-size:14px">INVITE 123456@</span>42.1.7.1:33746;transport=tcp  SIP/2.0</div><div>but <span style="font-size:14px">KA_</span><span style="font-size:14px">EDGE do not send this sip msg to </span><a href="http://42.1.7.1:33746">42.1.7.1:33746</a>, it send to another nat ip and port(other Linphone's ip and port behind same NAT layer)</div>







<div><div><br></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-03-14 21:42 GMT+08:00 Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    Indeed, the ports are different, that's why adding received is
    important in this situation.<br>
    <br>
    While local ip and local port are in most of the cases also unique
    for devices behind a nat router, it is not 100% true, because there
    can be many layers of NATs, which can result in seeing same local
    ip/port for devices.<br>
    <br>
    Cheers,<br>
    Daniel<div><div class="h5"><br>
    <br>
    <div>On 14/03/16 13:06, 张顺通 wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr"><span style="font-size:14px">source IP  is same,
           But port is different。</span><br>
        <div><span style="font-size:14px">like INVITE
            <a>sip:Linphone_nat_Ip:Linphone_nat_port;tcp</a>;</span></div>
        <div><span style="font-size:14px"><br>
          </span></div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">2016-03-14 18:26 GMT+08:00
          Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com" target="_blank"></a><a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span>:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div bgcolor="#FFFFFF" text="#000000"> Adding received
              information to Path helps to identify properly the
              connection to be used. Because both devices are behind the
              same NAT, practically they show the same source IP when
              they send traffic to server.<br>
              <br>
              Cheers,<br>
              Daniel
              <div>
                <div><br>
                  <br>
                  <div>On 14/03/16 04:05, 张顺通 wrote:<br>
                  </div>
                  <blockquote type="cite">
                    <div dir="ltr"><span style="font-size:14px">KA_</span><span style="font-size:14px">EDGE have two IP,external
                        public IP and internal IP.</span><br>
                      <div><span style="font-size:14px">I
                          add modparam("path", "use_received", 1)  and
                          replace add_path() to add_path_received() in
                          edge server.</span></div>
                      <div><span style="font-size:14px">add modparam("registrar",

                          "path_use_received", 1) in </span><span style="font-size:14px">KA_</span><span style="font-size:14px">REGISTER server.</span></div>
                      <div><span style="font-size:14px"><br>
                        </span></div>
                      <div><span style="font-size:14px">DB path
                          info <<a>sip:aD15fXXXXXXXXXXXXeEpfqRY=@</a><a href="http://10.10.10.11" target="_blank">10.10.10.11</a>;lr;ob>

                          --> <sip:</span><span style="font-size:14px">10.10.10.11</span><span style="font-size:14px">;lr;received=<a></a><a>sip:42.129.1.1:43640%3Btransport%3Dtcp</a>></span></div>
                      <div><span style="font-size:14px"><br>
                        </span></div>
                      <div><span style="font-size:14px">This kind of
                          situation very little,It is not easy to
                          reappear.</span><br>
                      </div>
                      <div><span style="font-size:14px">Can you tell me
                          why this </span><span style="font-size:14px">situation
                          happen? and Why this change can solve the
                          problem?</span></div>
                      <div><br>
                      </div>
                      <div>Thanks for Your Time.<br>
                      </div>
                      <div><span style="font-size:14px"><br>
                        </span></div>
                      <div><span style="font-size:14px"><br>
                        </span></div>
                    </div>
                    <div class="gmail_extra"><br>
                      <div class="gmail_quote">2016-03-09 22:37
                        GMT+08:00 Daniel Tryba <span dir="ltr"><<a href="mailto:d.tryba@pocos.nl" target="_blank"></a><a href="mailto:d.tryba@pocos.nl" target="_blank">d.tryba@pocos.nl</a>></span>:<br>
                        <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Wed, Mar 09,
                            2016 at 10:05:11PM +0800, 张顺通 wrote:<br>
                            > Yes,Use Path in DB. like <<a></a><a>sip:XXxXXXXXXXXXX/ogxZg=@</a><a href="http://10.10.232.29" rel="noreferrer" target="_blank">10.10.232.29</a>;lr;ob><br>
                            > KA_REGISTER wile the path info in DB.<br>
                            <br>
                          </span>Should not be a problem if you use the
                          use_received options in<br>
                          <a href="http://kamailio.org/docs/modules/stable/modules/path.html#idp135216" rel="noreferrer" target="_blank">http://kamailio.org/docs/modules/stable/modules/path.html#idp135216</a><br>
                          and<br>
                          <a href="http://kamailio.org/docs/modules/stable/modules/registrar.html#registrar.p.path_use_received" rel="noreferrer" target="_blank">http://kamailio.org/docs/modules/stable/modules/registrar.html#registrar.p.path_use_received</a><br>
                          <br>
                          (and actually add the source as received on
                          the kamailio edge server).<br>
                          <div>
                            <div><br>
_______________________________________________<br>
                              SIP Express Router (SER) and Kamailio
                              (OpenSER) - sr-users mailing list<br>
                              <a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
                              <a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
                            </div>
                          </div>
                        </blockquote>
                      </div>
                      <br>
                    </div>
                    <br>
                    <fieldset></fieldset>
                    <br>
                    <pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<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>
</pre>
                  </blockquote>
                  <br>
                </div>
              </div>
              <span>
                <pre cols="72">-- 
Daniel-Constantin Mierla
<a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a>
<a href="http://twitter.com/#%21/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>
Kamailio World Conference, Berlin, May 18-20, 2016 - <a href="http://www.kamailioworld.com" target="_blank">http://www.kamailioworld.com</a></pre>
              </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" target="_blank">sr-users@lists.sip-router.org</a><br>
            <a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" rel="noreferrer" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <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>
Kamailio World Conference, Berlin, May 18-20, 2016 - <a href="http://www.kamailioworld.com" target="_blank">http://www.kamailioworld.com</a></pre>
  </div></div></div>

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