{"action":"opened","issue":{"url":"https://api.github.com/repos/davehorton/drachtio-server/issues/38","repository_url":"https://api.github.com/repos/davehorton/drachtio-server","labels_url":"https://api.github.com/repos/davehorton/drachtio-server/issues/38/labels{/name}","comments_url":"https://api.github.com/repos/davehorton/drachtio-server/issues/38/comments","events_url":"https://api.github.com/repos/davehorton/drachtio-server/issues/38/events","html_url":"https://github.com/davehorton/drachtio-server/issues/38","id":335050632,"node_id":"MDU6SXNzdWUzMzUwNTA2MzI=","number":38,"title":"NAT handling","user":{"login":"JimG777","id":20444071,"node_id":"MDQ6VXNlcjIwNDQ0MDcx","avatar_url":"https://avatars3.githubusercontent.com/u/20444071?v=4","gravatar_id":"","url":"https://api.github.com/users/JimG777","html_url":"https://github.com/JimG777","followers_url":"https://api.github.com/users/JimG777/followers","following_url":"https://api.github.com/users/JimG777/following{/other_user}","gists_url":"https://api.github.com/users/JimG777/gists{/gist_id}","starred_url":"https://api.github.com/users/JimG777/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JimG777/subscriptions","organizations_url":"https://api.github.com/users/JimG777/orgs","repos_url":"https://api.github.com/users/JimG777/repos","events_url":"https://api.github.com/users/JimG777/events{/privacy}","received_events_url":"https://api.github.com/users/JimG777/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-06-23T00:14:39Z","updated_at":"2018-06-23T00:14:39Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"Up till now, I have done lots of testing with drachtio-server running in a Docker network along with my other services. External clients could come in and access the server, but it was all enclosed by a private network.\r\n\r\nNow I am trying to deploy the Docker setup to AWS. However, when I run drachtio-server in a Docker network on an AWS EC2 instance, I can't getting NATing working correctly. The drachtio-server can't reach my clients. I even tries running drachtio-server directly on an AWS EC2 instance, but it has the same results. The log below is this case without Docker.\r\n\r\n[drachtio.txt](https://github.com/davehorton/drachtio-server/files/2129447/drachtio.txt)\r\n\r\nIn this example, my client REGISTERs, sends a SUBSCRIBE, and sends a PUBLISH. We get the 200 OK responses back for both of those. However, the NOTIFY we send from the Node.js/srf side doesn't reach the client. This is after the fix from before where we now send the NOTIFY after the 200 OK is successfully sent (it works well in the private network scenario).\r\n\r\nIn the log, 5.5.5.5 is the public IP from my office and 10.11.33.* is the private IP range. 222.222.222.222 is the public IP of the AWS EC2 instance and 10.0.3.* is the private IP range there.\r\n\r\nWhen I send the NOTIFY with the drachtio-srf object, I am using the received and rport parameters from the via[0] line (5.5.5.5:5070). But from the logs it looks like drachtio-server is trying to send to the private IP of my office network."}}
{"actor":{"display_login":"JimG777"}}