SIP scanners
giqcass:
I'm a big supporter of the “Oleg Method” myself. It ended all sip scanner activity from ringing my phone. Using the “Oleg Method” the sip scanner would need your Ip address, port number, and user name to ring your phone.
ddgiant:
Thanks for both of your quick reply's. The last time I had to deal with this was before the Oleg method.
I just want to make sure I am re-setting this correctly due to a lot of talk in these forms that I do not deal with regularly so it is a little confusing to me.
I have 2 SP services (Callcentric for E911 and GV for everything else)
SP1 I will change my X_InboundCallRoute from {(?|x|xx|xxx|xxxx|xxxxx|xxxxxx|u's'@.|abc@.):},{ph,ph2} to{>17771234567:ph1,ph2} (I just changing back to default will not set this)
SP2 I will change my X_InboundCallRoute from {(?|x|xx|xxx|xxxx|xxxxx|xxxxxx|u's'@.|abc@.):},{ph,ph2} to {>gmailaddres@gmail.com} is this correct?
If the Google voice one is not correct then is there an easy fix, or being I know Google is dropping the protocol I am using, maybe it is time to do my change over to 100% callcentric.
azrobert:
GoogleVoice doesn't use the SIP protocol, so you don't need to block SIP scanners on the GV trunk.
ianobi:
For Callcentric on sp1 this {>17771234567:ph1,ph2} should work fine.
As azrobert says, you should not need to worry about GV on sp2. You can see from your Call History that the scanner calls are coming in on sp1.
Personally, I like to use the Oleg Method and change the UserAgentPorts away from 5060, 5061 etc as these are the ones most often targeted by scanners. Some may say it's overkill, but I like a "belt and braces" approach to this problem :)
gderf:
On my Obi200 the "Oleg Method" is applied automatically when configured via OBiTALK. There is no need to do this manually.
Navigation
[0] Message Index
[#] Next page
[*] Previous page