SIP scanners
giqcass:
@QBZappy I must say I am very happy with Google Voice on the OBI but I do like to keep an incoming SIP backup in case there is an issue with Google Voice. I like redundancy. Google likes to change things and it may break functionality. I would think requiring registration would stop that issue but even when I allowed my PAP2 to take unregistered connections I never had the problems being described here.
I'm sure we will see an increase in this type of activity due to the increased popularity of VOIP. If the scanner is looking for SIP specific devices putting it in on another port should work. VOIP should work on any port that isn't being used. Here are a few ports that should not cause conflicts.
5076-5078
5364-5396
5457-5460
5466-5499
5507-5552
5586-5596
47809-47999
Here is a list of commonly used and unused ports. http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml
ianobi:
Hortoristic,
So long as the incoming Caller ID, shown as Peer Number in OBi Call History, has more than six digits, then it will be fine.
I'm still using the original string:
{(?|x|xx|xxx|xxxx|xxxxx|xxxxxx):},{ph}
I designed it that way as I need to accept some seven-digit Caller IDs. Other users have added and changed to suit there own situations.
You may simply want to try changing the UserAgentPort as to one suggested by giqcass. That worked for me for a while, but not in the long run. Maybe I should have picked a more obscure port number.
Hortoristic:
I'm not the smartest tool in the shed, so can someone explain how the SIP scanner is coming in on SP1 - when I have SP1 set up for GV? - the SIP account I have set up is actually on SP2, but my call history when the scanner calls is as:
Call History:
From '1' SP1(1)
So the {(?|x|xx|xxx|xxxx|xxxxx|xxxxxx):},{ph} string should be put into both X_InboundCallRoute for both SP1 and SP2 I'm assuming?
All my testing seems to show that a (on purpose SIP call from one of my UK DID's) SIP call is ringing one port above whatever SP1 is - I think my SP2 is port 5062, I never could get the first port to ring and thought this was because it was configured with GV.
Hortoristic:
Will blocked calls show up in my call history still, proving my X_InboundCallRoute is working?
ianobi:
Hortoristic,
Here is my limited understanding of what is going on. The SIP scanners are testing millions of IP addresses and at each address they test port 5060. The nuisance calls are not coming in via your service providers, but direct to your ip address/port, so it does not matter what service provider is say on sp1. In the Obi UserAgentPort for sp1 is 5060 by default. This is the one to change to some random port as posted above. I think some scanners may also look at 5061 and 5070, as I got caught using them. Using non-default ports and the above string has worked for me.
I don’t have an Obi202, so I’m curious about the Call History. You says yours shows: “From '1' SP1(1)” – does this indicate a Caller ID of “1”? If so, then the |x| rule in the string will stop it and any other single-digit Caller ID.
Blocked calls will not show up in Call History, as effectively the calls are not getting into the Obi.
Navigation
[0] Message Index
[#] Next page
[*] Previous page