Hi Razvan, <div><br></div><div>I have fixed an issue were rtpproxy was not being called during reinvites and the customer reduced the use of timeout notifications. The last occurrence of the problem was December 27. There are three possibilities for the problem have disappeared. </div>
<div><br></div><div>1. re-invite handling</div><div>2. rtpproxyset handling (I fixed some errors where the set was being set to an invalid value)</div><div>3. The user has decreased the use of timeout notifications to a minimum and the occurrence is now less frequent. </div>
<div><br></div><div>Still observing the problem. </div><div class="gmail_extra"><br clear="all"><div><div>Flavio E. Goncalves</div><div> </div></div><br><div class="gmail_quote">2013/1/7 Răzvan Crainea <span dir="ltr">&lt;<a href="mailto:razvan@opensips.org" target="_blank">razvan@opensips.org</a>&gt;</span><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, Flavio!<br>
        <br>
        Can you tell me what versions of OpenSIPS and RTPProxy are you
        using?<br>
        <br>
        Best regards,<br>
      </tt><div class="im">
      <pre cols="72">Razvan Crainea
OpenSIPS Core Developer
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a>
</pre></div><div><div class="h5">
      On 01/03/2013 12:31 PM, Flavio Goncalves wrote:<br>
    </div></div></div><div><div class="h5">
    <blockquote type="cite">Hi Razvan, 
      <div><br>
      </div>
      <div>I&#39;m checking if the problem is not related to re-invites and
        calling rtpproxy set with an invalid value. Anyway, the logs are
        below. </div>
      <div>
        <p>Dec 20 14:59:28 /sbin/opensips[6978]:
          ERROR:rtpproxy:timeout_listener_process: Wrong formated
          message received from rtpproxy [1]</p>
        <p>Dec 20 14:59:28 /sbin/opensips[6978]:
          <a>INFO:rtpproxy:timeout_listener_process</a>: RTPProxy buffer: [255]
&lt;3066.74196691#0121744.870880408#0121968.<a href="tel:1268777973%23012949" value="+551268777973" target="_blank">1268777973#012949</a>.<a href="tel:1984340712%2301274" value="+551984340712" target="_blank">1984340712#01274</a>.448511458#012860.999375735#0121893.793805873#0122451.492975819#0123796.1055294097#012485.853875076#0122426.1713554641#0122310.1069754522#012555.1176777710#0123225.315833604#0122922.440360056#012976.780586176#0122899.1149567571#0121&gt;</p>

      </div>
      <div class="gmail_extra"><br clear="all">
        <div>
          <div>Flavio E. Goncalves</div>
          <div>CEO - V.Office</div>
          <div> </div>
        </div>
        <br>
        <br>
        <div class="gmail_quote">2012/12/18 Răzvan Crainea <span dir="ltr">&lt;<a href="mailto:razvan@opensips.org" target="_blank">razvan@opensips.org</a>&gt;</span><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, Flavio!<br>
                  <br>
                  I&#39;ve attached a patch for the rtpproxy module, that
                  for every error, it prints the buffer received from
                  the Rtpproxy server. What I want to see is if the
                  message is totally broken, or only some parts of it
                  are malformed. Could you please apply this patch, and
                  paste us the output when the error occurs again?<br>
                  <br>
                  Best regards,<br>
                </tt>
                <pre cols="72">Razvan Crainea
OpenSIPS Core Developer
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a>
</pre>
                <div>
                  <div> On 12/13/2012 07:01 PM, Flavio
                    Goncalves wrote:<br>
                  </div>
                </div>
              </div>
              <blockquote type="cite">
                <div>
                  <div>
                    <div>I&#39;m having an issue with timeout notification
                      of rtpproxy. </div>
                    <div><br>
                    </div>
                    <div>Usually sessions are disconnected properly with
                      rtpproxy timeout notification:</div>
                    <div><br>
                    </div>
                    <div><a>INFO:do_timeout_notification</a>:
                      notification timeout sent 1715.2112525045 :
                      Success (The dialog hash is presented correctly
                      with period .)<br>
                    </div>
                    <div><br>
                    </div>
                    <div>However, In some cases (3 to 7 per day in 25000
                      calls) we got the following message from rtpproxy
                      module. RTP Proxy in this case send the dialog id
                      with a # in the middle. I can&#39;t reproduce the
                      problem in the lab. </div>
                    <div><br>
                    </div>
                    <div>
                      <div>Dec 12 16:42:4
                        ERROR:rtpproxy:timeout_listener_process: Wrong
                        formated message received from rtpproxy -
                        invalid dialog entry <a href="tel:%5B1727216578%230123634" value="+551727216578" target="_blank">[1727216578#0123634</a>]</div>
                    </div>
                    <div><br>
                    </div>
                    <div>In this case there is a hash in the middle of
                      the dialog identifier (a str2int function
                      generates this error in the rtpproxy module
                      denying the request and throwing the error
                      message. </div>
                    <div><br>
                    </div>
                    <div>
                      <div>No errors in OpenSIPS log</div>
                      <div>No errors in rtpproxy log (debug enabled)</div>
                    </div>
                    <div><br>
                    </div>
                    <div>Any ideas?</div>
                    <div><br>
                    </div>
                    <div>Flavio E. Goncalves</div>
                    <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" 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>
      <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>

<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" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>