<div dir="ltr">I think you mean the SIP messages exchanged. If any more info needed i can send.<br>1.1.1.1 == UA<br>2.2.2.2 == Opensips<br>999999999999 == number dialed<br><br><br>1.1.1.1 ===============&gt; 2.2.2.2<br><br>INVITE sip:999999999999@2.2.2.2:9092;transport=udp SIP/2.0<br>Via: SIP/2.0/UDP 1.1.1.1:60704;rport;branch=z9hG4bKac2a2c3c77b3c043ad3d85118<br>Max-Forwards: 70<br>From: &lt;<a href="mailto:sip%3A5656@2.2.2.2">sip:5656@2.2.2.2</a>&gt;;tag=f2e3a2e6ed6a6f4399443d7e0347f20d<br>To: &lt;<a href="mailto:sip%3A999999999999@2.2.2.2">sip:999999999999@2.2.2.2</a>&gt;<br>Contact: &lt;<a href="http://sip:5656@1.1.1.1:60704">sip:5656@1.1.1.1:60704</a>&gt;<br>Call-ID: b94573d6d94ee54ca945310968a14065<br>CSeq: 3 INVITE<br>User-Agent: Softphone Dialer v 4.02<br>Allow: INVITE, ACK, CANCEL, BYE, OPTIONS<br>Content-Type: application/sdp<br>Content-Length: 181<br><br>v=0<br>o=- 1435147412 1435147412 IN IP4 1.1.1.1<br>s= Media Server<br>c=IN IP4 1.1.1.1<br>t=0 0<br>m=audio 60705 RTP/AVP 18<br>a=rtpmap:18 G729/8000<br>a=ptime:20<br>a=fmtp:18 annexb=no<br><br>2.2.2.2 ===============&gt; 1.1.1.1<br><br>SIP/2.0 407 Proxy Authentication Required<br>Via: SIP/2.0/UDP 1.1.1.1:60704;received=1.1.1.1;rport=60704;branch=z9hG4bKac2a2c3c77b3c043ad3d85118<br>From: &lt;<a href="mailto:sip%3A5656@2.2.2.2">sip:5656@2.2.2.2</a>&gt;;tag=f2e3a2e6ed6a6f4399443d7e0347f20d<br>To: &lt;<a href="mailto:sip%3A999999999999@2.2.2.2">sip:999999999999@2.2.2.2</a>&gt;;tag=aabd1841c260dd885edee5bb6208511c.bd84<br>Call-ID: b94573d6d94ee54ca945310968a14065<br>CSeq: 3 INVITE<br>Proxy-Authenticate: Digest realm=&quot;2.2.2.2&quot;, nonce=&quot;558a9cb600000113aa59d19d1ae0ae586b08ead15a79cc44&quot;<br>Server: opensips Proxy v4.20<br>Content-Length: 0<br><br>2.2.2.2 ===============&gt; 1.1.1.1<br><br>ACK sip:2.2.2.2:9092;transport=udp SIP/2.0<br>Via: SIP/2.0/UDP 1.1.1.1:60704;rport;branch=z9hG4bKac2a2c3c77b3c043ad3d85118<br>Max-Forwards: 70<br>From: &lt;<a href="mailto:sip%3A5656@2.2.2.2">sip:5656@2.2.2.2</a>&gt;;tag=f2e3a2e6ed6a6f4399443d7e0347f20d<br>To: &lt;<a href="mailto:sip%3A999999999999@2.2.2.2">sip:999999999999@2.2.2.2</a>&gt;<br>Call-ID: b94573d6d94ee54ca945310968a14065<br>CSeq: 3 ACK<br>Content-Length: 0<br><br>1.1.1.1 ===============&gt; 2.2.2.2<br><br>INVITE sip:999999999999@2.2.2.2:9092;transport=udp SIP/2.0<br>Via: SIP/2.0/UDP 1.1.1.1:60704;rport;branch=z9hG4bK43d3de0414c6ba469c30a9d43<br>Max-Forwards: 70<br>From: &lt;<a href="mailto:sip%3A5656@2.2.2.2">sip:5656@2.2.2.2</a>&gt;;tag=f2e3a2e6ed6a6f4399443d7e0347f20d<br>To: &lt;<a href="mailto:sip%3A999999999999@2.2.2.2">sip:999999999999@2.2.2.2</a>&gt;<br>Contact: &lt;<a href="http://sip:5656@1.1.1.1:60704">sip:5656@1.1.1.1:60704</a>&gt;<br>Call-ID: b94573d6d94ee54ca945310968a14065<br>CSeq: 4 INVITE<br>User-Agent: Softphone Dialer v 4.02<br>Proxy-Authorization: DIGEST username=&quot;5656&quot;, realm=&quot;2.2.2.2&quot;, nonce=&quot;558a9cb600000113aa59d19d1ae0ae586b08ead15a79cc44&quot;, uri=&quot;<a href="mailto:sip%3A999999999999@2.2.2.2">sip:999999999999@2.2.2.2</a>&quot;, response=&quot;a2741b5fd118bac802d467a7d405f4c4&quot;<br>Allow: INVITE, ACK, CANCEL, BYE, OPTIONS<br>Content-Type: application/sdp<br>Content-Length: 181<br><br>v=0<br>o=- 1435147412 1435147412 IN IP4 1.1.1.1<br>s= Media Server<br>c=IN IP4 1.1.1.1<br>t=0 0<br>m=audio 60705 RTP/AVP 18<br>a=rtpmap:18 G729/8000<br>a=ptime:20<br>a=fmtp:18 annexb=no<br><br>2.2.2.2 ===============&gt; 1.1.1.1<br><br>SIP/2.0 100 Giving a try<br>Via: SIP/2.0/UDP 1.1.1.1:60704;received=1.1.1.1;rport=60704;branch=z9hG4bK43d3de0414c6ba469c30a9d43<br>From: &lt;<a href="mailto:sip%3A5656@2.2.2.2">sip:5656@2.2.2.2</a>&gt;;tag=f2e3a2e6ed6a6f4399443d7e0347f20d<br>To: &lt;<a href="mailto:sip%3A999999999999@2.2.2.2">sip:999999999999@2.2.2.2</a>&gt;<br>Call-ID: b94573d6d94ee54ca945310968a14065<br>CSeq: 4 INVITE<br>Server: opensips Proxy v4.20<br>Content-Length: 0<br><br>2.2.2.2 ===============&gt; 1.1.1.1<br><br>SIP/2.0 183 Session Progress<br>Via: SIP/2.0/UDP 1.1.1.1:60704;received=1.1.1.1;rport=60704;branch=z9hG4bK43d3de0414c6ba469c30a9d43<br>From: &lt;<a href="mailto:sip%3A5656@2.2.2.2">sip:5656@2.2.2.2</a>&gt;;tag=f2e3a2e6ed6a6f4399443d7e0347f20d<br>To: &lt;<a href="mailto:sip%3A999999999999@2.2.2.2">sip:999999999999@2.2.2.2</a>&gt;;tag=r8HZU2gDavryg<br>Call-ID: b94573d6d94ee54ca945310968a14065<br>CSeq: 4 INVITE<br>Contact: &lt;sip:999999999999@2.2.2.2:9092;did=499.a0c0dd53&gt;<br>Accept: application/sdp<br>Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE<br>Supported: timer, path, replaces<br>Content-Type: application/sdp<br>Content-Disposition: session<br>Content-Length: 215<br>User-Agent: Bridge v4.20<br><br>v=0<br>o=FreeSWITCH 1435123396 1435123397 IN IP4 2.2.2.2<br>s=FreeSWITCH<br>c=IN IP4 2.2.2.2<br>t=0 0<br>m=audio 18344 RTP/AVP 18<br>a=rtpmap:18 G729/8000<br>a=fmtp:18 annexb=no<br>a=ptime:20<br>a=sendrecv<br>a=rtcp:18345<br><br>2.2.2.2 ===============&gt; 1.1.1.1<br><br>SIP/2.0 200 OK<br>Via: SIP/2.0/UDP 1.1.1.1:60704;received=1.1.1.1;rport=60704;branch=z9hG4bK43d3de0414c6ba469c30a9d43<br>From: &lt;<a href="mailto:sip%3A5656@2.2.2.2">sip:5656@2.2.2.2</a>&gt;;tag=f2e3a2e6ed6a6f4399443d7e0347f20d<br>To: &lt;<a href="mailto:sip%3A999999999999@2.2.2.2">sip:999999999999@2.2.2.2</a>&gt;;tag=r8HZU2gDavryg<br>Call-ID: b94573d6d94ee54ca945310968a14065<br>CSeq: 4 INVITE<br>Contact: &lt;sip:999999999999@2.2.2.2:9092;did=499.a0c0dd53&gt;<br>Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE<br>Supported: timer, path, replaces<br>Content-Type: application/sdp<br>Content-Length: 212<br>User-Agent: Bridge v4.20<br><br>v=0<br>o=FreeSWITCH 1108548551 1905294444 IN IP4 2.2.2.2<br>s=FreeSWITCH<br>c=IN IP4 2.2.2.2<br>t=0 0<br>m=audio 18364 RTP/AVP 18<br>a=rtpmap:18 G729/8000<br>a=fmtp:18 annexb=no<br>a=maxptime:20<br>a=sendrecv<br>a=rtcp:18365<br><br>1.1.1.1 ===============&gt; 2.2.2.2<br><br>ACK sip:2.2.2.2:9092;transport=udp SIP/2.0<br>Via: SIP/2.0/UDP 1.1.1.1:60704;rport;branch=z9hG4bK43d3de0414c6ba469c30a9d43<br>Max-Forwards: 70<br>From: &lt;<a href="mailto:sip%3A5656@2.2.2.2">sip:5656@2.2.2.2</a>&gt;;tag=f2e3a2e6ed6a6f4399443d7e0347f20d<br>To: &lt;<a href="mailto:sip%3A999999999999@2.2.2.2">sip:999999999999@2.2.2.2</a>&gt;<br>Call-ID: b94573d6d94ee54ca945310968a14065<br>CSeq: 4 ACK<br>Content-Length: 0<br><br><br>After that 200 OK is sent to 1.1.1.1 again and again and it sends ACK <br><br><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jun 30, 2015 at 1:36 PM, Vlad Paiu <span dir="ltr">&lt;<a href="mailto:vladpaiu@opensips.org" target="_blank">vladpaiu@opensips.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div bgcolor="#FFFFFF" text="#000000">
    Hello,<br>
    <br>
    Please post a trace of this.<br>
    <br>
    Best Regards,<br>
    <pre cols="72">Vlad Paiu
OpenSIPS Developer
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a> </pre><div><div class="h5">
    <div>On 25.06.2015 06:25, John Nash wrote:<br>
    </div>
    </div></div><blockquote type="cite"><div><div class="h5">
      <div dir="ltr">
        <div>
          <div>Let me add some more details which I noticed.<br>
            <br>
          </div>
          As i explained in previous post in the same subject, we
          receive ACK without to tag from one UA, since it will not
          match any dialog, I tried to route it to destination with
          topology_hiding but topology hiding used different branch tag
          than the 200 OK received (It only replaced .0 with .2). I
          think this is happening because I am also using drouting
          module and UAC which use branches.<br>
          <br>
        </div>
        I can post trace also if someone wants to have a look.<br>
        <div><br>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <div class="gmail_quote">On Wed, Jun 24, 2015 at 10:06 PM, John
          Nash <span dir="ltr">&lt;<a href="mailto:john.nash778@gmail.com" target="_blank">john.nash778@gmail.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div dir="ltr">
              <div>
                <div>I am using opensips 2.1 with topology_hiding
                  module. I have an issue only with one SIP endpoint.
                  This endpoint sends Ack message (after 200 OK to
                  Invite) without any to tag because of that it is not
                  matching with In dialog request section.<br>
                  <br>
                </div>
                Can a UA send ACK without to tag?...If yes any way I can
                match it with ongoing dialog?<span><font color="#888888"><br>
                    <br>
                  </font></span></div>
              <span><font color="#888888">John<br>
                </font></span></div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset></fieldset>
      <br>
      </div></div><pre>_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
    </blockquote>
    <br>
  </div>

<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>