September 26, 2018, 04:14:42 am *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: 1 ... 7 8 [9] 10
  Print  
Author Topic: SIP scanners  (Read 776293 times)
ianobi
Hero Member & Beta Tester
*****
Posts: 1828


« Reply #160 on: February 04, 2014, 04:41:49 am »

Quote
Here is a trick you can do to determine the username.
Temporarily add {sp1($2)} to the beginning of your SP2 X_InboundCallRoute, then call your SP2 phone number.

That is a neat trick. I'm filing that one away for future use ...   Smiley
Logged
giqcass
Hero Member & Beta Tester
*****
Posts: 1437


« Reply #161 on: February 04, 2014, 06:01:14 am »

Quote
Here is a trick you can do to determine the username.
Temporarily add {sp1($2)} to the beginning of your SP2 X_InboundCallRoute, then call your SP2 phone number.

That is a neat trick. I'm filing that one away for future use ...   Smiley
I saved it to my file already. lol
Logged

Register at e164.org and friends can use Sipbroker to call you from a regular telephone for free from almost any country.
DDNS hack for OBi
Old OBi? Want Ring.to?
Rick
Hero Member
*****
Posts: 1006


« Reply #162 on: May 14, 2014, 12:56:20 pm »

I've now setup Callcentric on both SP1 and SP2 on my 110.  I got 2 free DIDs, and setup GV to forward my two numbers, one to each of them.  Works great.

Then, I setup SP2 with the {>1777xxxxxxx:ph} and it worked fine.

I now want to setup SP1 also.  Since it uses an extension, it's 1777xxxxxxx101.  I tried that, and nothing comes through (this is the peer number displayed in history).  I tried using it without the extension, and nothing comes through, which doesn't surprise me. 

Ideas welcome.
Logged
azrobert
Hero Member & Beta Tester
*****
Posts: 3568


« Reply #163 on: May 14, 2014, 01:23:13 pm »

Check my post here:
http://www.obitalk.com/forum/index.php?topic=4067.msg46145#msg46145
Logged
Rick
Hero Member
*****
Posts: 1006


« Reply #164 on: May 14, 2014, 02:06:06 pm »

I read that (earlier in the thread), tried it, but got nothing new.  Perhaps I was doing it wrong.  If SP2 works today and is setup just fine, and SP1 is just plain PH, I change that to:

{sp2($2)}:ph    ?

I want to discover what to put in the SP1 X_Inbound Call Route.

Thanks!
Logged
Shale
Hero Member
*****
Posts: 1061


« Reply #165 on: May 14, 2014, 03:31:04 pm »

If SP2 works today and is setup just fine, and SP1 is just plain PH, I change that to:

{sp2($2)}:ph    ?

I want to discover what to put in the SP1 X_Inbound Call Route.

Thanks!
I am thinking that would be
{sp2($2)},{ph}
Logged
Rick
Hero Member
*****
Posts: 1006


« Reply #166 on: May 15, 2014, 12:43:02 pm »

What that shows me is the Callcentric number with the extension after it, and when I used that it didn't ring at all. 

I guess I'll worry about it when I start getting callers in the middle of the night on that line.
Logged
azrobert
Hero Member & Beta Tester
*****
Posts: 3568


« Reply #167 on: May 15, 2014, 01:01:42 pm »

Try:
{>(1777xx.):ph}
Logged
Rick
Hero Member
*****
Posts: 1006


« Reply #168 on: May 15, 2014, 01:08:38 pm »

Thanks, that worked (i.e. call came through).

So that restricts it to receiving Callcentric calls only, correct?  Appreciate it.

Now I have to figure out how to setup a Voice Gateway for all my outbound calls to automatically use the gateway, not SP1 or SP2  Smiley
Logged
Shale
Hero Member
*****
Posts: 1061


« Reply #169 on: May 19, 2014, 07:51:11 am »

Thanks, that worked (i.e. call came through).

So that restricts it to receiving Callcentric calls only, correct?  Appreciate it.

Now I have to figure out how to setup a Voice Gateway for all my outbound calls to automatically use the gateway, not SP1 or SP2  Smiley
Depends on what you mean by a Callcentric call. Non-Callcentric users will be able to dial your phone number that is served by Callcentric.

Regarding gateway, set it up to test first.

On phone OutboundCallRoute, I think that is processed left to right. So if you add {(Mvg1):vg1}, after your 911 processing and after your **1, **2 etc processing, and before other things that you want to have less precedence, then if the number matches the DigitMap for VG1, then the number will be sent out on the VG1 service. If it does not, then the next thing in the routing will be processed. The last thing in the OutboundCallRoute would normally be ,{(Mpli):pli} -- so that things that don't match the special cases go out on the Primary Line.

If VG1 were a choice for your Primary Line, you could just select that. It looks like you could maybe put VG1 into a trunk group and make that the Primary. I have not tried trunk groups.


Logged
Rick
Hero Member
*****
Posts: 1006


« Reply #170 on: May 19, 2014, 10:45:04 am »

I guess I have to set aside a few hours to get this done.  Basically I want 911 and 933 to go out on SP2, and ANY OTHER CALL to go out on a Voice Gateway that I'll set up with a cheap outbound service.  So the Outbound Call Route should be fairly short and simple.
Logged
pvpham
Jr. Member
**
Posts: 42


« Reply #171 on: July 01, 2014, 08:04:21 am »

Hi,

Due to my ignorance, I totally lost reading these post. I would like to implement Oleg's method to block Sip scanner.
 
I currently have PhonePower on Sp1, CallCentric on Sp2.

My X_InboundCallRoute is now like this: {my_CC_ID>(Msp1):sp1},{101>1777xxxxxxx:aa},{ph}

I recalled the above setting is to ring my cell phone .

How do I implement the Oleg's string to my X_InboundCallRoute .

Thanks
Logged
DPMc
Newbie
*
Posts: 2


« Reply #172 on: December 18, 2015, 07:15:09 am »

Dear ObiHai,

I can not find the way to make the change as outlined in part 2 of the instructions on the first post in this page. Would you please tell me where to find it on the ObiTalk 100?

2. A more fool-proof method is to enable the parameter: X_EnforceRequestUserID. This parameter is under SPn in the SIP Credentials section.   What this does, is it makes sure the incoming INVITE has a User ID that matches the User ID of your SIP service account. If it does not match, the INVITE will be rejected and the phone will not ring.  Enabling this parameter will maintain normal voice service as well as block SIP scanners. Notes:  Some service providers do not adhere to this rule. This parameter is not available on the OBi100 and OBi110 devices.
http://www.obitalk.com/obinet/pg/obhdev/config/2251269/advcfg_VS_1_VP_1_L_1_?inst=1


2. A more fool-proof method is to enable the parameter: X_EnforceRequestUserID. This parameter is under SPn in the SIP Credentials section.   What this does, is it makes sure the incoming INVITE has a User ID that matches the User ID of your SIP service account. If it does not match, the INVITE will be rejected and the phone will not ring.  Enabling this parameter will maintain normal voice service as well as block SIP scanners. Notes:  Some service providers do not adhere to this rule. This parameter is not available on the OBi100 and OBi110 devices.[/color]

[End: Obihai Support Response]
 

[/quote]
Logged
Mango
Hero Member
*****
Posts: 548


« Reply #173 on: December 18, 2015, 07:57:54 am »

X_EnforceRequestUserID is a feature not available on the OBi1 series.  For the same behaviour, set your SPx Service X_InboundCallRoute to: {>Insert your AuthUserName here:ph}

However, I disagree that this is a "more fool-proof method".  With this method, the OBi will still accept, then reject the scanning traffic, indicating to a hacker that a device is present.  If one day someone finds an exploit in OBi devices, all devices using this method will be hacked fairly quickly and most likely used to make expensive long distance calls.

The best way to prevent SIP scanners is with a firewall.  In this case, the hacker will have no indication that VoIP equipment exists.  Never use port forwarding or DMZ with any VoIP equipment as this disables your firewall.  If you don't use port forwarding or DMZ and still receive scanning calls, you should consider replacing your router with a more secure one, such as any router with Tomato firmware: http://tomato.groov.pl/?page_id=69
« Last Edit: December 18, 2015, 08:01:33 am by Mango » Logged

ScottS
Newbie
*
Posts: 12


« Reply #174 on: February 10, 2018, 03:11:41 pm »

Hi, where is this setting in the Obi302> "EnforceRequestUserID" ?

A more fool-proof method is to enable the parameter: X_. This parameter is under SPn in the SIP Credentials section.   What this does, is it makes sure the incoming INVITE has a User ID that matches the User ID of your SIP service account. If it does not match, the INVITE will be rejected and the phone will not ring.  Enabling this parameter will maintain normal voice service as well as block SIP scanners. Notes:  Some service providers do not adhere to this rule. This parameter is not available on the OBi100 and OBi110 devices.[/color]

[End: Obihai Support Response]
 

Logged
Taoman
Hero Member
*****
Posts: 1130


« Reply #175 on: February 10, 2018, 03:45:58 pm »

Hi, where is this setting in the Obi302> "EnforceRequestUserID" ?


I only have the 1xx and 2xx series but I assume it would be in the same location:

Voice Services-->SPx Service-->SIP Credentials
Logged
ScottS
Newbie
*
Posts: 12


« Reply #176 on: February 12, 2018, 03:08:28 pm »

yes TY! obiTalk parameter was unchecked by me.

found Inbound routing unchecked both and edited to block
& Have been using back up feature.
IF both Inbound routing boxes unchecked, it appears that line is not saved. I searched in wordpad but not found.
so started a text file to save that line.
What else should I do? I have several backups now JIC.  
TY!
« Last Edit: February 12, 2018, 03:28:49 pm by ScottS » Logged
Taoman
Hero Member
*****
Posts: 1130


« Reply #177 on: February 12, 2018, 05:39:00 pm »


What else should I do? 


Voice Services-->SPn Service-->X_AcceptSipFromRegistrarOnly

Check the box for that parameter.
Logged
ScottS
Newbie
*
Posts: 12


« Reply #178 on: April 02, 2018, 11:35:48 am »

Phonepower list setup 
Click the Enter OBi Expert button.
Click to enlarge
On the left hand side of the new page, expand the menu for Service Providers by clicking on it.
Click to enlarge
Click on ITSP Profile A SIP.
Click to enlarge
Scroll down until you see the section for X_AccessList.
Click to enlarge
Click the box on the checked box on the far right to uncheck the box.
In the text entry box to the right of "X_AccessList" please enter

    208.64.8.6,206.15.130.6,206.15.150.6

Works on my Obii302s w/ latest firmware

Is there a way of preventing SIP scanners from ringing my phone at night?....
...
« Last Edit: April 02, 2018, 11:40:55 am by ScottS » Logged
flamaest@gmail.com
Newbie
*
Posts: 6


« Reply #179 on: May 27, 2018, 12:44:48 pm »

Phonepower list setup 
Click the Enter OBi Expert button.
Click to enlarge
On the left hand side of the new page, expand the menu for Service Providers by clicking on it.
Click to enlarge
Click on ITSP Profile A SIP.
Click to enlarge
Scroll down until you see the section for X_AccessList.
Click to enlarge
Click the box on the checked box on the far right to uncheck the box.
In the text entry box to the right of "X_AccessList" please enter

    208.64.8.6,206.15.130.6,206.15.150.6

Works on my Obii302s w/ latest firmware

Is there a way of preventing SIP scanners from ringing my phone at night?....
...

Can we please get these steps detailed for an OBIHAI 202 which is just using GVoice?  I turned off DMZ on my router and I still see {much less} phantom calls come in, but the ones that make it through into the obihai are sometimes at 2 or 3 am!  I am about to toss this thing in the garbage. 
Logged
Pages: 1 ... 7 8 [9] 10
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC