I'm using Asterisk with 2Talk. All outgoing calls work great. However, for incoming 028 calls I am geting very inconsistent results. Sometimes the connection is made and the receiving phone rings, but more often than not, the call goes directly to 2Talk voicemail after a few seconds of silence. There is no evidence in the Asterisk logs indicating tht it had received anything from 2Tlk, so I suspect that 2Talk for whatever reasons thinks that my connection is down. Anyone else ever had this problem?
Yes, there does appear to be blocking of incoming SIP requests from the 2Talk IP address. It was my understanding, maybe wrong, that 2Talk didn't require the opening of 5060 for incoming connection requests as the connection would be constantly "kept alive" once registered. For Asterisk, I'm using the default settings as suggested by 2Talk. Namely: registerattempts=0 registertimeout=20
It doesn't typicaloly require any ports to be opened. But the issue you're seeing is one typically experienced when NAT firewalls do block incoming requests.
Opening port 5060 exposes your Asterisk box to the whole wide world. Don't do this under any circumstances unless you're fully aware of the security implications. If you're running iptables and Fail2ban which are essential for any Asterisk install these days you will be reasonably well protected.
Been a while but thought I'd provide an update on how it looks like I resolved my issue. Since I couldn't amend the keepailve time for incoming UDP SIP on my firewall, I changed over to 2talk+ which allows for TCP SIP. Once I changed my 2talk settings to use TCP SIP and changed my Asterisk configuration settings to use TCP SIP, all incoming calls (so far) are getting through. We'll see what happens, but so far so good.
Twitter and LinkedIn »
Follow us to receive Twitter updates when new discussions are posted in our forums: