I just ran a report from
Security report for fqdn created Wed, January 18 2017, 17:33 UTC
0 SIP services detected
0 Extensions found
0 Passwords cracked
Yes, I have fail2ban running. But, this would, I think, explain why I cannot register a SIP device to this server:
Does AWS do something out-of-the-box with regards to firewalls? I don’t recall reading anything along those lines. I’m using an EIP (Elastic IP) so that the FQDN maps with DNS to the IP address for the server. When I SSH, I just type in the FQDN and the rest happens automagically (DNS resolution, and the pub key is sent for authentication).
Not even sure how to proceed. Can I prod the server somehow with a networking tool?
From within the Asterisk console, I can see the trunking peer, they show as “ok” and “sip show registry” shows the registry string with a state of “registered”. So far as I can tell from within the server everything works fine.
Can I send a message, poke, or prod, from the server to a device? However, any such device would be behind NAT…
so probably better to poke and prod the server. But, how? What could possibly be wrong?