I have a DD-WRT router that has an option on Port Forwarding to limit the forwarding to a source IP address. I use the Oleg method to block scanners and it works perfectly, but this and other methods on the forum will let the scanner calls into your network and the OBi rejects them. If you include each of your provider's IP in a Port Forwarding entry the scanner calls are blocked at the router and never enter your network. No need to setup blocking in the OBi.
If your Provider uses SRV records you can get a list of the servers on a Windows machine like this:
Open a Command Prompt window.
Key the following:
nslookup
set type=srv
_sip._udp.callcentric.com
The _sip.udp. does not work for sip2sip, so do the following:
nslookup
ping
proxy.sipthor.netNegatives:
Not all routers have this option.
This might require more entries in your router.
If your provider changes IP, calls might fail.
Questions for any network guru.
Question 1
Why doesn't "_sip._udp.proxy.sipthor.net" work?
_sip._udp.callcentric.com produced 2 more servers than ping.
alpha14.callcentric.com and
alpha16.callcentric.comWhy?
Question 2
I always thought Port Forwarding was not required for a registered provider. I tried turning Port Forwarding off and outbound calls worked perfectly, but inbound were inconsistent. Some rang, others didn't. Turning Port Forwarding back on fixed the problem. I don't know if another problem was happening at the same time. I did not try to reproduce the problem.
Is Port Forwarding required for registered providers?
Thanks
Twinkle Toes (Inside Joke)