<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hello,</p>
    <p>usually you should not loop requests locally, unless a very
      special case -- do you do the loop routing because of a need or
      just happens but you don't know why?</p>
    <p>Cheers,<br>
      Daniel<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 31.07.17 13:46, George
      Diamantopoulos wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAPcKEYORuL2j_iemF9oP9QSpFYpK+ZfMJCimTQz=pxHVXhFd3Q@mail.gmail.com">
      <div dir="ltr">
        <div>Hello all,<br>
          <br>
          I have been toying with kamailio lately, and I thought I had
          gotten to the point where I had a mostly working (tm)
          prototype. I gave it a test drive with some real calls,
          however, and an issue manifested at least once, where homer
          received packets originating from the kamailio host, and whose
          destination was also the kamailio host.<br>
          <br>
          The dialog this manifested in is a generally problematic one,
          with many retransmissions occurring because of slow database
          access (I haven't implemented htable caching yet). No packet
          capture over the network is actually taking place, I'm copying
          everything to homer with "trace_mode"set to 1.<br>
          <br>
          Homer shows these messages like in the screenshot: <a
            href="https://imagebin.ca/v/3VGJAmovRBmo"
            moz-do-not-send="true">https://imagebin.ca/v/3VGJAmovRBmo</a>.
          Here's an example of a packet:<br>
          <br>
          <br>
          <div style="margin-left:40px">2017-07-28 14:32:29 +0300 : <a
              href="http://2.3.4.5:5060" moz-do-not-send="true">2.3.4.5:5060</a>
            -> <a href="http://2.3.4.5:5060" moz-do-not-send="true">2.3.4.5:5060</a><br>
            INVITE <a
              href="mailto:sip%3A1234567890@kamailio-server.org"
              moz-do-not-send="true">sip:1234567890@kamailio-server.org</a>
            SIP/2.0<br>
            Record-Route: <a class="moz-txt-link-rfc2396E" href="sip:2.3.4.5;lr;ftag=as491cec82"><sip:2.3.4.5;lr;ftag=as491cec82></a><br>
            Via: SIP/2.0/UDP
            2.3.4.5;branch=z9hG4bK0cf.07799e3eb71f33a9ef91178ac760ebd2.0<br>
            Via: SIP/2.0/UDP
2.3.4.5;branch=z9hG4bKsr-BnCVyrWoUladI14pU7Pry-Pzy-ONy-VSQ74NU7HzeYazq2nFU2Oc5FIWiGIKq-HXex1oONpam-C6IrIXkr4FQxZRh7sM<br>
            Max-Forwards: 69<br>
            From: <<a href="http://sip:subscriber@5.4.3.2:5061"
              moz-do-not-send="true">sip:subscriber@5.4.3.2:5061</a>>;tag=as491cec82<br>
            To: <<a
              href="mailto:sip%3A1234567890@kamailio-server.org"
              moz-do-not-send="true">sip:1234567890@kamailio-server.org</a>><br>
            Contact:
<a class="moz-txt-link-rfc2396E" href="sip:2.3.4.5;line=sr-eNC05xhKefQnON1EglFrOkF0OfpzV2s9UzM9UXMNQXMn5-B0Q-s*"><sip:2.3.4.5;line=sr-eNC05xhKefQnON1EglFrOkF0OfpzV2s9UzM9UXMNQXMn5-B0Q-s*></a><br>
            Call-ID: <a
              href="http://4e5d22c3369704b97d866c8d0f3798f8@192.168.201.2:5061"
              moz-do-not-send="true">4e5d22c3369704b97d866c8d0f3798f8@192.168.201.2:5061</a><br>
            CSeq: 103 INVITE<br>
            User-Agent: Asterisk PBX 11.13.1~dfsg-2~bpo70+1<br>
            Date: Fri, 28 Jul 2017 11:32:24 GMT<br>
            Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE,
            NOTIFY, INFO, PUBLISH, MESSAGE<br>
            Supported: replaces, timer<br>
            Remote-Party-ID: "9876543210" <<a
              href="mailto:sip%3A9876543210@192.168.201.2"
              moz-do-not-send="true">sip:9876543210@192.168.201.2</a>>;party=calling;privacy=off;screen=yes<br>
            Content-Type: application/sdp<br>
            Content-Length: 500<br>
            <br>
            v=0<br>
            o=root 242468242 242468243 IN IP4 172.17.130.13<br>
            s=Asterisk PBX 11.13.1~dfsg-2~bpo70+1<br>
            c=IN IP4 172.17.130.13<br>
            t=0 0<br>
            m=audio 59426 RTP/AVP 18 101<br>
            a=rtpmap:18 G729/8000<br>
            a=fmtp:18 annexb=no<br>
            a=rtpmap:101 telephone-event/8000<br>
            a=fmtp:101 0-16<br>
            a=ptime:50<br>
            a=sendrecv<br>
            a=rtcp:59427<br>
            a=ice-ufrag:hffIoy6x<br>
            a=ice-pwd:nXB8ip7Qz8ZG5yyZRr97kGJbej<br>
            a=candidate:igct4zWHEzhGCjWc 1 UDP 2130706431 172.17.130.13
            59426 typ host<br>
            a=candidate:igct4zWHEzhGCjWc 2 UDP 2130706430 172.17.130.13
            59427 typ host<br>
          </div>
          <br>
        </div>
        Can something like this be triggered by misconfiguration in the
        routing scripts? Should it worry me and should I dig into it
        more? Could it be a bug of the siptrace module and nothing bad
        actually took place? I'm not sure where to start with this, so
        any input would be greatly appreciated. Thanks!<br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Kamailio (SER) - Users Mailing List
<a class="moz-txt-link-abbreviated" href="mailto:sr-users@lists.kamailio.org">sr-users@lists.kamailio.org</a>
<a class="moz-txt-link-freetext" href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users</a>
</pre>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 
Daniel-Constantin Mierla
<a class="moz-txt-link-abbreviated" href="http://www.twitter.com/miconda">www.twitter.com/miconda</a> -- <a class="moz-txt-link-abbreviated" href="http://www.linkedin.com/in/miconda">www.linkedin.com/in/miconda</a>
Kamailio Advanced Training - <a class="moz-txt-link-abbreviated" href="http://www.asipto.com">www.asipto.com</a>
Kamailio World Conference - <a class="moz-txt-link-abbreviated" href="http://www.kamailioworld.com">www.kamailioworld.com</a></pre>
  </body>
</html>