Constant calls from Caller ID 1000

[shawn122]

Just now my FPL line was ringing constantly for 2min. Caller number and ID both said 1000. When I answered, the call waiting would kick in. If I hung up.. The phone would ring again and again.

It stopped after I unplugged my handset.

Anyone get something like this?

[lustucru]

This looks like a spoofed CallerId.

Unfortunately, there is not too much you can do to avoid such calls. Maybe, block them through a PBX feature.

[lustucru]

I made a test with Skype with the following results:

- Skype to Cell: Caller_Id 10000123456
- Skype to DV: Caller_Id 661-xxx-xxxx
- Skype to DID2CALL (forwarded to VoipBuster): CallerId 10000123456

I noticed in the past that Skype CallerId displays differents numbers and is not consistant.

[Jake]

There is a setting on some ATAs that will only accept calls from registered sources. I don't know the term that the Obi might have it in so you might have to flick through the manual unless someone else can post what it is.

[shawn122]

Thanks for the advice. I will look to see what I can do. If anyone has an idea what I should look for, any help is appreciated!

[Jake]

Thanks for the advice. I will look to see what I can do. If anyone has an idea what I should look for, any help is appreciated!

It won't be much help probably, but on the Grandstream products the setting is called "Allow Incoming SIP Messages from SIP Proxy Only".

I had a quick look on Google but could not find the Obi100 equivalent, sorry. Maybe it doesn't have one.

There are a few Obi users on the forum, maybe one of those will help.

[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, then go into Voice Services, then SP1 (assuming SP1 is for your FPL), 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@@.):},{ph}
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".

[tbrummell]

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.

[shawn122]

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.

Thanks for this tip! I removed the port forwarding and will see if this goes away.

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, then go into Voice Services, then SP1 (assuming SP1 is for your FPL), 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@@.):},{ph}
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".

Thanks for the info! I will try removing the port forward listed above to see if this gets rid of the problem. If not...I will try your solution next.