Call End Now Not Working...

[56 Kruiser]

A while back I created 4 profiles that would end calls from zip codes that I commonly get spam calls from, unless in my contacts list. It was working perfectly.

Then a couple weeks ago or so, I got a message (I think it was from Tasker, but don't recollect for sure now), that due to changes Google has made that I can no longer use END CALL, and suggested using Screen Calls instead. Printscreen of one of the tasks after modification below:

So, naturally it does not work. BTW...the call block command at the end never has worked either.

Originally I had a Call End command where the Call Screening command is now.

Any thoughts on why the call screening command is not working?

I might add that I just now went to try putting in End Call, and I got a message from Tasker that for it to work I need to run an ADB command that MUST be re-run every time I boot the phone, and that it cannot be automated. That is a bit of a pain so, not wanting to go down that path.

[Robert Ryan]

This is what I use to block unknown callers:

    Profile: Unknown Caller

        Restore: no 

        Notification: no

        

        Event: Call Screened 

        Caller: !C:ANY

        

    Enter: 

    A1: Call Screening  

        Disallow/Allow: Disallow 

        Reject: On 

        Skip Call Log: On 

        Skip Notification: Off 

Note: The Call Screening action does not block outgoing calls. 

In the enter task, you also have the following local variables:

• %cs_number - the current incoming or outgoing phone number. 
• %cs_incoming - true if the call is incoming, false if outgoing. 
• %cs_name - the name associated with the phone number, if any. 

The Call Block action only affects outgoing calls, it has no effect on calls you receive. 

--
You received this message because you are subscribed to the Google Groups "Tasker" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tasker/2be22177-07ac-4fcf-9857-a201e6d20a04n%40googlegroups.com.

[56 Kruiser]

I appreciate the input. Looking at that, I am confused.

The only thing I did not do compared to your list is mark Skip Call Log  to on. I wouldn't think that would keep it from working. 

On the Call Block...that doesn't make much sense to me. Why would a person block outgoing calls? Just don't make the call. I must be misunderstanding something. But I guess as long as it dumps the call, it's not so important to block it. I can do so manually if I wish. 

I just turned Skip Call Log. We'll see if it makes any difference. Can't imagine why it would. But, fingers crossed.

[Robert Ryan]

One more thing. Make sure you have set Tasker as the Default Caller ID and Spam App. On my device this setting is located at:

System settings > Apps > 3-dot menu > Default apps 

To view this discussion on the web visit https://groups.google.com/d/msgid/tasker/8b78ac72-b837-42f0-b680-6bcdb47d17b2n%40googlegroups.com.

[56 Kruiser]

Well, I've checked my settings, and all are as you suggest. It still is not working.

Anyone have any other ideas? Again, I am on a Samsung Note 20 Ultra. 

[João Dias]

Hi. The Call Sceened event will not set the %CNUM variable. You need to use the built-in local variables for the event :)

Thank you for your contact.

   Join: connect multiple devices (send pushes, remote SMS, notifications) on Android, Windows, Mac, Linux

   Tasker: customize/automate anything on your phone!

   AutoApps: add advanced functionality to Tasker via plugins

     

João Dias

[56 Kruiser]

I appreciate the feedback. But, when I click on the icon to display variables to use, it does not list any local variables at all. I based that on reading in the help file that local variables are all lower case. It displays all upper case, and proper case, none shown in strictly lower case. That is from within the  task I created in the IF statement; Then I also checked in the IF statement area of the Call Screening task. It too has no all lower case variables.

What am I missing?

Thanks for the help ;-)

[João Dias]

Hhmm that's strange. Does the Call Screened event condition also not show any variables if you edit?

[56 Kruiser]

Let me present some pics...maybe you'll see where I'm going wrong:

Below is the task:

Note that my IF statement is  here, NOT inside the Call Screening, if that is of importance.

So, next  is Call Screening opened to set options:

I did open the IF on the above, and clicked on the variables selection icon, and it shows a lot of proper case variables, and a few all upper case. No all lower case variables.

Thinking through it, my Profile is just based on the phone ringing. Once inside the task, there is an if statement that was working fine for months until the recent change Google made that requires using CAll Screening. I'm not sure if the initial IF statment inside of the task is failing, or if the call screening option is failing.

Appreciate the help. ;-)

[João Dias]

Oh, that's your issue :) The profile has to be based on the Call Screened event for those variables to show up.

[56 Kruiser]

I am still not having success with call blocking. The profile send the call through the task pictured in the link. I get the message that it has been blocked, then immediately after that the call starts ringing on my phone.

Can you see what I have configured wrong?

https://photos.app.goo.gl/WkSU99FE4ERB9Hiy9

[Robert Ryan]

Your regex has a syntax error. The last character should be a curly brace, not a parentheses. 

-- 

You received this message because you are subscribed to the Google Groups "Tasker" group.

To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/tasker/2ea96b3c-e909-4cb8-b394-44432db8f864o%40googlegroups.com.

[56 Kruiser]

RBR...I'd swear I replied to you with thanks, but I don't see it here. I appreciate your replying to me.

So, fixing that syntax corrected the issue at hand then. But now, it still is not working as expected.

I know that the call is going though the task, because I get a message on the phone: "A 785 call has been blocked", but immediately after that message it starts ringing with a spam call from 785. A picture again of the task pages:

This is the task page as entered into. You can see the say comand. BTW..the Call Block seems to not work either. Well, just glancing at the help on block, looks like it only blocks outgoing calls...I have idea why a person would want to do that. 

Anyway...

Now to show the task that is supposed to keep the call from ringing. This is where the syntax had to be corrected. You will notice that I have not set Reject. The help screen on Disallow/Allow says :Disallow to prevent call from going through. If you don't enable 'Reject', the caller will not know that you wont listen to the phone ring or vibrate. To them it'll seem like a normal call that is left unanswered." That is a strong implication to me that it should not go through, and that I don't need to set Reject on. That being said, having just read all that again to post here, I am going to turn on Reject  and see if that works. If so, Ill be good, but maybe the developer needs to be notified of a bug.

BTW...the Regex used was provided to me from groups here (maybe this thread). I had a typo in it but that has been fixed. I will hunt that down and compare what I am using to be sure it is correct as provided.

Any other help is appreciated.

[56 Kruiser]

Oh, RBR...I see it was you that provided me the Regex. You've been supporting me through this overall. Thanks so much...

The original Regex had a 4 in the brackets at the end, but you responded back pretty quick telling me to change that to 7. 

[Robert Ryan]

There is another error in the regex that I didn't see the first time. You have have the ? and the : swapped. 

It should be (?:

To view this discussion on the web visit https://groups.google.com/d/msgid/tasker/f856a5e1-21f8-489b-bee5-e7bcc131f81cn%40googlegroups.com.

[56 Kruiser]

I'm still not having success. 

So what happens now is that when a call comes in, I get the message from the task that the call has been blocked...but then the call starts ringing my phone. It's like it is ignoring Call Screening part of the task, first line in the task. I'm pasting in a current picture of the Call Screening part of the task:

[jmjc...@gmail.com]

Mind sharing your profile description (instead of just one action)? Long click on profile name -> click top right icon -> Export -> Description to Clipboard. Then paste it here.

If you delete the %cs_number condition, does it work? It should then block ALL incoming calls. If that works, then you know there is a problem with the condition. If that doesn't work either, then maybe your device is not set up properly.

[56 Kruiser]

Glad to do it. For some reason I can't reply to group messages from my phone. So I emailed it to myself then pasted below. I hope that doesn't break what you are looking for from it:

 Profile: Spam Screen 785 (60)

     Restore: no Notification: no

     Event: Call Screened [ Output Variables:* Caller:!C:ANY ]

    Enter: Block 785 (64)

     A1: Call Screening [  Disallow/Allow:Disallow Reject:On Silence:Off Skip Call Log:Off Skip Notification:Off ] If [ %cs_number ~R (?:\+1)?785\d{7} ]

     A2: Variable Add [ Name:%BLOCKED Value:1 Wrap Around:0 ] 

     A3: Say [ Text:A 7 8 5 call has just been blocked by screening 1 Engine:Voice:default:default Stream:3 Pitch:5 Speed:5 Respect Audio Focus:On Network:Off Continue Task Immediately:Off ] 

     A4: Call Block [ Number Match:%CNUM Info:Off ] 

    

I might point out that in the Profile, IO have a condition set because I have 4 area codes I am trying to do this with. All 4 were getting the message, so I would hear 4 times that a call has been blocked, and of course get the call anyway.

I'll past a picture of that setup below, for the 785 number:

Thanks for your time on this...

If you need any thing else from me, just let me know.

[jmjc...@gmail.com]

Thanks.

The description looks alright except A4 is not needed since my understanding is you want to block incoming unknow calls only.  I will suggest removing the %cs_number condition to see if it does block ALL calls. You should also flash %cs_number to make sure it is indeed in the format you expected.

The picture shows something wrong. It should be %cs_number, not %csnumber.

[56 Kruiser]

  Thanks for the input. Here is what  can say at this point.

RE: A4, I certainly can delete that one. The fact is it does not do anything at all. I expected it to mark a particular number as blocked, and it does not do that.

RE: the %cs_number variable and the typo of %csnumber variable: 

- I'm sorry, I don't know what you mean by "...flash %cs_number"

- It is interesting about the csnumber being there. I agree with your statement it should be %cs_number, and I will change that. What's interesting is that the condition does work, based on the following: Without that condition, which was the original suggested way to set it up,  in any of the 4 numbers I'm trying to block (unless they are in my contacts), all four would go through all 4 profiles and be sent to the task. So I would get a message 4 times like this:

• "A call from 785 has been blocked"
• "A call from 913 has been blocked"
• "A call from 312 has been blocked"
• "A call from 316 has been blocked"
• Then my phone would start ringing, having not been blocked.

So, since I added the condition, I only get 1 message that it has been blocked, and again, it in fact is not blocked.
I had all these working before Google made the change that forces us to now use the Call Screening function.

Based on the fact that I get the message that a call has been blocked, that confirms for certain that the call is reaching the task, and it reaching the correct task, as when it says "A 785 call has been blocked", that is the area code of the call that starts ringing.

So it would seem that the calls are not being processed successfully in line A1 of the task. Is that because for some reason it is not getting into A1, or is it that the statement or variables have errors?

Who knows, maybe when I correct the %cs_number variable it will work. I'll correct that, and remove the Call Block statement post back how it goes.

I appreciate your help.

[jmjc...@gmail.com]

If you use the %cs_number as a condition in the EVENT context, you don't need to repeat it in A1. You can safely delete the %cs_number condition in A1 to see if it works.

[56 Kruiser]

Thanks for you continued help. Much appreciated.

I just deleted it from the Call Screening in the task. I'll reply re: success soon.