<div dir="ltr">Hi Daniel,<div><br></div><div><div>Sure Daniel, I can process 487 on onreply route... I was trying to handle 487 in failure_route block, I didn't know it can be processed in onreply_route!</div><div><br>
</div><div>I know that rtpproxy destroys the session by itself in short time it is not confirmed, but I'm trying to force it the most amount of possible cases.</div><div><br></div><div>Now, my final problem (I hope) is destroy the rtp session when receive the BYE message to finish a forking call. I have to add “extra_id_pv” and use "b" parameter to get destroy the session on rtpproxy, but I don't know if exist somehow to discover if the BYE belongs a forking call context. I tryed use $branch variable but without success...</div>
<div><br></div><div>Best Regards</div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/5/15 Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
  
    
  
  <div text="#000000" bgcolor="#FFFFFF">
    Hello,<div class="im"><br>
    <br>
    <div>On 5/14/13 7:15 PM, Bruno Bresciani
      wrote:<br>
    </div>
    <blockquote type="cite">
      <div dir="ltr">Thank's Daniel,
        <div><br>
        </div>
        <div>
          <div>I need process cancel requests to delete sessions on rtp
            proxy... In a call forking, when I need forking to multiple
            destinations on different network segments, requiring
            different rtpproxy parameters, I use the “extra_id_pv” and
            "b" parameter in the rtpproxy_offer() function to created a
            session RTP to each branch of calling in rtp proxy. When one
            of branch answer the call, I want delete the other(s)
            session(s) on rtp proxy (unforce_rtp_proxy()) using the
            CANCEL SIP message to do this, but I can't get handle it in
            configuration file...</div>
          <div>I am wrong trying use the CANCEL message to delete
            session rtp? I will try onsend_route to handle...</div>
        </div>
      </div>
    </blockquote>
    <br></div>
    maybe you can do it onreply route, when the invite is replied with
    487.<br>
    <br>
    Anyhow, rtpproxy destroys the session by itself in short time it is
    not confirmed.<br>
    <br>
    Cheers,<br>
    Daniel<div><div class="h5"><br>
    <br>
    <blockquote type="cite">
      <div dir="ltr">
        <div>
          <div><br>
          </div>
          <div>Best Regards</div>
        </div>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">2013/5/14 Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>></span><br>
          <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
            <div text="#000000" bgcolor="#FFFFFF"> Hello,<br>
              <br>
              why do you need to process cancel requests? They have
              special routing requirements related to associated invite
              and sent from tm directly. The event route is for the
              requests sent by modules via tm.<br>
              <br>
              Haven't tried, but maybe onsend_route will capture it.<br>
              <br>
              Cheers,<br>
              Daniel
              <div>
                <div><br>
                  <br>
                  <div>On 5/14/13 12:30 AM, Bruno Bresciani wrote:<br>
                  </div>
                </div>
              </div>
              <blockquote type="cite">
                <div>
                  <div>
                    <div dir="ltr">Hi All,
                      <div><br>
                      </div>
                      <div>
                        <div>in a call forking, after one branch answer
                          the call (200 OK reply), a CANCEL SIP message
                          has been sending to other/another branch(es)
                          and I need to process this/these cancellations
                          in configuration file. After reading some
                          documentations, I discovered there is
                          event_route[tm:local-request] block, which is
                          executed when tm generates internally and
                          sends a SIP request,  Such cases are:</div>
                        <div><br>
                        </div>
                        <div>SIP messages sent by msilo module</div>
                        <div>SIP messages sent by presence server</div>
                        <div>SIP messages sent by dialog module</div>
                        <div>SIP messages sent via MI or CTL interfaces </div>
                        <div><br>
                        </div>
                        <div> I didn't understand very well this cases,
                          so I insert event_route block in my
                          kamailio.cfg but neither CANCEL SIP message or
                          other requests generated by tm module was
                          handled by event_route. I must be using wrong
                          concept to handle this CANCEL SIP message,
                          it's possible handle this messages in
                          configuration file?</div>
                        <div><br>
                        </div>
                        <div>Best Regards</div>
                      </div>
                    </div>
                    <br>
                    <fieldset></fieldset>
                    <br>
                  </div>
                </div>
                <pre>_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a>
<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><span><font color="#888888">
</font></span></pre>
                <span><font color="#888888"> </font></span></blockquote>
              <span><font color="#888888"> <br>
                  <pre cols="72">-- 
Daniel-Constantin Mierla - <a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a>
<a href="http://twitter.com/#%21/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a>
Kamailio Advanced Training, San Francisco, USA - June 24-27, 2013
  * <a href="http://asipto.com/u/katu" target="_blank">http://asipto.com/u/katu</a> *</pre>
                </font></span></div>
            <br>
            _______________________________________________<br>
            SIP Express Router (SER) and Kamailio (OpenSER) - sr-users
            mailing list<br>
            <a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a><br>
            <a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users</a><br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
    <pre cols="72">-- 
Daniel-Constantin Mierla - <a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a>
<a href="http://twitter.com/#!/miconda" target="_blank">http://twitter.com/#!/miconda</a> - <a href="http://www.linkedin.com/in/miconda" target="_blank">http://www.linkedin.com/in/miconda</a>
Kamailio Advanced Training, San Francisco, USA - June 24-27, 2013
  * <a href="http://asipto.com/u/katu" target="_blank">http://asipto.com/u/katu</a> *</pre>
  </div></div></div>

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