Getting constant "calls" from 100 and 10001
drgeoff:
Quote from: Sheffield_Steve on January 03, 2019, 08:20:50 am
Sorry, It's NOT required to have port 5060 open on your router for incoming calls unless you have a SIP phone system.
The Obi or other SIP software on devices such as phones makes and keeps an outgoing connection open on that port. Having any port open on your router for incoming traffic is a big security risk.
You are agreeing with me.
Sheffield_Steve:
I'm not sure how!
You are saying the port needs to be open on the router, I'm saying it doesn't and shouldn't be.
drgeoff:
Quote from: Sheffield_Steve on January 03, 2019, 08:56:57 am
I'm not sure how!
You are saying the port needs to be open on the router, I'm saying it doesn't and shouldn't be.
That port needs to be open on the router. The OBi (or other SIP ATA) does that by means such as sending keep alive messages, periodic registration messages etc to the ITSP.
Sheffield_Steve:
But it still does NOT require that you open the SIP ports on the router for incoming connections, as the ITSP doesn't connect back TO the Obi device (or any other SIP client) using the typical SIP ports (5060,5061).
The way it works is as follows:
a) The Obi client firmware opens a random high port on it's hardware (NOT 5060 or 5061). Lets say it's 11111 for this example
b) It then initiates and makes an OUTBOUND connection to the SIP port (5060, or 5061 usually) on the ITSP's server. Let's say it's 5060 for this example.
c) If it succeeds, the ITSP server software opens a random high port on it's hardware. Lets say it's 22222 for this example
d) Then, the ITSP and the Obi negotiate a random ephemeral port for the connection for the ITSP to the Obi. (Lets say they chose 33333)
So in this EXAMPLE, the connections are as follows:
Obi's port 11111 is connected to the ITSP server's port 5060
ITSP's port 22222 is connected to the Obi's port 33333
i.e. At no point is a SIP port (5060, or 5061) open or needed on the Obi hardware. (It's only open on the ITSP's server)
Thus, to get back to the OP, if they are getting phone spam and it's not coming via his phone ITSP's, then their Obi must have the SIP ports open and exposed to the internet.
ProfTech:
While checking "X_AcceptSipFromRegistrarOnly" can work, with some service providers it won't work. Some ITSP's send INVITE's from a different IP address than you are registered to and you won't get those calls. Another old fix for this has been around since the 100/110 days. Simply set Inbound call route to something like "{>1234567:ph},{?|@:}". Replace 1234567 with the user ID you have with your ITSP. Both the 200 & 202 have a check box specifically for this. If you have a 200 or 202 simply check X_EnforceRequestUserID. If the spammer doesn't know your sip user ID your phone won't ring.
*edited* If my memory serves me correctly, the user agent port for sp1 on the 100 series defaults to 5060 and sp2 defaults to 5061. I highly recommend changing both to another number [make sure both sp's use a different number]. I think this was corrected in the 200 series. Also, disable sp2-sp4 if they are not being used.
Navigation
[0] Message Index
[#] Next page
[*] Previous page