Printable View
I was quite unpleasantly awakened at around 3 AM this morning by two calls in rapid succession that rang on line 2 only (both lines have the same number). They showed up on the caller ID as "1001" for both the name and phone number. Nobody was on the line when I answered, and neither call shows up in my call history. I've submitted a ticket regarding this matter and thought I'd see if other customers have experienced anything like this.
the calls don't come through your Voipo account. You can search for SIP scanners, or read a decent discussion here. The post deals with how to thwart them as well; however, unless you have unlocked (BYOD) device, you can't change SIP port or incoming dial plan (I don't know if such thing even exists on Grandstreams).
I would think that Voipo can set up the adapter to reject all calls that don't come from Voipo servers...
I hate to say it, but it is probably just a matter of time before we all start getting anonymous Viagra calls. :(
I believe there is a way to disable inbound calls from non-registered sources or something. Just not sure if all devices have that capability.
I just started getting calls on line 2. Caller ID says 1000 for both name and number. The calls were coming non-stop until I received a real call on line 1. Does anyone know what is causing this and how to keep it from happening again?
These unwanted calls are typically caused by someone probing/scanning your ATA.....most likely coming from a China IP address. They are not coming from Voipo.
Here's a few suggestions:
1) The best thing to do is open up a support ticket with Voipo and have them change your SIP ports to something other than 5060 or 5061 (e.g. 5078 or 5079). This will usually stop the probing.
2) If you have a Linksys ATA, ask support if they will enable the "Restrict Source IP" setting in the ATA. Other ATA brands (Grandstream, etc) may or may not have a similar setting. This will absolutely stop the probing. In layman's terms, this basically tells the ATA to drop all data packets from any untrusted IP source and to only accept data packets from Voipo's SIP server.
3) Lastly, tighten up your router's firewall if you can. They are getting through your open ports in your router's firewall to the ATA, so removing any DMZ or port forwarding to your ATA may eliminate the issue. Hopefully you can do so without affecting calls to/from your ATA.
Hope this helps.........
Just reporting the same occurance happend to me at midnight last night - incoming call from 1001 followed by rapid rings. Extremly annoying.
My ATA was in a DMZ, but I just changed that and hopefully that will take care of this.
I do have an Obi that I used in the past for Google Voice. If I were to use this as my Voipo ATA would I loose any of the Voipo features?
So far it's just been the one time for me. It was frustrating because I couldn't make it stop except by unplugging the phone and I was expecting a call. My ATA is in a DMZ because it was easier than forwarding all the required ports.
It happened again tonight after my wife went to bed. Is there a way to stop this? Caller ID now says 1001 like everyone else.
Couldn't you simply use Call Routing. Set incoming calls from 1001 to receive a diconnected signal or something else of your choice?
Good idea. I just routed 1000 and 1001 numbers to disconnected. Will wait and see if it works.Quote:
Originally Posted by budmaster
I'm sure it won't. When this happens, Voipo's servers aren't involved at all, so routing is bypassed. To effectively deal with this problem the ATA needs to be configured to ignore traffic from all sources except Voipo's servers.
Quote:
Originally Posted by ThorsDad
Hello,
Feel free to submit a ticket to support@voipo.com and we can accommodate ATA changes to alleviate this issue pretty easily.
If you have unlocked (BYOD) adapter, I suggest you look at different ways you block the scanners on OBiHai forum. If you have a different adapter, it will still help you as long as you know how to do the things the article describes. I found out through personal experience that just changing ports from 5060 to 5070 didn't help :(
If you have a Voipo-provisioned adapter, I suppose, voipo support can restrict the calls by originating IP or something similar... I am surprised that nobody from Voipo support commented here. EDIT: I missed the second page of posts that makes this paragraph irrelevant :)
Again, these calls are not coming from your Voipo account; so any "blocking" that you do on Voipo website are completely irrelevant. Also, tinkering with firewall in most cases is irrelevant as well (I can't think of any situation when changes in firewall would make a difference - but I am sure I am missing some unique situation)
This is still an issue with the Cisco (Linksys) SPA-8000 and SP-112 ATAs as there a way to hack them. The fix from Cisco has been to enable "Restrict Source IP" but you cannot do this with Voipo service as per Voipo "Only allowing packets from sip.voipwelcome.com will break call signaling for any traffic routing directly from our media gateways. Their IP range is outside of our control and can be unique depending on the call's routing."
I have asked Voipo for the underlying carrier IP ranges but they cannot provide them and will not support BYOD devices.
So the only way to block the hackers are to put the ATA behind a firewall and block the specific IP addresses from the hackers. This will end up getting very tedious and you will be right back to the firewall closing ports and having connectivity issues with Voipo services and the ATA.
Yesterday, my phone (primarily line 2 which is the same number as line 1), started ringing almost non-stop every few minutes. I am a BYOD'er with a Grandstream and it was a quite easy fix. If you are having this issue (and are not a BYOD'er), submit a ticket and Voipo can fix it.