SIP URI calling is a massive security risk these days. Everybody out there with a SIP device that has 5060 port forwarded will realise this when there phone keeps ringing randomly in the middle of the night..

sbiddle: SIP URI calling is a massive security risk these days. Everybody out there with a SIP device that has 5060 port forwarded will realise this when there phone keeps ringing randomly in the middle of the night..

sbiddle: SIP URI calling is a massive security risk these days. Everybody out there with a SIP device that has 5060 port forwarded will realise this when there phone keeps ringing randomly in the middle of the night..

What's the solution?

Only allowing SIP access from your SIP proxy. Cisco/Linksys devices have an option called "restrict source IP", but this apparently doesn't work with 2talk.

SIP URI calling is a massive security risk these days. Everybody out there with a SIP device that has 5060 port forwarded will realise this when there phone keeps ringing randomly in the middle of the night..

SIP URI calling is a massive security risk these days. Everybody out there with a SIP device that has 5060 port forwarded will realise this when there phone keeps ringing randomly in the middle of the night..

Just out of curiosity... Why would that happen?

Because there are bots out there continually trying brute force SIP attacks. Unless you're fully aware of the implications and have adequate security policies in place you should never expose any SIP devices directly to the internet.

The other issue with not using something such as Restrict Source IP is that these bots will use your traffic allowance. I had some dealings with an iTalk customer a few months ago who had used several GB over the course of a week, all of which was a bot running a 24/7 attack against their Linksys VoIP router.