<div class="gmail_quote">On Tue, Jul 14, 2009 at 1:52 PM, Arturo Ochoa <span dir="ltr"><<a href="mailto:arturo.era@gmail.com">arturo.era@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi List...<br>
<br>
I got this question:<br>
<br>
On the past Unicall implementation, there was a variable called t3 on<br>
the MX variant.<br>
<br>
mfcr2->t3 = 5000;<br>
/* The time the inbound register has to accept or reject the<br>
call (by sending<br>
the group B tone) is 90s, which is longer than the normal<br>
compelled sequence<br>
timer. */<br>
<br>
Does anyone know where (if possible) can I change that value in openr2?<br>
AFAIK, this will only affect the inbound perspective.<br>
<br></blockquote></div><div><br></div>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.<div>
<br></div><div>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.<br clear="all">
<br>-- <br>Moises Silva<br>Software Developer<br>Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3 Canada<br>t. 1 905 474 1990 x 128 | e. <a href="mailto:moy@sangoma.com">moy@sangoma.com</a><br>
</div>