[asterisk-r2] Timer Question?

[Arturo Ochoa]

Yes, I already did it... that's why I'm asking....
I found this timers on the r2proto.conf


# Timers in milliseconds
# Use -1 to leave default, or just comment it out for that matter
timers.mf_back_cycle=1500
timers.mf_back_resume_cycle=150
timers.mf_fwd_safety=10000
timers.r2_seize=8000
timers.r2_answer=80000
timers.r2_metering_pulse=0
timers.r2_double_answer=0
timers.r2_answer_delay=150
timers.cas_persistence_check=500

and also:

mfcr2_mfback_timeout=-1
mfcr2_metering_pulse_timeout=-1


I've been trying playing with all of them, but I'm not sure which is
the right one...

Ing Arturo Ochoa





On Tue, Jul 14, 2009 at 11:56 AM, Juan Carlos
Huerta<juancarloshuerta at gmail.com> wrote:
> There's a lot of timer settings you can customize in OpenR2, check de doc to
> set the timers according to your needs.
>
> Juan Carlos
> ~ Lo que no te mata te fortalece ~
>
>
> On Tue, Jul 14, 2009 at 12:52 PM, Arturo Ochoa <arturo.era at gmail.com> wrote:
>>
>> Hi List...
>>
>> I got this question:
>>
>> On the past Unicall implementation, there was a variable called t3 on
>> the MX variant.
>>
>>  mfcr2->t3 = 5000;
>>        /* The time the inbound register has to accept or reject the
>> call (by sending
>>           the group B tone) is 90s, which is longer than the normal
>> compelled sequence
>>           timer. */
>>
>> Does anyone know where (if possible) can I change that value in openr2?
>> AFAIK, this will only affect the inbound perspective.
>>
>>
>> Ing Arturo Ochoa
>>
>> _______________________________________________
>> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>>
>> asterisk-r2 mailing list
>> To UNSUBSCRIBE or update options visit:
>>   http://lists.digium.com/mailman/listinfo/asterisk-r2
>
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-r2 mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-r2
>