HOWTO: Thwarting SIP Scanners during Set-up
azrobert:
Quote from: SSmith on June 30, 2014, 01:12:18 pm
>('AuthUserName'):ph
syntax.
It makes sense from the Admin guide that an all-numeric AuthUserName would not require the parentheses and hyphens but an alpha-numeric one would. Presumably, the hyphens would not be necessary if the AuthUserName did not include any reserved characters but mine does.
I believe you are wrong and TonyC is correct.
{>('AuthUserName'):ph}
When you enclose the string in parentheses (like above rule) it becomes a DigitMap. In a DigitMap reserved characters must be enclosed in quotes if you don't want to use them as reserved characters, so what you coded is a correct syntax.
Here is where you are wrong:
When you don't enclose the string in parentheses like this:
{>AuthUserName:ph}
The string becomes a literal and all characters including reserved characters are valid without quotes.
InsanitySix:
The cheapskate that I am.. I bought a newer Obi100 and use Ring.To (from a GrooveIP account I had) and Anveo e911. Except for the almost immediate SIP scanner issue, it all works better than it should (pretty much perfectly). Actually I manly did it for a spare line for my kids when they are home and we are out so we can take both of our cell phones with us.
So because of that I really didn't need more. We still use our cells as our primary lines.
ANYWAY. The setup that Obihai does automagically for this is the Oleg #4 for Anveo e911 (SP2) but not for ring.to! It was port 5060 and {ph} for SP1.
So for the last two months or so I been fine with the {?|x|xx|xxx...} method. But this morning "AS100" kept calling.. ;) So I did block that string and also changed the ports to a high random for both SP1/Ring.to and SP2/Anveo e911.
The AuthUserName for ring.to is a string like the following "ringto_user_12345". What's the proper method of using Oleg's#4 with this string? Could I and should I combine it with the {?|x|xx|xxx} method as well? This might, for instance be handy for whomever with otherwise legit numbers I want to put right to Ringto voicemail.
Thanks much..
The Crazy One.
Mango:
Set the following as your (Voice Services) SPn Service->X_InboundCallRoute
Only accept calls destined for your AuthUserName:
{>('ringto_user_12345'):ph}
Reject calls with specific Caller ID numbers, accept all other calls destined for your username: (note this is one of multiple ways to do this)
{(2064560661|9052811282|8888001250):},{>('ringto_user_12345'):ph}
Taoman:
Quote from: Mango on August 10, 2014, 07:14:02 am
{(2064560661|9052811282|8888001250):},{>('ringto_user_12345'):ph}
Thanks for this info. Didn't realize you could combine the Oleg method with individual numbers you wanted to block. However, the syntax you used wouldn't work for me. I had to remove the ":" after the numbers that I wanted blocked in order for it to work. I assume you made a typo or should it actually work the way you have it listed? Thanks.
Mango:
Actually that wasn't a typo. What I posted was based on the rule at http://www.obihai.com/docs/OBiDeviceAdminGuide.pdf, at the bottom of page 194. However, as long as what you are doing works, then that's just fine. :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page