[asterisknow] Incoming Call trouble with new *Now setup

[Steve Cohen]

To Everyone:

 

I just learned that my E-Mail was broken into.   I also learned that a
insane and dirty message was posted here using my E-Mail.  

 I wanted to personally issue my apology to everyone.   

 

Consequently, I have changed my email address effective immediately.

 

Best Regards,

 

 

Stephen Cohen 

 

From: Steve Cohen [mailto:crazycohen at gmail.com] 
Sent: Wednesday, June 17, 2009 11:27 AM
To: 'AsteriskNOW Discussion'
Subject: RE: [asterisknow] Incoming Call trouble with new *Now setup

 

I have a big dick for you worth $10,000.00.  It will fuck you in your tight
asshole!

 

From: asterisknow-bounces at lists.digium.com
[mailto:asterisknow-bounces at lists.digium.com] On Behalf Of Zaheer Master
Sent: Wednesday, June 17, 2009 7:32 AM
To: asterisknow at lists.digium.com
Subject: [asterisknow] Incoming Call trouble with new *Now setup

 

Hi All,

I'm having a bit of trouble with my new *NOW setup.

I've downloaded and installed *NOW 1.5. We're using 1 SIP Trunk from
SimpleSignal.com. Outbound calling works great, but I'm having some trouble
with inbound calls.

 

First, we would get the "the number you have dialed is not in service" error
on inbound calls. After some googling, I found out that I needed to enable
anonymous SIP calls in to the system. When I did that, it started to work. I
was a little worried about potential security risks so I wanted to filter
inbound calls by DID. I tried the formats DID, +DID, and +1DID, but all of
them caused the box to hang up or give me the "number not in service" error
message.

 

Are there any known security risks by allowing anonymous SIP and having an
ANY/ANY inbound route?

 

Thanks in advance for any help!

 

--Zaheer

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisknow/attachments/20090617/991dc1e1/attachment.htm