Mysterious Incoming Calls

<< < (2/2)

RonR:
Quote from: pgde on March 19, 2012, 09:32:27 pm

Newbie here -- could this work for Anveo -- i.e. substitute anveo_ip_address for voip.ms_ip_address?


Yes.

pgde:
Quote from: RonR on March 19, 2012, 10:26:00 pm

Quote from: pgde on March 19, 2012, 09:32:27 pm

Newbie here -- could this work for Anveo -- i.e. substitute anveo_ip_address for voip.ms_ip_address?


Yes.



Thanks, I'll try it.

Peter

MB..:
Quote from: RonR on March 15, 2012, 12:00:35 pm

It's likely SIP scanners probing your OBi.

You don't need to remove your port forwarding.  Simpy set:

Voice Services -> ITSP Profile A -> SIP -> X_AccessList : voip.ms_ip_address

Then, only Voip.ms will be permitted in.  If you need to allow others, such as SIP URI callers or incoming DID's, simply add their IP addresses to the list (separated by commas).



One thing to watch out here: if a voip.ms server goes down, they will reroute calls via a different server. So you should probably add a comma-separated list of all the voip.ms server IP addresses for greatest reliability.

The SPA2102 has an option to only allow calls from the server you a registered to. I don't know if there's an equivalent on the Obi. 

Not being on port 5060 if you don't have a published sip URI is definitely a good idea. You can get an idea of the number of probes on this port by looking at the SANS Internet Storm Center here: http://isc.sans.edu/port.html?port=5060

Navigation

[0] Message Index

[*] Previous page