Stupid fake incoming calls

<< < (2/2)

Kamakzie:
So I just put that line {(?|x|xx|xxx|xxxx|xxxxx|xxxxxx):} ... exactly as it is and it should work?

ianobi:
{(?|x|xx|xxx|xxxx|xxxxx|xxxxxx):} ...

Put this rule before the rules you already have. If all you have now is ph, then the final X_InboundCallRoute would look like:

{(?|x|xx|xxx|xxxx|xxxxx|xxxxxx):},{ph}

It bans any blank caller id and any caller id less that seven digits, all other calls ring the phone.

I suggested

{(?|x|xx|xxx|xxxx|555555xx.|un@@.|anon@@.):}

to try to fit the numbers you described. For example un@@. will block any call that shows up as "unknown". Try to fit the rule to the numbers that you wish to ban.

Kamakzie:
So I would do {(?|x|xx|xxx|xxxx|100xx.|un@@.|anon@@.):}

?? 100 is the number coming up.

Kamakzie:
I  put this in {(?|x|xx|xxx|xxxx|xxxxx|xxxxxx):},{ph} we will see if that fixes it.  Why do those idiots scan anyways? 

GregoryZ:
Quote from: Kamakzie on September 07, 2012, 03:43:39 pm

Why do those idiots scan anyways? 


I was wondering the same thing.  :)

Does anyone have a clue?

-G

Navigation

[0] Message Index

[*] Previous page