PDA

View Full Version : Cid: +0



sal
07-26-2010, 10:29 AM
Got a call:

+0
Unknown
Call Reference ID: 1527269569_42784117@xxx.xxx.xx.xxx

I have block all unknown calls enabled. Does anyone know what this is?

holmes4
07-26-2010, 06:45 PM
I'd like to suggest that Voipo treat invalid CID numbers as "Blocked". For example, I got a call today from "7260002827". That of course has to be bogus, with a 000 exchange. The telemarketers are supplying deliberately invalid CID info and I'd think that Voipo could apply some basic rules to filter these out.

usa2k
07-27-2010, 05:00 AM
I'd like to suggest that Voipo treat invalid CID numbers as "Blocked". For example, I got a call today from "7260002827". That of course has to be bogus, with a 000 exchange. The telemarketers are supplying deliberately invalid CID info and I'd think that Voipo could apply some basic rules to filter these out. Excellent thought!

VOIPo may need the occasional ticket to open a new overlay, but otherwise that sounds effective. It would mostly be a bit of work and debugging as it is newly implemented. In routing, along with "unknown", they could add a separate rule called "Invalid CID". Require the NPA-NXX to be valid.

My In-laws who live in Canada had their call rejected the other day. I was wondering what was going on! I reject all but a few local exchanges. I do not have 416*******, but their 519******* is good to ring the phone.

On checking, their number was ID'd as 416825**** and should have been 519825****. Apparently this was a side-effect of a calling card service. I added my own *8251234 rule to let their specific 7 digit number ring in the future!

holmes4
07-27-2010, 09:22 AM
Upon further investigation, Voipo might already be doing this. It turns out that the "000" exchange number never rang my phone, though I saw it in the call log. I have "Unknown" numbers blocked.

My suggestion would not require overlay checking - just look for syntactically invalid numbers (area code or exchange of 000), which I see a lot of telemarketers using. I suppose they could switch to 001 or something like that...

voipinit
08-02-2010, 06:00 AM
I use call routes to block 000 area codes and exchanges, 000******* and ***000****.

MisterEd
08-02-2010, 06:51 PM
^^^ What he said. Also do the same for all the other oddball CID's. Call routes with wildcards are great.

sal
08-04-2010, 07:22 AM
Thanks everybody. I blacklisted 0********* and ***000****.

4plus3vette
08-06-2010, 10:45 AM
Hey Sal,

Since you used 0*********, would you also be able to use ***0****** instead of ***000****?

Also, when blocking these types of calls, I like to have it go to a busy signal. That way they can continue to waste their time calling back.

Jim

4plus3vette
08-06-2010, 10:49 AM
Here is another one:

1*********

This website: http://www.bennetyee. org/ucsd-pages/area.html lists out area codes and the first one is at 201.