[asterisk-r2] clear_back_persistence_check equivalent

Sat Apr 4 18:50:07 CDT 2009

Like any other variable there is no original value until you set it. I
agree however it could be handy to set that variable when the channel
is created to have the value configured in chan_dahdi.conf, I may add
that someday if I don't forget it.

Moy

On Fri, Apr 3, 2009 at 2:22 PM, Paulo Angonese <angonese at gmail.com> wrote:
> Moises, the server is ready, and the extensions.conf prepared.
> But, just to avoid "losing the travel" (because the PABX is far), I´ve put
> some NoOp's to display the content of  MFCR2_DOUBLE_ANSWER variable and made
> a test.  But not connected to the E1/R2 trunk yet.
> Before SET the value is null (no value) and after  the value is "no".  The
> behaviour is like any other variable I've invented.
> Is that correct?  The original value shouldn't be "yes"?
>
> CLI> mfcr2 show version
> OpenR2 version: 1.2.0, revision: 189
>
> extensions.conf
> exten => _30[8-9],1,NoOp,xx${MFCR2_DOUBLE_ANSWER}
> exten => _30[8-9],n,Set(MFCR2_DOUBLE_ANSWER=no)
> exten => _30[8-9],n,NoOp,xx${MFCR2_DOUBLE_ANSWER}
> exten => _30[8-9],n,Dial(Dahdi/g1/${EXTEN},40)
>
> The output from console:
>     -- Executing [308 at dddcelular:1] NoOp("SIP/9349-b7600468", "") in new
> stack
>     -- Executing [308 at dddcelular:2] Set("SIP/9349-b7600468",
> "MFCR2_DOUBLE_ANSWER=no") in new stack
>     -- Executing [308 at dddcelular:3] NoOp("SIP/9349-b7600468", "no") in new
> stack
>     -- Executing [308 at dddcelular:4] Dial("SIP/9349-b7600468",
> "Dahdi/g1/308|40") in  new stack
>
> Paulo Angonese
>
>
>
>
>
>
>
> Moises Silva escreveu:
>
> Forget about your idea of Answer(), Hangup(), Answer(), that will
> never work under any situation.
>
> Just call Set(MFCR2_DOUBLE_ANSWER=yes) in the calls where you want to
> use double answer (Based on DNIS, CallerID or whatever you want)
> before doing Dial() or before Answer() if you want to answer
> immediately before Dialing, for all other calls
> Set(MFCR2_DOUBLE_ANSWER=no) or just don't set it. If you don't set
> that variable the default from chan_dahdi.conf will be used.
>
> Moy
>
> On Thu, Apr 2, 2009 at 4:07 PM, Paulo Angonese <angonese at gmail.com> wrote:
>
>
> Let me confirm:
>
> - change the MFCR2_DOUBLE_ANSWER to YES;
> - include in the extensions.conf, just before the DIAL, Answer(),
> Hangup(), Answer ();
> Is this ok?
> The MFCR2_DOUBLE_ANSWER=YES will only work only in this situation, not
> in global form?
>
> Paulo Angonese
>
>
> Moises Silva escreveu:
>
>
> The functionality you require is only in
> http://svn.digium.com/svn/asterisk/team/moy/mfcr2-1.4 and the beta
> release of Asterisk 1.6.2.
>
> You just set the variable MFCR2_DOUBLE_ANSWER before calling Answer()
>
> This also requires openr2 from the release-1 branch
> (http://openr2.googlecode.com/svn/branches/release-1) that is the
> branch that will become openr2 1.2.0 anytime soon. However, be aware I
> added some changes a few days ago for DTMF/R2 support and I have not
> really tested it well, I may have introduced some bug here or there
> :-)
>
> Moy
>
> On Thu, Apr 2, 2009 at 3:19 PM, Paulo Angonese <angonese at gmail.com> wrote:
>
>
>
>     Ok. It´s working.  Using  mfcr2_metering_pulse_timeout=2000 in openr2
> and clear_back_persistence_check=2000 in unicall as well.
>
>     But... (always has a but...)
>
>     There are some extensions in PABX which the colletc calls are permited.
> In these cases it doesn´t do the double answer.
> And,... the variable MFCR2_CATEGORY is always the same:
> national_subscriber... the TelCo is not changing its value.
> I´m trying to talk to TelCo to change, but I don´t believe. And, sincerely,
> the ideal is to implement the solution without talking with TelCo and PABX
> maintanaince.
> The transparent form is the ideal.
>
>    One solution could be do the bouble answer in Asterisk, based in the
> destination extension. I tried answer - hangup - answer and dial the
> extension. But just after the hangup Asterisk ends the call.  Flash() only
> in FXO lines. Is there any other technique to simulate the double answer in
> Asterisk?
>
>    A sugestion: simply bypass the ANSWER - CLEAR BACK - ANSWER from E1 PABX
> to  E1 TelCo.  Transparently, if it occurs between the
> mfcr2_metering_pulse_timeout  time.   At this manner the colletc call policy
> could be stayed at the PABX (totally transparent!).
>
>   It´s another problem. Time to change the title?
>
>   Paulo Angonese
>
>
> Moises Silva escreveu:
>
> Just add this:
>
> mfcr2_metering_pulse_timeout=2000
>
> Moy
>
> On Wed, Apr 1, 2009 at 2:05 PM, Paulo Angonese <angonese at gmail.com> wrote:
>
>
>    Hi. I´m new in this list.
>
>    I'm trying to put an Asterisk betwen an Ericsson MD110 and the TelCo
> (Brasil Telecom).
>    The problem is collect calls blocked by the MD110. It uses the double
> answer technique. When Asterisk, using OpenR2, receives the CLEAR BACK ,
> call drops immediatly. One solution is to program the MD110 allowing the
> collect calls, and use the use the mfcr2_allow_collect_calls=no or
> mfcr2_double_answer=yes in Asterisk, I know. But I can´t (and I don´t want)
> ask to MD110 maintaince to do this.
>    The solution using Unicall is to change
> mfcr2->clear_back_persistence_check in mfcr2.c  to  a value like 2000 (two
> seconds in my case).
>    How can I do this using OpenR2?
>
>    Thanks
>
>    Paulo Angonese
>
>
> _______________________________________________
> --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
>
>
>
>
>
>
> _______________________________________________
> --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
>

-- 
"I do not agree with what you have to say, but I’ll defend to the
death your right to say it." Voltaire