| Concerned With Call Log Hello,
I am new user to Voip.ms and in general to VOIP. I recently signed up with Voip.ms, got a DID and set it up in a new OBi100. Everything was looking pretty normal but then I checked the log in the device and noticed a couple of odd entries.
image upload
Should I be concerned? I am testing this out with a did available for my region before I port over my regular land line number. I know if I encounter problems at that point the wife will never let it down. If it is nothing major then that's fine. Just found it odd for a entry of that nature. |
|
|
|
 Adam4Premium
join:2011-05-30
Woodland Hills, CA | Those call records are "crack attempts" trying to access your ATA, trying to find a resource they can steal calls from. I know this from direct experience, as in the past, users on my system have gotten these "calls" from "asterisk".
The crackers are looking for VOIP servers. Your ATA is a VOIP client, but the crackers don't know that. All they know is that they see a VOIP protocol answering to the standard port like 5060.
But, because your ATA is a client and not a server, there is nothing on your client that the crackers can access and/or steal. For you, these crack attempts are safe and if anything, just a nuisance.
If the crack attempts become incessant and/or annoy you, you could try to change the port your ATA uses from 5060 to something else. I'm not sure, though, how this would affect how VoIP.ms interacts with you. You could try it experimentally and if VoIP.ms stops working, change it back. You could also try putting your ATA behind a firewall.
--
VoIP.ms - Callcentric - Sipgate - IPComms - UKDDI - Numbergroup |
|
| Thanks for the reply.
I do indeed have it behind a firewall (With ports forwarded) and I am running the latest firmware on the ATA.
The existence of the "attempts" is annoying, but am comforted by the fact that these entries aren't a result of a misconfiguration on my part.
I Guess I will keep a eye on it and hopefully they cease in the future.
Thank you. |
|
Adam4Premium
join:2011-05-30
Woodland Hills, CA | They may not cease, but it will probably be sporadic. If you could see the logs of the network activity, you'd probably see it's a different IP address every day, as one tries, fails, moves on, and then another comes in and tries...
--
VoIP.ms - Callcentric - Sipgate - IPComms - UKDDI - Numbergroup |
|
MZB
join:2010-11-25
Dunrobin, ON | reply to Adam4
said by Adam4:If the crack attempts become incessant and/or annoy you, you could try to change the port your ATA uses from 5060 to something else. I'm not sure, though, how this would affect how VoIP.ms interacts with you.
Just to note that there are no problems in using a port other than 5060 when communicating with voip.ms. (And it is probably a good idea to use a different port).
The only difference is in IP calling - when caller will have to explicitly specify the port number in the URI. |
|
Adam4Premium
join:2011-05-30
Woodland Hills, CA | said by MZB:there are no problems in using a port other than 5060 when communicating with voip.ms.
Good to know! Thanks!
I didn't know for sure as I don't use VoIP.ms on an ATA, I have VoIP.ms connected to my Asterisk box.
--
VoIP.ms - Callcentric - Sipgate - IPComms - UKDDI - Numbergroup |
|
