Weird calls from 1001

[billcanada]

I just received over 10 calls in a row from 1001. The first few I answered and said hello but no one said anything and I heard two guys talking in the background in an unknown accent. Maybe Russian, Middle Eastern. As soon as I hung up, the phone would ring again so I kept answering and said nothing until the other person hung up. When I hung up on my end the phone would immediately ring again. I checked my call logs and no unknown calls showed up. Does anyone know what is going on? Was some nut trying to hack into my computer through an open port to my ATA?

[Jake]

It is probably because your ATA is either in DMZ or you have port 5060 forwarded.

Look on your Line 1 Tab (assuming FPL is set up on Line 1) and look in the 'SIP Settings' section. Try changing 'Restrict Source IP' to yes. This will only allow calls to come from registered trunks, rather than your Middle Eastern friends.

[billcanada]

I am currently using an OBi202. My modem/router and ATA are not in DMZ mode. I don't have a 'Restrict Source IP' option. I have 5060 for my ProxyServerPort, RegistrarServerPort, OutboundProxyPort, X_EchoServerPort and X_KeepAliveServerPort. I have voip.freephoneline.ca for my ProxyServer and OutboundProxy. Are all of those settings correct or should I change or delete something?

It is probably because your ATA is either in DMZ or you have port 5060 forwarded.

Look on your Line 1 Tab (assuming FPL is set up on Line 1) and look in the 'SIP Settings' section. Try changing 'Restrict Source IP' to yes. This will only allow calls to come from registered trunks, rather than your Middle Eastern friends.

[Jake]

Ahh sorry, for some reason I thought you had a PAP2T.

I am not sure about what setting it will be on the OBi, I will try and find it tomorrow unless someone else can help out in the mean time.

[Maxwell Smart]

I have an Obi100. I had this problem too with bogus calls (they are sip scanners / hackers that take advantage of the port 5060 default used with many VOIP devices). I solved the problem by logging into my obi settings, (and in Expert settings) then go into Voice Services, then SP1 (assuming SP1 is for your default VOIP service provider), then in the setting: X_UserAgentPort -- take out the default 5060, and make up some random number greater than 5060 and less than 65535. Save and reboot. That solved the problem completely for me.

Failing that, use the string:
{(?|x|xx|xxx|xxxx|xxxxx|xxxxxx|un@@.|anon@@.):},{p h}
by putting this rule in the X_InboundCallRoute:
This string will ban calls with no Peer Number, any Peer Number less than seven digits, Peer Number "unknown" and Peer Number "anonymous".

Also, if by chance you have your router's firewall set to open port 5060... don't.. close it.. Remove the port 5060 forwarding from your router, then the firewall won't pass the SIP message to the Obi. Port forwarding of 5060 is not required in a proper working VoIP set up. Since the device registers, and re-registers every xx seconds, that keeps the NAT translation open at the firewall. (closing your firewall is important for security sake)

[Hyrules]

you can also simply use the X_AccessList in the obi202. Just add the 2 ip address of FPL. I have fixed that problem that way.