It makes me crazy, can not block calls from "demo"

[lionhoho]

Hi everyone, now is almost 2:00 am here. The f*ck SIP Scanners pull me out from my bed  . The calls start from 1:00am and ring up my phone every 5-10 minutes. I even tried setup my X_InboundCallRoute in SP1 Service to {(xx.):},{ph}, I was pretty sure I couldn't ring my phone by using my cell but the truth is I still getting calls from caller ID "demo" to SP1.

Here are some log form the Call History
Call 1   05/06/2014    01:48:08   

01:48:08   From 'demo' SP1(demo)   To PH1
01:48:08      Ringing
01:48:13      Call Connected
01:48:15      Call Ended
Call 2   05/06/2014    01:41:00   

01:41:00   From 'demo' SP1(demo)   To PH1
01:41:00      Ringing
01:41:07      Call Connected
01:41:09      Call Ended
Call 3   05/06/2014    01:33:56   

01:33:56   From 'demo' SP1(demo)   Fork to:
PH1
PH2
01:33:56      Ringing (PH1)
01:33:56      Ringing (PH2)
01:34:07      Call Connected (PH1)
01:34:13      Call Ended
Call 4   05/06/2014    01:26:54   

01:26:54   From 'demo' SP1(demo)   To PH1
01:26:54      Ringing
01:26:59      Call Connected
01:27:01      Call Ended
Call 5   05/06/2014    01:19:50   

01:19:50   From 'demo' SP1(demo)   Fork to:
PH1
PH2
01:19:50      Ringing (PH1)
01:19:50      Ringing (PH2)
01:19:55      Call Connected (PH1)
01:19:57      Call Ended
Call 6   05/06/2014    01:12:36   

01:12:36   From 'demo' SP1(demo)   Fork to:
PH1
PH2
01:12:37      Ringing (PH1)
01:12:37      Ringing (PH2)
01:12:41      Call Connected (PH1)
01:12:44      Call Ended
Call 7   05/06/2014    01:05:29   

01:05:29   From 'demo' SP1(demo)   Fork to:
PH1
PH2
01:05:29      Ringing (PH1)
01:05:29      Ringing (PH2)
01:05:34      Call Connected (PH1)
01:05:52      Call Ended
Call 8   05/06/2014    00:58:33

00:58:33   From 'demo' SP1(demo)   Fork to:
PH1
PH2
00:58:33      Ringing (PH1)
00:58:33      Ringing (PH2)
00:58:39      Call Connected (PH1)
00:59:11   Call Ended   
Call 9   05/06/2014    00:51:37   

00:51:37   From 'demo' SP1(demo)   Fork to:
PH1
PH2
00:51:37      Ringing (PH1)
00:51:37      Ringing (PH2)
00:51:48      Call Connected (PH1)
00:51:51      Call Ended
Call 10   05/06/2014    00:44:28   

00:44:28   From 'demo' SP1(demo)   Fork to:
PH1
PH2
00:44:28      Ringing (PH1)
00:44:28      Ringing (PH2)
00:44:42      Call Connected (PH1)
00:44:49      Call Ended

------

Is there anything I missed？Please save me! Thanks!

[ianobi]

General info on stopping SIP scanner calls is here:

http://www.obitalk.com/forum/index.php?topic=5467.msg35387#msg35387

I use methods 2 and 4 described in that post and never receive any nuisance calls.

{(xx.):},{ph}

This would stop all numbers from calling you, but not CallerIDs made up of letters such as "demo".
{(@@.):},{ph} would stop all CallerIDs made up of numbers or letters or a mixture of both, but then you could receive no calls!

If you wish to block calls using your InboundCallRoute, then something like this should work:

{(?|@|@@|@@@|@@@@|@@@@@|@@@@@@):},{ph}

It blocks anonymous calls and any Caller ID with one to six alphanumeric characters. For example @@@@@ blocks callerIDs with five alphanumeric characters: user1, 12345, abc23, Peter.

Each @ is one alphanumeric character - one letter or one number. If you only want to block numbers, then use x in place of @

[lionhoho]

Thanks a lot ianobi, I used to use

{(?|x|xx|xxx|xxxx|xxxxx|xxxxxx|xxxxxxx|100xx|xxxxxxxxx53351|18006686500|as11111as|un@@.|anon@@.|demo@@.|abc@@.|admin@@.|pri@@.):},{ph1,ph2}

still got scan calls. I'll try to use your method. Thanks a lot!

[ianobi]

Looks like you had a lot of CallerIDs covered! However, I can see why "demo" got through. This rule:

demo@@.

means a CallerID starting with the letters "demo" followed by one alphanumeric character, followed by none or more alphanumeric characters. A simple "@" with no dot means there has to be one alphanumeric character. "@." means none or more alphanumeric characters.

A rule stating "demo" or "demo@." or "@@@@" would all have matched a CallerID of "demo".

OBi devices are very pedantic when it comes to punctuation   

[lionhoho]

Very appreciate your help. Now I get a right direction to fix my rules. I didn't get the idea of @@. and @. before so as you can see I was trying to block "admin" as well but sometimes I still get calls from this ID. Now my rules should be

{(?|x|xx|xxx|xxxx|xxxxx|xxxxxx|xxxxxxx|100xx|xxxxxxxxx53351|18006686500|as11111as|un@.|anon@.|demo@.|abc@.|admin@.|priva@.):},{ph1,ph2}

I thinks this rule fits for anyone using freephoneline in Canada. I got all the scan calls form here. Anyway, thanks a lot for the help!

[ipse]

Ianobi's suggestion works for me just fine...as a matter of fact I see some weird calls in my Anveo logs, but they never make it to the device.
That's on top of the scanner elimination - knock on wood, I haven't got a SIP scanner call in 18 months.
Telemarketers on the other hand...a whole other story: they seem to buy numbers in bulk these days, as I block one and the next day they call again from a number few digits apart.