# Streaming via other methods beside port 1935

**URL:** <https://community.wowza.com/t/streaming-via-other-methods-beside-port-1935/35501>\
**Category:** Wowza Streaming Engine\
**Created:** [October 8, 2010, 2:04pm UTC](https://community.wowza.com/t/streaming-via-other-methods-beside-port-1935/35501 "2010-10-08T14:04:26Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jason\_Stobbe](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@Jason\_Stobbe](https://community.wowza.com/u/Jason_Stobbe)\
**Post date:** [October 8, 2010, 2:04pm UTC](https://community.wowza.com/t/streaming-via-other-methods-beside-port-1935/35501/1 "2010-10-08T14:04:26Z")

</div>

I have come across some issues streaming a live stream into some corporate firewalls. I’ve been looking into the RTMP protocol a bit more and it doesn’t even exist as standard option to disable in many corporate firewalls. It can bemanually added, however it appears that there are 3 ways to send RTMP:

1. Standard port: 1935 will likely be blocked by a lot of firewalls.

2. Encapsulated (Embedded, Tunnelled) port: 80 no issues – This embedded version goes over the http and would be open in almost any firewall. Then it is just a URL issue, not a potential port problem.

3. Encrypted SSL port: 443 no issues but would need a cert on the embedded website or more likely the originating stream site.

Is there any way to send the stream from EC2 via Encapsulated RTMP?

Thanks!

---

<div class="post-metadata">

**Author:** ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)\
**Post date:** [October 8, 2010, 8:57pm UTC](https://community.wowza.com/t/streaming-via-other-methods-beside-port-1935/35501/2 "2010-10-08T20:57:22Z")

</div>

Yes, EC2 already has port 80 configured, so you just need to use RTMPT protocol:

> **RTMPT** ://[wowza-address]/[app-name]

Richard

---

<div class="post-metadata">

**Author:** ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)\
**Post date:** [October 12, 2010, 5:20pm UTC](https://community.wowza.com/t/streaming-via-other-methods-beside-port-1935/35501/3 "2010-10-12T17:20:47Z")

</div>

I think you posted to support regarding this issue. (btw, same crew, me answering there too)

Richard

---

<div class="post-metadata">

**Author:** ![Jason\_Stobbe](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@Jason\_Stobbe](https://community.wowza.com/u/Jason_Stobbe)\
**Post date:** [October 12, 2010, 10:25am UTC](https://community.wowza.com/t/streaming-via-other-methods-beside-port-1935/35501/4 "2010-10-12T10:25:05Z")

</div>

Richard,

Thanks for your response. I thought it would be simple enough. I changed both my broadcasting and embedded links.

I changed from

```auto
rtmp://ec2-xxx-xx-xxx-234.compute-1.amazonaws.com/live

```

to

```auto
rtmpt://ec2-xxx-xx-xxx-234.compute-1.amazonaws.com/live

```

By reading your response, it seems all I need to do is change the rtmp to rtmpt, but i get a “stream not found” response.

I’ve looked elsewhere, and it seems there is more I could do if I had access to my wowza server, but it is not so when streaming from AMAZON EC2.

I could show you the exact config thru a PM, if you wish.

---

<div class="post-metadata">

**Author:** ![Jason\_Stobbe](https://avatars.discourse-cdn.com/v4/letter/j/ee59a6/32.png) [@Jason\_Stobbe](https://community.wowza.com/u/Jason_Stobbe)\
**Post date:** [October 12, 2010, 1:13pm UTC](https://community.wowza.com/t/streaming-via-other-methods-beside-port-1935/35501/5 "2010-10-12T13:13:56Z")

</div>

Thank you Richard. Turned out to be a simple issue: enabling TCP port 80 in my default security settings in the amazon console.