Mango has suggested that I add Oleg's method as a good alternative way to thwart SIP scanners. I would like to understand and then be able to describe the method in a way that a person doing setup could use.
As I understand this, the modification of the InboundCallRoute looking for the AuthUserName is an alternative method of thwarting SIP scanners. The InboundCallRoute is what identifies whether to send a given call to ph, ph1 or ph2 on OBi202, or AA,
or to kick it to the byte bucket.
Question 1: The strings on the left side of colons are compared against the incoming caller ID equivalent -- what do we call that string?
Oleg's situation seems to be that he gets connections directly from his company rather than a sip provider... maybe I am wrong on this.
Question 2. Is this method be suitable as the method for avoiding SIP scanners if they receive their calls through Anveo, Callcentric, voip.ms
, etc? This method seems particularly useful for providers that have too many server IPs to list. It also
seems useful for those that want to permit some direct connections without opening the path to everybody.
3/20/2013 2:19:10 AM INVITE sip:+firstname.lastname@example.org:5078 SIP/2.0
3/20/2013 2:19:14 AM INVITE sip:email@example.com:5078 SIP/2.0
3/20/2013 2:19:14 AM INVITE sip:firstname.lastname@example.org:5078 SIP/2.0
3/20/2013 2:19:17 AM INVITE sip:email@example.com:5078 SIP/2.0
3/20/2013 2:19:17 AM INVITE sip:firstname.lastname@example.org:5078 SIP/2.0
3/20/2013 2:19:20 AM INVITE sip:email@example.com:5078 SIP/2.0
Question 3: Where did Oleg get these logs and how would I get them? The Call History from my OBi202 does not resemble that.