unblock anonymous?

<< < (2/2)

ckck:
@Shale ... I'll try the *68 approach.

@Everton ... I don't have Anonymous CallerID blocked in any of my filters.

I'm 99% certain now that this is happening on the Obi side ... just can't figure out why.

ckck:
OMG, I'm feeling pretty stupid now. I'm really sorry for wasting time/space on this thread.

Way back, when having trouble with SIP scanners (see http://www.obitalk.com/forum/index.php?topic=4067.msg30166#msg30166) waking me at 3 AM, I made this change ...

Obi's Voice Services -> SP1 Serivce -> X_InboundCallRoute:

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

I incorrectly assumed that, since the SIP scanners where targeting the Obi directly and not coming through my voip.ms or GV numbers, changing this setting would only affect calls coming directly to my Obi. This was pretty dumb of me.

I'm going to remove the '?' since most of the SIP scanner calls I was getting were announced as '100' or '1000' and all the '@' should catch those.

Shale:
Quote from: ckck on April 28, 2013, 06:31:56 am



I incorrectly assumed that, since the SIP scanners where targeting the Obi directly and not coming through my voip.ms or GV numbers, changing this setting would only affect calls coming directly to my Obi. This was pretty dumb of me.

I'm going to remove the '?' since most of the SIP scanner calls I was getting were announced as '100' or '1000' and all the '@' should catch those.


Good detective work.

Regarding SIP scanners, see http://www.obitalk.com/forum/index.php?topic=5467.0
What you described is listed as method #1 there. Rather than using that method, you would be better to use method 4 or 3 with you voip.ms account. If you modify your string to just remove the '?', then a voip scanner could spoof what looks like a regular phone number or even present "voipscanner" as a caller ID and would poke right through.

ckck:
Well, early this morning I started to get SIP scanner calls again, one every minutes starting at 2:40am until 3:03am. The scanner's 'Peer Name' and 'Peer Number' were blank.

I followed Shale's method #4 and set X_InboundCallRoute to {>111111:ph} (111111 is not my real AuthUserName).

This should allow anonymous calls, but only through my voip.ms SIP.

Navigation

[0] Message Index

[*] Previous page