SIP scanners
kevin8629:
Quote from: ianobi on September 21, 2012, 12:52:13 am
kevin8629,
I guess you are making changes using the web page. Your changes are being over written by the OBi Portal. Read this:
http://www.obitalk.com/forum/index.php?topic=61.msg109#msg109
I suggest you use the OBi Portal via the expert pages at least until you get familiar with the OBi. Click on your OBi device on the Dashboard and follow prompts to get to the Expert Pages.
I'm going to assume you do changes from the portal via the expert pages. To make a change to a value uncheck both boxes to the right of that value, leave them unchecked, make your changes, then press submit and wait for the OBi to reboot. Each page needs a submit/reboot before you move to another page.
Thank your help and the link. I was able to make the changes and I think I learned a little too ;D
corporate_gadfly:
Quote from: ianobi on September 09, 2012, 11:37:47 pm
{(?|x|xx|xxx|xxxx|xxxxx|xxxxxx|un@@.|anon@@.):},{ph}
This will ban calls with no Peer Number, any Peer Number less than seven digits, Peer Number "unknown" and Peer Number "anonymous".
Sleep well :)
Thanks in advance for any replies.
I have an obi202. The default X_InboundCallRoute for obi202 is ph,ph2.
So, keeping in mind that it is an obi202 and with the added requirement to reject calls from 1-800 numbers ala {(1800xx.|1888xx.):}, what changes should I make?
Would something like be appropriate?
Code:
{(?|x|xx|xxx|xxxx|xxxxx|xxxxxx|un@@.|anon@@.):},{(1800xx.|1888xx.):},{ph,ph2}
Cheers,
ianobi:
corporate_gadfly,
Your format works fine, or you could just add to the original rule:
{(?|x|xx|xxx|xxxx|xxxxx|xxxxxx|un@@.|anon@@.|1800xx.|1888xx.):},{ph,ph2}
Each X_InboundCallRoute needs its own rule. The "standard" rule I proposed just happened to suit my set up. Looks like it is useful to lots of other OBi users, but be careful not to ban callers you might want to talk to.
flex25:
Thanks ianobi, I put your string in X_InboundCallRoute, and added 7, 8, and 9-digit numbers, because I am in a 10-digit calling area. I also changed X_UserAgentPort to 5070 for SP1 and 5071 for SP2. I tested at every step, and it all seems to be working.
Does anyone know if it is possible to use an even more obsure port in the SIP port range of 5060 to 5080, such as 5078 or 5067? Other users on this forum routinely recommend changing 5060 to 5070, but would any port number between 5060 and 5080 work? Also, do people using SIP scanners check the port range 5060-5080, or must they check one port at a time? If they can check a port range, it seems to me that they would check the full SIP range 5060-5080, and changing the port wouldn't stop them from ringing my phone.
Thanks. I am hopeful these changes will stop the SIP scanners.
QBZappy:
flex25,
Quote from: flex25 on October 19, 2012, 03:27:53 pm
Does anyone know if it is possible to use an even more obsure port in the SIP port range of 5060 to 5080, such as 5078 or 5067? Other users on this forum routinely recommend changing 5060 to 5070, but would any port number between 5060 and 5080 work?
I believe that X_UserAgentPort can be any port number you like. If you have ever looked at a sip trace you will be able to see ip:port number in the headers. You may need to test if you need port forwarding.
Sample wireshark trace (partial):
Eyebeam (Softphone) SUCCESSFUL
SUBSCRIBE sip:105@172.16.240.3:5080 SIP/2.0
Via: SIP/2.0/UDP 172.16.240.101:1614;branch=z9hG4bK-d8754z-3560f947510b5a43-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:105@172.16.240.101:1614> <----------- Note the softphone user agent port number
To: "100Eyebeam"<sip:105@172.16.240.3:5080>
From: "100Eyebeam"<sip:105@172.16.240.3:5080>;tag=df48580b
Call-ID: ZGQxMGRkOTUwMWNjMjljOGI5Yjk2N2RkZjNkMWUwMGE.
CSeq: 2 SUBSCRIBE
Expires: 300
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
User-Agent: eyeBeam release 1102q stamp 51814
Authorization: Digest username="105",realm="5024",nonce="0079de5c",uri="sip:105@172.16.240.3:5080",response="87e08ac88637156c4fd2a098157408fa",algorithm=MD5
Event: message-summary
Content-Length: 0
Navigation
[0] Message Index
[#] Next page
[*] Previous page