Publish brekeke sip server not work over internet just local

1. Brekeke Product Name and Version: 3.6.2.2 Evaluation

2. Java version: 1.8

3. OS type and the version: Windows server 2012

4. UA (phone), gateway or other hardware/software involved:

5. Your problem:

I have installed brekeke sip server (on Amazon server EC2) and run on local (127.0.0.1) successfully. I goto web browser with 127.0.0.1:18080 or 172.31.26.163:18080 successful (local IP).
But, I can not goto browser with my static public IP.
I have create new some Inbound and outbout for port 5060 and 18080 in firewall of windows.
I have changed 18080 to 91 to test port, but, it is not working too.

I also have installed openfire and have some .jsp, and it can be access over internet.

Please tell me why and show me how to solve my problem.
Thanks.
ThienVu

Did you set 18080 and 5060 in EC2's [Security Group]->[Inbound] ?

Even so, you can not access to the Brekeke SIP Server's web page?

Thanks!
Yes, I have set 18080 5060 on Inbound and Outbound, but I can not access to Brekeke SIP Server's Webpage over public IP Address.

> I also have installed openfire and have some .jsp, and it can be access over internet.

Is it running on the same Tomcat on the port 18080?

Of course not, openfire running on 9090 and 9091.
Brekeke Sip server running on 18080 and 5060.

I have a friend build on other same hosting EC2, and I have compared configuration, PC,... almost the same. But my friend's Brekeke Sip server running ok (and my friend use Brekeke 3.3.4.4 and user licence, my brekeke 3.6.2.2 and use evaluation licence 60 days trial).

Thanks.

If you access to the URL without "sip", can you see the Tomcat page?

For example:
http://<public-IP>:18080/

Does the browser show any error message?

When I access public IP with port of Tomcat, I also can not access.
I have try on the other PC and public IP I own (from the other ISP - internet service provider), it runs successfully.
I think that the reason maybe about configuration on PC or on gateway of AWS hosting.
Thanks.

If you run Wireshark in Windows on EC2, can you see packet activities on the TCP port 18080?