<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    Hey Steven,<br>
    <br>
    actually that was one of the first things I tried. I also upgraded
    my FS to the newest stable and tried it without success.<br>
    <br>
    BUT: Just to be save, I did the test again. And it worked as
    described. Maybe I had a typo or some.<br>
    <br>
    Thank you for your time.<br>
    <br>
    Once again the inbuilt greatness of FreeSWITCH prevails :)<br>
    <br>
    Greetz<br>
    Mitja<br>
    <br>
    <div class="moz-cite-prefix">Am 07.01.2014 19:02, schrieb Steven
      Ayre:<br>
    </div>
    <blockquote
cite="mid:%3CCAFiqYu=fkSGaGCjon7YTxU6gApOLwETzk6MWx2j1EUE8MmhRwA@mail.gmail.com%3E"
      type="cite">
      <div dir="ltr">See <a moz-do-not-send="true"
          href="http://wiki.freeswitch.org/wiki/NDLB">http://wiki.freeswitch.org/wiki/NDLB</a>
        <div><br>
        </div>
        <div>Try&nbsp;NDLB-connectile-dysfunction... it'll rewrite the
          contact header to where the REGISTER packet came from.</div>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On 7 January 2014 08:38, Mitja <span
            dir="ltr">&lt;<a moz-do-not-send="true"
              href="mailto:unau0@gmx.de" target="_blank">unau0@gmx.de</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">
            Hello there,<br>
            <br>
            Im trying to solve NAT related Problem which is caused by
            missbehaving<br>
            SIP phone.<br>
            Up Front: I searched the wiki and the web for all the NAT
            related<br>
            sites/mailling list. I think its a error of the invoxia
            IPhone docking<br>
            station (the missbehaving SIP phone), thus I did not open a
            jira for it.<br>
            <br>
            We have a freeswitch server with internet accessibility and
            a Phone<br>
            behind a natting router (Fritz!Box).<br>
            FreeSWITCH (1.2.3.4) &lt;-&gt; (10.11.12.13) NAT
            (192.168.0.1) &lt;-&gt;<br>
            (192.168.0.2) SIP Phone<br>
            <br>
            The Phone is able to register and initiate calls. But when
            someone else<br>
            to call that endpoint, its unreachable.<br>
            <br>
            I did some research and the problem seems to be that the
            phone registers<br>
            with a Contact containing the private IP Adress
            (192.168.0.2).<br>
            <br>
            <a class="moz-txt-link-abbreviated" href="mailto:freeswitch@1.2.3.4@internal">freeswitch@1.2.3.4@internal</a>&gt; sofia status profile
            internal reg<br>
            <br>
            Registrations:<br>
=================================================================================================<br>
            <br>
            Call-ID: &nbsp; &nbsp; &nbsp; &nbsp;aeac7f28-a6a0-4ba1-9d7c-30934924726d<br>
            User: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <a moz-do-not-send="true"
              href="mailto:270@1.2.3.4">270@1.2.3.4</a><br>
            Contact: &nbsp; &nbsp; &nbsp; &nbsp;"user" <a class="moz-txt-link-rfc2396E" href="sip:270@192.168.0.2:52767;ob">&lt;sip:270@192.168.0.2:52767;ob&gt;</a><br>
            Agent: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;invoxia-lemonvoice-v6.17.4<br>
            Status: &nbsp; &nbsp; &nbsp; &nbsp; Registered(UDP)(unknown) EXP(2014-01-06
            13:06:35)<br>
            EXPSECS(134)<br>
            Host: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; ippbx-border<br>
            IP: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 10.11.12.13<br>
            Port: &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; 52767<br>
            Auth-User: &nbsp; &nbsp; &nbsp;270<br>
            Auth-Realm: &nbsp; &nbsp; 1.2.3.4<br>
            MWI-Account: &nbsp; &nbsp;<a moz-do-not-send="true"
              href="mailto:270@1.2.3.4">270@1.2.3.4</a><br>
            <br>
            Other devices in the same Setup have their NAT IP [+Port]<br>
            (<a moz-do-not-send="true" href="http://10.11.12.13:52767"
              target="_blank">10.11.12.13:52767</a>) in their Contact
            Header which then works fine. In<br>
            this setup however the FreeSWITCH tries to send the INVITE
            Message to<br>
            192.168.0.2 and even when a NAT Table on the firewall
            manages to map it<br>
            to <a moz-do-not-send="true"
              href="http://10.11.12.13:52767" target="_blank">10.11.12.13:52767</a>
            the answer from 10.11.12.13 is discarded.<br>
            <br>
            Normally I use bridge with user/<a moz-do-not-send="true"
              href="mailto:270@1.2.3.4">270@1.2.3.4</a> with the
            dialstring<br>
"{presence_id=${dialed_user}@${dialed_domain}}${sofia_contact(internal/${dialed_user}@${dialed_domain})}".<br>
            I tried to force freeswitch to use the NAT IP address by
            calling bridge<br>
            with "sofia/internal/<a class="moz-txt-link-freetext" href="sip:270@10.11.12.13:52767;ob">sip:270@10.11.12.13:52767;ob</a>" which
            worked fine.<br>
            The IP address is of course not static but if I would be
            able to extract<br>
            the IP information which is stored in sofia registry (see
            above) I could<br>
            arrange my dialplan in a way that would fix that phones
            missbehaviour.<br>
            <br>
            So after all that describing text (sorry for that), heres my
            question:<br>
            Is there a way (an API or Dialplan command) to get the IP
            Information<br>
            which is stored the sofia registry.<br>
            <br>
            Thanks in advance<br>
            <br>
            Regards,<br>
            Mitja<br>
            <br>
            <br>
            <br>
            <br>
_________________________________________________________________________<br>
            Professional FreeSWITCH Consulting Services:<br>
            <a moz-do-not-send="true"
              href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
            <a moz-do-not-send="true"
              href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
            <br>
            FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>
            <a moz-do-not-send="true" href="http://www.cudatel.com"
              target="_blank">http://www.cudatel.com</a><br>
            <br>
            Official FreeSWITCH Sites<br>
            <a moz-do-not-send="true" href="http://www.freeswitch.org"
              target="_blank">http://www.freeswitch.org</a><br>
            <a moz-do-not-send="true" href="http://wiki.freeswitch.org"
              target="_blank">http://wiki.freeswitch.org</a><br>
            <a moz-do-not-send="true" href="http://www.cluecon.com"
              target="_blank">http://www.cluecon.com</a><br>
            <br>
            FreeSWITCH-users mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
            <a moz-do-not-send="true"
              href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users"
              target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
            UNSUBSCRIBE:<a moz-do-not-send="true"
              href="http://lists.freeswitch.org/mailman/options/freeswitch-users"
              target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
            <a moz-do-not-send="true" href="http://www.freeswitch.org"
              target="_blank">http://www.freeswitch.org</a><br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>