Unknown call on caller ID--came through Obi box?
flex25:
Hey QBZappy. Thanks for your help.
I tested the Callcentric IP range in the Obi setup, ITSP Profile A>SIP->X_AccessList =
I entered 204.11.192.0/22
That didn't work; I couldn't receive a test phone call.
So, I tried 204.11.192.0 - 204.11.195.255
just that exact way, with spaces before and after the dash, as Callcentric showed it written, and that didn't work; I couldn't receive a test phone call.
Then I tried the single IP address within the range that I got when I tried the ping test (which timed out), and it did work; the test call did ring my phone.
So, I looked more online, and found this website,
http://support.google.com/googleanalytics/bin/answer.py?hl=en&answer=55572
that has a calculator thing to generate an IP address range using the first and last IP address in the range. I entered them, and got:
^204\.11\.(1(9[2-5]))\.([0-9]|[1-9][0-9]|1([0-9][0-9])|2([0-4][0-9]|5[0-5]))$
Which I put in ITSP Profile A>SIP->X_AccessList =
and voila, the test call did ring my phone. So I guess that is the IP range in some other written format.
According to that link, it's a Google filter pattern. Then, there's this page that expalins Google regular expressions: http://support.google.com/googleanalytics/bin/answer.py?hl=en&answer=55582
It looks like a bunch of wldcard rules to match all variations of the numbers in the IP address range.
I would love to think I succeeded here. So whatdaya think?
QBZappy:
flex25,
The manual clearly says comma separated list.
My router allows this:
"1.1.1.1", "1.1.1.0/24", "1.1.1.1 - 2.2.2.2" or "me.example.com"
It seems that you may have tried a few of these variations already. It might be that the OBi simply does support ip ranges.
It would be nice if OBiSupport would chime in with the definite answer right about now.
Quote from: flex25 on June 13, 2012, 08:36:17 pm
Does the different IP address matter?
I would think so.
Are you still getting "Unknown" callers?
flex25:
Hi QBZappy--I tried something else after I posted that response and just modified my response.
I haven't gotten unknown callers since that day, but it's been only one week.
Quote
It would be nice if OBiSupport would chime in with the definite answer right about now.
I agree. This is an Obi-sponsored forum, and it appears that Obi does not respond as much as I would think they would.
Followup: Nope, this isn't the solution either. I tried some different ranges, written in the Google filter pattern, and all of them allowed my phone to ring. The Obi configuration is not recognizing the Google filter pattern--it's as if the field is blank, and it's defaulting to allow all IP addresses through. If I enter a single IP address outside the range, it blocks the call. The Obi configuration will not accept a range, only single addresses, separated by commas.
When I have some time, I will do the range as a list with Excel, and format and paste the list, if the Obi configuration allows that long a list. I can look into what I can do in the router as well. Other than that, the only other option I see is to place an external call blocker between the Obi and the phone to block calls coming through the Obi itself.
Obi, please update so that ITSP Profile A/B>SIP->X_AccessList = to accept a range of IP addresses, to block SIP scanners. This is an issue that quite a few users have had.
Ad_Hominem:
I know that this is an OLD thread, but I wanted to chime in and let everyone know that it seems that the Belkin routers have a very special way of handling VOIP devices. If the router sees a VOIP device sending SIP calls out, it opens that port for ALL INCOMING SIP traffic to that device, even if the traffic is coming from somewhere other than where your device is connecting to. That's a huge security hole. Most routers DO NOT do this.
Just to clarify, if I have a VOIP device behind a typical router, and it registers to Callcentric, the router will open up the port so that Callcentric's IP address can respond. Belkin routers, however, just open the port completely and allow anyone to access the device. That's not safe.
I suggest that ANYONE who has a Belkin router DUMP it and get a router that does not engage in this kind of risky practices.
Shale:
Quote from: Ad_Hominem on October 04, 2013, 10:03:52 pm
... it seems that the Belkin routers have a very special way of handling VOIP devices. If the router sees a VOIP device sending SIP calls out, it opens that port for ALL INCOMING SIP traffic to that device, even if the traffic is coming from somewhere other than where your device is connecting to. That's a huge security hole. Most routers DO NOT do this.
I believe you are mistaken on this. Most routers do this. Some do not. Some users change the router firmware to get the behavior you are looking for.
Navigation
[0] Message Index
[#] Next page
[*] Previous page