Auto Redial - Help

[Rich_L]

Can Tasker recognize when my outgoing call is connected, and trigger an immediate automatic redial when the line is busy?

I have have to call an automated reservation system 1 week in advance at a specific time (I can call Monday at 7pm, for an appointment on the following Monday). Unfortunately, so many other people dial in, that I usually get a busy signal, or, three tones, and a message such as "we're sorry, your call can not be completed as dialed. Please hang up and try again." So, I redial until I am finally connected. Often all the reservations are gone in under 10 minutes.  I successfully get a reservation  1 week out of 5.

For about 20 minutes each week I dial (busy), hang up,  redial (busy), hang up. redial (busy) ....


Here's what I would like to do:

1. Auto-dial the phone number
2. If  there is a busy signal (or the 3 tones plus message),  then  hang up.
3. Auto-Dial until connected, or for either a fixed number of attempts (or possibly until a fixed amount of time has passed).
5. If connected, proceed to make my reservation via the keypad.

The trick is recognizing the connected call and/or the failed call. Is this possible with Tasker?

This would be great for calling for radio contests and concert tickets too!

Thanks,

Rich_L

[Pent]

> Can Tasker recognize when my outgoing call is connected,

You can't recognize a connected call, so all options will involve
listening
for a connected call and stopping a loop I think.

Use a widget to set a variable %CALLING and make the first call. When
you get event Phone Idle (for after call is disconnected) while
%CALLING is set, wait a couple of seconds and try again. Press a
different widget to stop the loop when you get connected (by clearing
%CALLING). Or if you're optimistic, use the same widget with a toggle
variable.

Pent

[Rich_L]

I was also looking at the built-in variable %CODUR, outgoing call duration, to determine if my call lasted less than say 5 seconds and have it  would auto redial.
but I can not seem to get a value for %CODUR.  Not sure what I am doing wrong.

[Pent]

Good idea.

Works fine for me. You're not just trying to show it via the Test
button are you ?

Pent

[Rich_L]

Yes It works for me too. I did not realize it would not work via the test button.

Thanks,

Rich

[BossMan]

... and I believe this is the reason for this (taken from SMS-related variables, http://tasker.dinglisch.net/userguide/en/variables.html):
"These variables will be empty until the first time a text is received after they have been referenced because Tasker does not monitor SMSs unless it's needed."

BR,
A.