SIP scanners
ianobi:
Mango,
Yes, very true. I tried to pick a simple illustration from my actual sp2 InboundCallRoute, which is:
{(Mcot)>(<**7:>(Mtg1))|(Mtg1):tg1},{(Mcot)>(<**7:>(Mextns))|(Mextns)|(<**7:>(Msp2))|(<**2:>(Msp2)):sp2},{(Mcot)>(<**7:>(Mvg4))|(<**4:>(Mvg4)):vg4},{(Mcot)>(<**7:>(Msoft)),(Mcot)>(Msoft):pp},{(Mcot)>(<**7:>(Msoft))|(Msoft)|(<**7:>(Mpp))|(<**9:>(Mpp)):pp},{(Mcot)>(<**7:>(**0))|**0:aa},{(Mcot)>(<**7:>(0|61))|(0|61):ph},{(Mcot):aa}
cot contains the allowed CallerIDs.
This rule from above may be of interest to this thread:
{(Mcot)>(<**7:>(0|61))|(0|61):ph}
Where you can see that the callee digit map (0|61) is used to call the phone.
Mango:
I see that you certainly know what you are talking about. :) Thanks for sharing your InboundCallRoute.
ianobi:
Ostracus,
It was my solution to calling a SIP URI directly over the OBiTALK network using OBiON from a cell phone or OBiAPP from a softphone. The OBiTALK network does not accept "@", so I replaced "@" with "+" and then translated "+" back to "@" using the bizarre digit map.
ianobi:
Mango,
It all makes sense if you read posts concerning using CSipSimple with OBi and using any OBI as a home PBX. Each idea just adds a little to the complexity!
Shale:
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.
Oleg posted
3/20/2013 2:19:10 AM INVITE sip:+972592280470@12.34.56.78:5078 SIP/2.0
3/20/2013 2:19:14 AM INVITE sip:0972592280470@12.34.56.78:5078 SIP/2.0
3/20/2013 2:19:14 AM INVITE sip:00972592280470@12.34.56.78:5078 SIP/2.0
3/20/2013 2:19:17 AM INVITE sip:000972592280470@12.34.56.78:5078 SIP/2.0
3/20/2013 2:19:17 AM INVITE sip:0000972592280470@12.34.56.78:5078 SIP/2.0
3/20/2013 2:19:20 AM INVITE sip:00000972592280470@12.34.56.78: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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page