<div dir="ltr">Excellent!  Apparently I mis-read this part of the RFC.  Thanks.<div><br></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><div>- Jeff</div><div><br></div></div></div>
<br><br><div class="gmail_quote">On Mon, Mar 17, 2014 at 12:02 PM, Bogdan-Andrei Iancu <span dir="ltr">&lt;<a href="mailto:bogdan@opensips.org" target="_blank">bogdan@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">
    <div><tt>Hi Jeff,<br>
        <br>
        Alice expects just a higher cseq number, not an increment with 1
        or any step...just higher than the prev one :)<br>
        <br>
        Regards,<br>
      </tt><div class="">
      <pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre></div><div><div class="h5">
      On 17.03.2014 17:52, Jeff Pyle wrote:<br>
    </div></div></div><div><div class="h5">
    <blockquote type="cite">
      <div dir="ltr">
        <div>Hi Bogdan,</div>
        <div><br>
        </div>
        <div>Let&#39;s say Bob reinvites Alice to T.38 through my proxy.  My
          proxy declines the reinvite.  That transaction has completed
          and Bob has incremented his CSeq number.  Now, if Bob sends
          another in-dialog request (such as a BYE), the CSeq is one
          higher than Alice is expecting.  That&#39;s not a problem?  Alice
          won&#39;t reply with a 400?</div>
        <div><br>
        </div>
        <div class="gmail_extra">
          <div>
            <div dir="ltr">
              <div><br>
              </div>
              <div>- Jeff</div>
              <div><br>
              </div>
            </div>
          </div>
          <br>
          <br>
          <div class="gmail_quote">On Mon, Mar 17, 2014 at 11:24 AM,
            Bogdan-Andrei Iancu <span dir="ltr">&lt;<a href="mailto:bogdan@opensips.org" target="_blank">bogdan@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">
                <div><tt>Hi Jeff,<br>
                    <br>
                    This is a false problem - you can simply decline the
                    re-INVITE without breaking anything - each side has
                    its own cseq number, and they are independently
                    increased when a party is generating a new requests.<br>
                    <br>
                    So, just decline it and that&#39;s it !<br>
                    <br>
                    Regards,<br>
                  </tt>
                  <pre cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a></pre>
                  <div>
                    <div> On 11.03.2014 19:42, Jeff Pyle wrote:<br>
                    </div>
                  </div>
                </div>
                <div>
                  <div>
                    <blockquote type="cite">
                      <div dir="ltr">
                        <div class="gmail_extra">
                          <div>
                            <div dir="ltr">
                              <div>Hi Alexander,</div>
                              <div><br>
                              </div>
                              <div>To detect the &quot;image&quot; session in the
                                SDP, you are thinking the same way that
                                I am.  The problem I see is how to
                                actually reject the re-INVITE.  If I
                                were to do something like a
                                sl_send_reply(&quot;488&quot;, &quot;Not Acceptable
                                Here&quot;), that would work in the moment,
                                but the CSeq values would be increased
                                by one on side compared to the other.
                                 That sounds to me like a recipe for
                                problems in future in-dialog
                                transactions (like BYE).</div>
                              <div><br>
                              </div>
                              <div><br>
                              </div>
                              <div><br>
                              </div>
                              <div>- Jeff</div>
                              <div><br>
                              </div>
                              <div> <br>
                              </div>
                            </div>
                          </div>
                          <br>
                          <br>
                          <div class="gmail_quote">On Tue, Mar 11, 2014
                            at 12:58 PM, Alexander Mustafin <span dir="ltr">&lt;<a href="mailto:mustafin.aleksandr@gmail.com" target="_blank">mustafin.aleksandr@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 style="word-wrap:break-word">Hi,
                                Jeff.
                                <div><br>
                                </div>
                                <div>Maybe stream_exists(regexp) in
                                  sipmsgops module will be useful for
                                  you.
                                  <div> <br>
                                  </div>
                                  <div>
                                    <div style="text-indent:0px;letter-spacing:normal;font-variant:normal;text-align:-webkit-auto;font-style:normal;font-weight:normal;line-height:normal;text-transform:none;white-space:normal;font-family:Helvetica;word-wrap:break-word;word-spacing:0px">

                                      <div>Best regards,</div>
                                      <div>Alexander Mustafin</div>
                                      <div><a href="mailto:mustafin.aleksandr@gmail.com" target="_blank">mustafin.aleksandr@gmail.com</a></div>
                                      <div><br>
                                      </div>
                                    </div>
                                    <br>
                                    <br>
                                  </div>
                                  <br>
                                  <div>
                                    <div>11 марта 2014 г., в 20:07, Jeff
                                      Pyle &lt;<a href="mailto:jpyle@fidelityvoice.com" target="_blank">jpyle@fidelityvoice.com</a>&gt;

                                      написал(а):</div>
                                    <br>
                                    <blockquote type="cite">
                                      <div>
                                        <div>
                                          <div dir="ltr">
                                            <div>
                                              <div dir="ltr">
                                                <div>Hello,</div>
                                                <div><br>
                                                </div>
                                                <div>Is there anything I
                                                  can do at the proxy
                                                  level to prevent a
                                                  dialog from reinviting
                                                  to to T.38?  I think I
                                                  could detect the T.38
                                                  attributes easily
                                                  enough and respond
                                                  with a 488, although
                                                  I&#39;m concerned the CSeq
                                                  values would be out of
                                                  sequence for the next
                                                  transaction that did
                                                  make it through the
                                                  proxy to the far end.
                                                   That could cause a
                                                  problem, no?</div>
                                                <div><br>
                                                </div>
                                                <div>Is this something
                                                  that requires a B2BUA?
                                                   Is it possible from
                                                  within the OpenSIPS
                                                  B2B modules to do SDP
                                                  inspection of any
                                                  sort?</div>
                                                <div><br>
                                                </div>
                                                <div><br>
                                                </div>
                                                <div>- Jeff</div>
                                                <div><br>
                                                </div>
                                              </div>
                                            </div>
                                          </div>
                                        </div>
                                      </div>
_______________________________________________<br>
                                      Users mailing list<br>
                                      <a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
                                      <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
                                    </blockquote>
                                  </div>
                                  <br>
                                </div>
                              </div>
                              <br>
_______________________________________________<br>
                              Users mailing list<br>
                              <a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
                              <a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
                              <br>
                            </blockquote>
                          </div>
                          <br>
                        </div>
                      </div>
                      <br>
                      <fieldset></fieldset>
                      <br>
                      <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>
                </div>
              </div>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
  </div></div></div>

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