[asterisk-r2] Timer Question?

[Arturo Ochoa]

On Tue, Jul 14, 2009 at 12:02 PM, Moises Silva<moises.silva at gmail.com> wrote:
> On Tue, Jul 14, 2009 at 1: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.
>>
>
> libmfcr2 uses the standard nomenclature for timers. I apologize, but openr2
> does not use the standard nomenclature because I wanted easy to remember
> names since I was not familiar with the standard names for the timers
> anyway.
> The t3 timer in libmfcr2 is the same as timers.mf_back_cycle setting in
> openr2 (read more in doc/r2proto.conf advanced sample file), however, being
> a common setting, you can also set it in chan_dahdi.conf in Asterisk via
> mfcr2_mfback_timeout, in both cases the amount of milliseconds must be
> specified.
>
> --
> Moises Silva
> Software Developer
> Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3
> Canada
> t. 1 905 474 1990 x 128 | e. moy at sangoma.com
>
> _______________________________________________
> --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
>

Ohh Thank you Moy... actually mfcr2_mfback_timeout was the first one I
tried... but in my test environment didn't work... but I'll change
that on the production one... let's see if there's some difference...