Any suggestions on encrypting the sip and rtp. I have done some googling on it. looks like it is not supported by most end point devices or service providers. But still your thoughts will be appreciated on this subject.<br>
<br><div class="gmail_quote">On Mon, Feb 28, 2011 at 6:13 PM, Rizwan Hisham <span dir="ltr"><<a href="mailto:rizwanhasham@gmail.com">rizwanhasham@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
You are right Terry. Sorry i did not describe full scenario before. Yes the users are remote with atas on port 5060. Attacks on the remote customers was my second guess. My network/system admin has already ruled out the implementation of VPN. In summary, we dont want to do anything on remote customer side. All kind of security and attck prevention techniques have to be implemented on the server.<br>
<br>Its comforting to hear someone say "they are harmless". But still i would like to know their next step of attack after "guessing/scanning". Or is it the only step?<br><br><div class="gmail_quote">
<div><div></div><div class="h5">On Mon, Feb 28, 2011 at 5:32 PM, Terry Brummell <span dir="ltr"><<a href="mailto:terry@brummell.net" target="_blank">terry@brummell.net</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="h5"><div link="blue" vlink="purple" lang="EN-US"><div>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">When he says “customers” I am assuming he means remote customers. It sounds like he is a reseller of telecom facilities to me. Which means his customers most likely have ATA’s with port 5060 forwarded to the ATA, or they are direct on the I’net.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">He has already set the ATA to only allow calls from the proxy server, so sounds like he has plugged the hole.</span></p><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">They are not ‘sniffing’ your traffic, they are guessing/scanning. That’s it, that’s all, no great conspiracy going on. They look for open 5060, then send SIP requests to it hopefully finding a badly implemented SIP solution to which they can dial through. Once they determine they cannot get through, the script will move on to the next sucker.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">You have a couple of options, which you could implement at *<b>each</b>* of your customers if you wanted. Set up a VPN, tunnel the SIP/RTP traffic through it. Set up IPTables at the customer to only allow SIP from your IP. Or, do what you have already done and forget about these idiots doing the scan, they are harmless at this point.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);">Vlans and DMZ for the server do no good as the attacks are being directed at the remote client side, not the server.</span></p>
<p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p><p class="MsoNormal"><span style="font-size: 11pt; color: rgb(31, 73, 125);"> </span></p><div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;">
<p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> <a href="mailto:asterisk-users-bounces@lists.digium.com" target="_blank">asterisk-users-bounces@lists.digium.com</a> [mailto:<a href="mailto:asterisk-users-bounces@lists.digium.com" target="_blank">asterisk-users-bounces@lists.digium.com</a>] <b>On Behalf Of </b>Ricardo Carvalho<br>
<b>Sent:</b> Monday, February 28, 2011 6:31 AM<br><b>To:</b> Asterisk Users Mailing List - Non-Commercial Discussion<br><b>Subject:</b> Re: [asterisk-users] asterisk security....again</span></p></div><div><p class="MsoNormal">
</p><div><p class="MsoNormal">Probably, you are receiving INVITE attacks from some tool like sipvicious. You should rearange your network to cover some inportant security issues.</p></div><div><p class="MsoNormal"> </p>
</div>
<div><p class="MsoNormal">The IP address of you server can be revealed in some unincrypted SIP signaling of some call through the Internet to/from your server's client, or simply by your client SRV record in the DNS, if you added it to his DNS.</p>
</div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Probably your network is exposed to the Internet. To address those situations, you can use a distinct VLAN to address SIP phones and you also can use port security at the switching ports where you connect your ATAs and phones. You should also deliver with tagging (802.1Q) that VLAN to those ATAs and phones. This should protect you from inside sniffers.</p>
</div><div><p class="MsoNormal">This VLAN should just communicate with the DMZ where you should have your asterisk server and between those two networks you should only open the needed ports - for a common SIP infrastructure you should open UDP 5060 and the specified UDP range shown in rtp.conf file for the media to pass. Phones VLAN should not communicate directlly with the world, just in the outbound direction if you like. </p>
</div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">Regards,</p></div><div><p class="MsoNormal">Ricardo Carvalho.</p></div><p class="MsoNormal"> </p><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">
</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal" style="margin-bottom: 12pt;"> </p><div><p class="MsoNormal">On Mon, Feb 28, 2011 at 10:33 AM, Rizwan Hisham <<a href="mailto:rizwanhasham@gmail.com" target="_blank">rizwanhasham@gmail.com</a>> wrote:</p>
<p class="MsoNormal">Hi all,<br>The problem I have been experiencing since last month is that some of my customers are getting calls with "Asterisk <Unknown>" caller id. Most of them in the middle of the night. And my asterisk server has no record of these calls. The customers were getting irritated as you can imagine. I guessed the only way to receive incoming calls by by-passing the registration server is thru sip-uri calls directly to customers. I have updated the customers atas to not accept any calls from sources other than the registration server. Thats all fine now. But the question is how can anyone know the direct sip uri addresses of our customers.<br>
<br>My guess is that someone has been sniffing my server's sip traffic. In that case what should i do to get rid of the sniffers?<br><br>If you think there is another reason for that then please tell me even if you dont have the solution.<br>
<br>Thanks<br><span style="color: rgb(136, 136, 136);"><br>-- </span></p><div><p class="MsoNormal"><span style="color: rgb(136, 136, 136);">Best Ragards</span></p></div><div><p class="MsoNormal"><span style="color: rgb(136, 136, 136);">Rizwan Qureshi</span></p>
</div><div><p class="MsoNormal"><span style="color: rgb(136, 136, 136);">VoIP/Asterisk Engineer</span></p></div><div><p class="MsoNormal"><span style="color: rgb(136, 136, 136);">Axvoice Inc.</span></p></div><div><p class="MsoNormal">
<span style="color: rgb(136, 136, 136);">V: +92 (0) 3333 6767 26</span></p></div><div><p class="MsoNormal"><span style="color: rgb(136, 136, 136);">E: <a href="mailto:rizwanhasham@gmail.com" target="_blank">rizwanhasham@gmail.com</a></span></p>
</div><div><p class="MsoNormal"><span style="color: rgb(136, 136, 136);">W: <a href="http://www.axvoice.com/" target="_blank">www.axvoice.com</a></span></p></div><p class="MsoNormal"><span style="color: rgb(136, 136, 136);"><br>
<br></span></p></div><p class="MsoNormal"> </p></div></div></div></div><br></div></div><div class="im">--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br></div></blockquote></div><br><br clear="all"><br>-- <br><div><div></div>
<div class="h5"><font color="#888888"><div>
Best Ragards</div><div>Rizwan Qureshi</div><div>VoIP/Asterisk Engineer</div><div>Axvoice Inc.</div>
<div>V: +92 (0) 3333 6767 26</div><div>E: <a href="mailto:rizwanhasham@gmail.com" target="_blank">rizwanhasham@gmail.com</a></div><div>W: <a href="http://www.axvoice.com/" target="_blank">www.axvoice.com</a></div></font><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><font color="#888888"><div>Best Ragards</div><div>Rizwan Qureshi</div><div>VoIP/Asterisk Engineer</div><div>Axvoice Inc.</div>
<div>V: +92 (0) 3333 6767 26</div><div>E: <a href="mailto:rizwanhasham@gmail.com" target="_blank">rizwanhasham@gmail.com</a></div><div>W: <a href="http://www.axvoice.com/" target="_blank">www.axvoice.com</a></div></font><br>