<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <tt>Hi Callum,<br>
      <br>
      I looked a bit into this. Checking the code, I see that the
      session creation is triggered on the spot when the
      rtpproxy_engage() is called...so it is a bit difficult to miss
      :D...<br>
      <br>
      Also I tried by running a simple cfg like:<br>
      <br>
      route {<br>
          ....<br>
          if (is_method("INVITE")) {<br>
              create_dialog();<br>
              do_accounting("log");<br>
              rtpproxy_engage();<br>
          }<br>
      <br>
          if (!lookup("location","m")) {<br>
              t_reply("404", "Not Found");<br>
              exit;<br>
          }<br>
          async( usleep("1000"), after_usleep );<br>
      }<br>
      <br>
      route[after_usleep] {<br>
          route(relay);<br>
      }<br>
      <br>
      And I got both U and L<br>
      <br>
      U 2019/03/14 19:15:51.618487 127.0.0.1:60966 -> 127.0.0.1:4545<br>
        3793_11 Uc0,2,4,8,18,96,97,98,101 <a class="moz-txt-link-abbreviated" href="mailto:91f0ad91-bde974e4@10.10.0.12">91f0ad91-bde974e4@10.10.0.12</a>
      10.0.0.12 163<br>
        90 d6119dad8d81e378o2;1     <br>
      <br>
      U 2019/03/14 19:16:05.813619 127.0.0.1:58127 -> 127.0.0.1:4545<br>
        3795_11 Lc0,3,110,8,98,101 <a class="moz-txt-link-abbreviated" href="mailto:91f0ad91-bde974e4@10.10.0.12">91f0ad91-bde974e4@10.10.0.12</a>
      10.10.0.15 8000 d6119<br>
        dad8d81e378o2;1 5a60fb3a;1    <br>
      <br>
      Am I missing something here ?<br>
      <br>
      Regards,<br>
    </tt>
    <pre class="moz-signature" cols="72">Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  <a class="moz-txt-link-freetext" href="https://www.opensips-solutions.com">https://www.opensips-solutions.com</a>
OpenSIPS Summit 2019
  <a class="moz-txt-link-freetext" href="https://www.opensips.org/events/Summit-2019Amsterdam/">https://www.opensips.org/events/Summit-2019Amsterdam/</a>
</pre>
    <div class="moz-cite-prefix">On 03/11/2019 10:37 AM, Callum Guy
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAFjCFzkHLFQeObjnE9SkaHjWtgYN+UK1c3cb_dcYa=eGP7hhSg@mail.gmail.com">
      <div dir="ltr">Hi Bogdan,
        <div><br>
        </div>
        <div>Yes, that's correct. </div>
        <div><br>
        </div>
        <div>In my scenario I created the dialog, engaged rtpproxy and
          then performed an async rest_post. The result was that the
          session creation was not triggered on the remote rtpproxy.</div>
        <div><br>
        </div>
        <div>Let me know if I can provide any further information.</div>
        <div><br>
        </div>
        <div>Many thanks,</div>
        <div><br>
        </div>
        <div>Callum</div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Mon, 11 Mar 2019 at 07:26,
          Bogdan-Andrei Iancu <<a href="mailto:bogdan@opensips.org"
            moz-do-not-send="true">bogdan@opensips.org</a>> wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div bgcolor="#FFFFFF"> <tt>Hi,<br>
              <br>
              Shortly said, if you do rtpproxy_engage() *before* an
              async call, the create session is not triggered  ?<br>
              <br>
              Regards,<br>
            </tt>
            <pre class="gmail-m_-4783947696075019566moz-signature" cols="72">Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  <a class="gmail-m_-4783947696075019566moz-txt-link-freetext" href="https://www.opensips-solutions.com" target="_blank" moz-do-not-send="true">https://www.opensips-solutions.com</a>
OpenSIPS Summit 2019
  <a class="gmail-m_-4783947696075019566moz-txt-link-freetext" href="https://www.opensips.org/events/Summit-2019Amsterdam/" target="_blank" moz-do-not-send="true">https://www.opensips.org/events/Summit-2019Amsterdam/</a>
</pre>
            <div class="gmail-m_-4783947696075019566moz-cite-prefix">On
              03/08/2019 04:30 PM, Callum Guy wrote:<br>
            </div>
            <blockquote type="cite">
              <div dir="ltr">
                <div dir="ltr">
                  <div dir="ltr">
                    <div dir="ltr">Hi OpenSIPs Community,
                      <div><br>
                      </div>
                      <div>I wanted to report an issue I discovered when
                        attempting to use the rtpproxy module, using the
                        dialog backed rtpproxy_engage() function.
                        Finding that it was not engaging in certain
                        scenarios I took a closer look at the activity
                        on the control port and discovered that OpenSIPS
                        never sent a request to open the session in this
                        scenario.</div>
                      <div><br>
                      </div>
                      <div>To help illustrate, here is an example
                        control port sequence of a properly engaged
                        call:</div>
                      <div><br>
                      </div>
                      <div>65098_11 <b>UR</b>8.8.8.8c9,8,0,3,101,13 <b><i>the-call-id</i></b>
                        192.168.153.223 10248 <b><i>from-tag</i></b>;1<br>
                      </div>
                      <div>65118_19 <b>LR</b>8.8.8.8c8,101 <b><i>the-call-id</i></b> 192.168.153.223 10248 <b><i>from-tag</i></b>;1 <b><i>to-tag</i></b>;1<br>
                      </div>
                      <div><br>
                      </div>
                      <div>In my scenario the <b>UR</b> (create
                        session) request was never received. Without
                        claiming any expertise on the rtpproxy protocol
                        this was clearly not correct and the <b>LC</b> (update
                        session) request could not locate a session to
                        act on.</div>
                      <div><br>
                      </div>
                      <div>Following a fairly lengthy investigation I
                        traced the issue back to my usage of the async()
                        function where i was issuing the
                        rtpproxy_engage() request before calling async
                        for another purpose. The solution was simply to
                        move the rtpproxy_engage() call to after the
                        async method.</div>
                      <div><br>
                      </div>
                      <div>I'm happy that the issue is resolved for my
                        requirements however I thought I would share the
                        experience to the list in case others found
                        themselves having a similar issue.</div>
                      <div><br>
                      </div>
                      <div>Thanks!</div>
                      <div><br>
                      </div>
                      <div>Callum</div>
                    </div>
                  </div>
                </div>
              </div>
              <br>
              <p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;text-align:justify"><font
                  face="Verdana" size="3"><span
style="font-size:8px;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline"></span></font></p>
              <div><img
src="https://www.x-on.co.uk/email/footer/banner-surgeryconnect-mar-19.jpg"
                  moz-do-not-send="true"></div>
              <div><br>
              </div>
              <div>
                <div>
                  <div><font size="4"><b><sup><font face="Verdana">0333
                            332 0000  |  <a
                              href="http://www.x-on.co.uk"
                              target="_blank" moz-do-not-send="true">www.x-on.co.uk</a> 
                            |  <sub> </sub></font></sup></b></font><font
                      size="4"><b><sub><sup><font face="Verdana"><a
                                href="https://www.linkedin.com/company/x-on"
                                target="_blank" moz-do-not-send="true"><img
src="http://www.x-on.co.uk//images/icon/linkedin.png"
                                  moz-do-not-send="true" height="24"
                                  width="24"></a>  <a
                                href="https://www.facebook.com/XonTel"
                                target="_blank" moz-do-not-send="true"><img
src="http://www.x-on.co.uk//images/icon/facebook.png"
                                  moz-do-not-send="true" height="24"
                                  width="24"></a>  <a
                                href="https://twitter.com/xonuk"
                                target="_blank" moz-do-not-send="true"><img
src="http://www.x-on.co.uk//images/icon/twitter.png"
                                  moz-do-not-send="true" height="24"
                                  width="24"></a></font></sup></sub> </b></font><br>
                    <p><span
                        style="font-size:6pt;font-family:Verdana;color:black">X-on
                        is a trading name of Storacall Technology Ltd a
                        limited company registered in England and Wales.<br>
                        Registered Office : Avaland House, 110 London
                        Road, Apsley, Hemel Hempstead, Herts, HP3 9SD.
                        Company Registration No. 2578478.<br>
                        The information in this e-mail is confidential
                        and for use by the addressee(s) only. If you are
                        not the intended recipient, please notify X-on
                        immediately on <span>+44(0)333 332 0000</span>
                        and delete the<br>
                        message from your computer. If you are not a
                        named addressee you must not use, disclose,
                        disseminate, distribute, copy, print or reply to
                        this email. </span><span
                        style="font-size:6pt;font-family:Verdana;color:black">Views
                        or opinions expressed by an individual<br>
                        within this email may not necessarily reflect
                        the views of X-on or its associated companies.
                        Although X-on routinely screens for viruses,
                        addressees should scan this email and any
                        attachments<br>
                        for viruses. X-on makes no representation or
                        warranty as to the absence of viruses in this
                        email or any attachments.</span></p>
                    <p><span
                        style="font-size:6pt;font-family:Verdana;color:black"></span><font
                        size="2"><span
                          style="font-size:6pt;font-family:Verdana;color:black"></span></font></p>
                  </div>
                </div>
              </div>
              <br>
              <fieldset
                class="gmail-m_-4783947696075019566mimeAttachmentHeader"></fieldset>
              <br>
              <pre>_______________________________________________
Users mailing list
<a class="gmail-m_-4783947696075019566moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org" target="_blank" moz-do-not-send="true">Users@lists.opensips.org</a>
<a class="gmail-m_-4783947696075019566moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank" moz-do-not-send="true">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
            </blockquote>
            <br>
          </div>
        </blockquote>
      </div>
      <br>
      <p dir="ltr"
style="line-height:1.38;margin-top:0pt;margin-bottom:0pt;text-align:justify"><font
          face="Verdana" size="3"><span
style="font-size:8px;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:baseline"></span></font></p>
      <div><img
src="https://www.x-on.co.uk/email/footer/banner-surgeryconnect-mar-19.jpg"
          moz-do-not-send="true"></div>
      <div><br>
      </div>
      <div>
        <div>
          <div><font size="4"><b><sup><font face="Verdana">0333 332
                    0000  |  <a href="http://www.x-on.co.uk"
                      target="_blank" moz-do-not-send="true">www.x-on.co.uk</a> 
                    |  <sub> </sub></font></sup></b></font><font
              size="4"><b><sub><sup><font face="Verdana"><a
                        href="https://www.linkedin.com/company/x-on"
                        target="_blank" moz-do-not-send="true"><img
                          src="http://www.x-on.co.uk//images/icon/linkedin.png"
                          moz-do-not-send="true" height="24" width="24"></a>
                       <a href="https://www.facebook.com/XonTel"
                        target="_blank" moz-do-not-send="true"><img
                          src="http://www.x-on.co.uk//images/icon/facebook.png"
                          moz-do-not-send="true" height="24" width="24"></a>
                       <a href="https://twitter.com/xonuk"
                        target="_blank" moz-do-not-send="true"><img
                          src="http://www.x-on.co.uk//images/icon/twitter.png"
                          moz-do-not-send="true" height="24" width="24"></a></font></sup></sub> </b></font><br>
            <p><span
                style="font-size:6.0pt;font-family:Verdana;color:black">X-on
                is a trading name of Storacall Technology Ltd a limited
                company registered in
                England and Wales.<br>
                Registered Office : Avaland House, 110 London Road,
                Apsley, Hemel Hempstead,
                Herts, HP3 9SD. Company Registration No. 2578478.<br>
                The information in this e-mail is confidential and for
                use by the addressee(s)
                only. If you are not the intended recipient, please
                notify X-on immediately on <span>+44(0)333 332 0000</span>
                and delete the<br>
                message from your computer. If you are not a named
                addressee you must not use,
                disclose, disseminate, distribute, copy, print or reply
                to this email. </span><span
                style="font-size:6.0pt;font-family:Verdana;color:black">Views
                or opinions expressed by an individual<br>
                within this email may not necessarily
                reflect the views of X-on or its associated companies.
                Although X-on routinely
                screens for viruses, addressees should scan this email
                and any attachments<br>
                for
                viruses. X-on makes no representation or warranty as to
                the absence of viruses
                in this email or any attachments.</span></p>
            <p><span
                style="font-size:6.0pt;font-family:Verdana;color:black"></span><font
                size="2"><span
                  style="font-size:6.0pt;font-family:Verdana;color:black"></span></font></p>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>