[OpenSIPS-Users] Rtpproxy - failover

[Max Mühlbronner]

  Hi Bogdan,

Really makes sense, I should have noticed this myself while looking at 
the Documentation.

This totally explains why the gateways got no replies back from 
opensips, because every minute it would stall for 5 seconds. (5 retries 
x 1 sec timeout --> every minute)

Thanks

Max M.

Am 22.09.2010 11:12, schrieb Bogdan-Andrei Iancu:
> Hi Max,
>
> For re-enabling RTPproxy, there are 3 parameters:
>
> 1: "rtpproxy_disable_tout" - how long the RTPproxy is kept in disable
> state before re-enabling it again
>
> 2: "rtpproxy_timeout" - timeout in communication with RTPp
>
> 3: "rtpproxy_retr" - number of retries before timeout
>
> So, to avoid too much waiting, tthe "rtpproxy_timeout" and
> "rtpproxy_retr" should have small values - this will avoid blocking.
>
> Regards,
> Bogdan
>
> Max Mühlbronner wrote:
>>    Hello everyone,
>>
>> i have experienced some strange Problem using multiple instances of
>> rtpproxy via  rtpproxy_sock. (Opensips 1.6.2) If one rtpproxy is
>> disabled, opensips will still try to re-enable/reconnect to the same
>> rtpproxy later. The problem is, opensips is not responding correctly at
>> this time, it is hanging and not doing any other transactions while
>> trying the rtpproxy...?
>>
>> It seems like opensips is checking every ~60 Seconds if the rtpproxy is
>> available (i already found: "rtpproxy_disable_tout" which is 60 by
>> default). So i probably just have to raise it, so rtpproxy will not be
>> tried so often? But am not sure if its a bug, or just a limitation, any
>> similar experiences?
>>
>>
>> Max M.
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>