<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Hey Brett,<br>
    <br>
    For your info, I have tried a similar thing, raising another event
    out of the E_DLG_STATE_CHANGED route however for some reason I could
    not access the avps in there, so not much more info than the
    original event had.<br>
    <br>
    DanB<br>
    <br>
    <div class="moz-cite-prefix">On 18.05.2015 15:23, Brett Nemeroff
      wrote:<br>
    </div>
    <blockquote
      cite="mid:13AE2925-9111-4497-85AD-1B60871A36FA@nemeroff.com"
      type="cite">
      <meta http-equiv="content-type" content="text/html; charset=utf-8">
      <div>Bogdan,</div>
      <div>How about an event route that lets you use script logic to
        modify the event prior to emitting it? <br>
        <br>
        Sent from my iPhone</div>
      <div><br>
        On May 18, 2015, at 4:57 AM, Bogdan-Andrei Iancu &lt;<a
          moz-do-not-send="true" href="mailto:bogdan@opensips.org">bogdan@opensips.org</a>&gt;
        wrote:<br>
        <br>
      </div>
      <blockquote type="cite">
        <div>
          <meta content="text/html; charset=utf-8"
            http-equiv="Content-Type">
          <tt>Hi Dan,<br>
            <br>
            I will do the backport to 1.2.0 - thank you for testing.<br>
            <br>
            Now, on your comments: IMHO it is not wise to add more info
            to the event - the actual event should notify only on the
            change of state and that's it; You need extra A and B
            fields, somebody else C and D, etc... So there is no way to
            get a consents in term of what and how much additional info
            should be added.<br>
            The Options I see:<br>
            1) extend support for events, so you can specify extra vars
            to be pushed into the event - this is a long shot. <br>
            2) derive the event - capture the event and build on top of
            it another custom one, with the additional things you want<br>
            3) get the original event, and using the dialog ID, make a
            dlg_list to get all the info from the dialog.<br>
            <br>
            Regards,<br>
          </tt>
          <pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
          <div class="moz-cite-prefix">On 17.05.2015 14:58, DanB wrote:<br>
          </div>
          <blockquote cite="mid:55588257.5010609@gmail.com" type="cite">
            <meta content="text/html; charset=utf-8"
              http-equiv="Content-Type">
            Hey Bogdan,<br>
            <br>
            Thanks for this.<br>
            <br>
            I can confirm that the hash_entry and hash_id are now
            attached to the event:<br>
            """<br>
            #<br>
            U 2015/05/17 13:55:45.632615 127.0.0.1:60380 -&gt;
            127.0.0.1:2020<br>
            E_DLG_STATE_CHANGED<br>
            hash_entry::1593<br>
            hash_id::82596694<br>
            old_state::4<br>
            new_state::5<br>
            """"<br>
            <br>
            As inquired in the ticket also, will it be possible here to
            add some $avp or dialog variables maybe? From the billing
            perspective we will need to know at least user and
            destination called to make use of dialog_start event.<br>
            <br>
            Ta,<br>
            DanB<br>
            <br>
            <div class="moz-cite-prefix">On 15.05.2015 17:02,
              Bogdan-Andrei Iancu wrote:<br>
            </div>
            <blockquote cite="mid:55560A88.9010707@opensips.org"
              type="cite">
              <meta content="text/html; charset=utf-8"
                http-equiv="Content-Type">
              <tt>Hi Dan,<br>
                <br>
                Could you check the patch I did (see commit e461b65) to
                provide the hash_entry and hash_id for the event ? if
                ok, I will backport to 2.1 too<br>
                <br>
                Regards,<br>
              </tt>
              <pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
              <div class="moz-cite-prefix">On 11.05.2015 15:08,
                Bogdan-Andrei Iancu wrote:<br>
              </div>
              <blockquote cite="mid:55509BAC.1090703@opensips.org"
                type="cite">
                <meta content="text/html; charset=utf-8"
                  http-equiv="Content-Type">
                <tt>Right good one :D..... We will patch it to include
                  the DID too.<br>
                  <br>
                  Regards,<br>
                </tt>
                <pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
                <div class="moz-cite-prefix">On 11.05.2015 14:54, DanB
                  wrote:<br>
                </div>
                <blockquote cite="mid:5550985A.7090708@gmail.com"
                  type="cite">
                  <meta content="text/html; charset=utf-8"
                    http-equiv="Content-Type">
                  Hi Bogdan,<br>
                  <br>
                  That is a useful variable indeed (works perfect with
                  Accounting). Unfortunately have no clue how to
                  include/attach it to the E_DLG_STATE_CHANGED event.<br>
                  <br>
                  Thanks,<br>
                  DanB<br>
                  <br>
                  <div class="moz-cite-prefix">On 11.05.2015 13:52,
                    Bogdan-Andrei Iancu wrote:<br>
                  </div>
                  <blockquote cite="mid:555097EC.5010805@opensips.org"
                    type="cite">
                    <meta content="text/html; charset=utf-8"
                      http-equiv="Content-Type">
                    <tt>Hi Dan,<br>
                      <br>
                      Try the $DLG_did variable :<br>
                          <a moz-do-not-send="true"
                        class="moz-txt-link-freetext"
href="http://www.opensips.org/html/docs/modules/1.11.x/dialog.html#id297237">http://www.opensips.org/html/docs/modules/1.11.x/dialog.html#id297237</a><br>
                      <br>
                      Regards,<br>
                    </tt>
                    <pre class="moz-signature" cols="72">Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a></pre>
                    <div class="moz-cite-prefix">On 09.05.2015 12:23,
                      DanB wrote:<br>
                    </div>
                    <blockquote cite="mid:554DD217.8030003@gmail.com"
                      type="cite">
                      <meta content="text/html; charset=utf-8"
                        http-equiv="Content-Type">
                      Hey Bogdan,<br>
                      <br>
                      Thank you for the tip. I am trying now to use as
                      advised E_DLG_STATE_CHANGED.<br>
                      <br>
                      I get the following information in the event:<br>
                      """<br>
                      U 2015/05/09 11:19:59.018404 127.0.0.1:40817 -&gt;
                      127.0.0.1:2020<br>
                      E_DLG_STATE_CHANGED<br>
                      old_state::1<br>
                      new_state::5<br>
                      """<br>
                      <br>
                      Can you advise me how to add some useful
                      information inthere? I would need to know at least
                      h_entry and h_id for the dialog (so I can kill it
                      from outside<span style="color: rgb(0, 0, 0);
                        font-family: Helvetica, Arial; font-size: 12px;
                        font-variant: normal; font-weight: normal;
                        letter-spacing: normal; line-height: normal;
                        orphans: auto; text-align: justify; text-indent:
                        0px; text-transform: none; white-space: normal;
                        widows: 1; word-spacing: 0px;
                        -webkit-text-stroke-width: 0px;
                        background-color: rgb(255, 255, 255);"></span>)
                      and some other $avps I need for prepaid at the
                      start of the call.<br>
                      <br>
                      Thanks again!<br>
                      DanB<br>
                      <br>
                      <div class="moz-cite-prefix">On 07.05.2015 18:42,
                        Bogdan-Andrei Iancu wrote:<br>
                      </div>
                      <blockquote
                        cite="mid:554B9612.7050708@opensips.org"
                        type="cite">Hi Dan, <br>
                        <br>
                        As in ACC you cannot do START/STOP and CDRs in
                        the same time, I suggest to use the CDR event
                        for accounting purposes and for monitoring the
                        dialog status take a look at the
                        E_DLG_STATE_CHANGED event: <br>
                        <a moz-do-not-send="true"
                          class="moz-txt-link-freetext"
href="http://www.opensips.org/html/docs/modules/2.1.x/dialog.html#id297207">http://www.opensips.org/html/docs/modules/2.1.x/dialog.html#id297207</a>
                        <br>
                        <br>
                        Regards, <br>
                        <br>
                        Bogdan-Andrei Iancu <br>
                        OpenSIPS Founder and Developer <br>
                        <a moz-do-not-send="true"
                          class="moz-txt-link-freetext"
                          href="http://www.opensips-solutions.com">http://www.opensips-solutions.com</a>
                        <br>
                        <br>
                        On 06.05.2015 13:39, DanB wrote: <br>
                        <blockquote type="cite">Hey Guys, <br>
                          <br>
                          I am using EVI to generate CDRs out of
                          OpenSIPS. The result is that I get one CDR
                          record at the end of the dialog as E_ACC_CDR
                          event. <br>
                          <br>
                          Now I would need to know also when dialog
                          starts (eg: after INVITE is being OKed). <br>
                          <br>
                          What is the most recommended way to achieve
                          that? I tried setting evi_flag but it appears
                          that works only if I do not set cdr_flag. Am I
                          right in that assumption? Are both evi_flag
                          and evi_missed_flag options suppressed by
                          cdr_flag? <br>
                          <br>
                          Thanks in advance for your feedback! <br>
                          DanB <br>
                          <br>
                          _______________________________________________
                          <br>
                          Users mailing list <br>
                          <a moz-do-not-send="true"
                            class="moz-txt-link-abbreviated"
                            href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
                          <br>
                          <a moz-do-not-send="true"
                            class="moz-txt-link-freetext"
                            href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
                          <br>
                          <br>
                          <br>
                        </blockquote>
                        <br>
                      </blockquote>
                      <br>
                    </blockquote>
                    <br>
                  </blockquote>
                  <br>
                </blockquote>
                <br>
                <br>
                <fieldset class="mimeAttachmentHeader"></fieldset>
                <br>
                <pre wrap="">_______________________________________________
Users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
              </blockquote>
              <br>
            </blockquote>
            <br>
          </blockquote>
          <br>
        </div>
      </blockquote>
      <blockquote type="cite">
        <div><span>_______________________________________________</span><br>
          <span>Users mailing list</span><br>
          <span><a moz-do-not-send="true"
              href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a></span><br>
          <span><a moz-do-not-send="true"
              href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a></span><br>
        </div>
      </blockquote>
    </blockquote>
    <br>
  </body>
</html>