# mpeg2-ts h.264 for BrighSigns
**URL:** https://community.wowza.com/t/mpeg2-ts-h-264-for-brighsigns/37457
**Category:** Wowza Streaming Engine
**Created:** [March 5, 2014, 9:33am UTC](https://community.wowza.com/t/mpeg2-ts-h-264-for-brighsigns/37457 "2014-03-05T09:33:06Z")
**Posts on this page:** 12
**Page:** 1
### Author:  [@Ben\_Watson](https://community.wowza.com/u/Ben_Watson)
#### Post date: [March 5, 2014, 9:33am UTC](https://community.wowza.com/t/mpeg2-ts-h-264-for-brighsigns/37457/1 "2014-03-05T09:33:06Z")
We are using bright signs for our campus and want to stream to them. We use wirecast to push to an amazon ec2 feed (for our web feed). Does wowza output mpeg2-ts in h.264 codec on it’s rtsp feed? see link below:
[http://support.brightsign.biz/entries/22262919-What-Video-Streaming-Formats-Do-BrightSign-Players-Support-](http://support.brightsign.biz/entries/22262919-What-Video-Streaming-Formats-Do-BrightSign-Players-Support-)
I’ve also tried outputting straight from wire cast (local rtsp stream), but I’m not getting anything.
ANy help would be appreciated!
-Ben
---
### Author:  [@Daren\_Johnson](https://community.wowza.com/u/Daren_Johnson)
#### Post date: [March 5, 2014, 9:53pm UTC](https://community.wowza.com/t/mpeg2-ts-h-264-for-brighsigns/37457/2 "2014-03-05T21:53:47Z")
Hi,
There is a way to stream MPEG-TS using RTSP, there are properties discussed in [this article here](https://www.wowza.com/docs/how-to-generate-and-control-mpeg-ts-output-for-set-top-boxes) that enable
this.
According to your link, HLS is also supported.
Wowza can deliver HLS streams to supporting HLS players.
A typical URL would look like this:
```auto
http://[wowza-ip-address]:1935/live/myStream/playlist.m3u8
```
There’s more information [here](https://www.wowza.com/docs/how-to-playback-on-apple-ios-devices-cupertino-apple-hls%28Cupertino-Apple-HLS%29), on how to playback HLS streams for iOS and other supporting devices
Daren
---
### Author:  [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)
#### Post date: [March 19, 2014, 7:42pm UTC](https://community.wowza.com/t/mpeg2-ts-h-264-for-brighsigns/37457/3 "2014-03-19T19:42:42Z")
Ben,
The classic StreamManager is still there, but it uses port 8086:
```auto
http://[wowza-ec2-public-dns]:8086/streammanager/index.html
```
The default username is “wowza” and the password is the instanceid. You can change or add in /conf/admin.password file, or in the manager.
Richard
---
### Author:  [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)
#### Post date: [March 19, 2014, 8:09pm UTC](https://community.wowza.com/t/mpeg2-ts-h-264-for-brighsigns/37457/4 "2014-03-19T20:09:21Z")
Ben,
There must be some issue at your location, because I can reach both. I get the manager login page, and the StreamManager authentication challenge
Richard
---
### Author:  [@Daren\_Johnson](https://community.wowza.com/u/Daren_Johnson)
#### Post date: [March 18, 2014, 10:22pm UTC](https://community.wowza.com/t/mpeg2-ts-h-264-for-brighsigns/37457/5 "2014-03-18T22:22:42Z")
Hi,
You just need to add a Custom TCP Rule to your Security Group to open port 8088.
Once that’s open, if you you go to http://[YourEC2IPaddress]:8088
You’ll be Presented with the Wowza Streaming Engiine Manager intro page.
You can skip the intro if you wish and go to the login page.
Enter username: wowza
password: (yourAmazonInstance ID) \<- get this from your Amazon AWS console)
You should then be taken to the manager home page.
You can then configure, as Jason directed, from there.
Daren
---
### Author:  [@Jason\_Hilton](https://community.wowza.com/u/Jason_Hilton)
#### Post date: [March 18, 2014, 9:02am UTC](https://community.wowza.com/t/mpeg2-ts-h-264-for-brighsigns/37457/6 "2014-03-18T09:02:44Z")
Hi,
Be sure to restart after editing the application. If you’re using Wowza Streaming Engine 4, you can add these Properties using the Wowza Streaming Engine Manager.
You may need the correct permissions to add Properties, please take a look at the [Managing Sign-In credentials](https://www.wowza.com/docs/how-to-install-and-configure-wowza-streaming-engine#signinManager) in our Quick Start Guide.
The logging below will only appear when a RTSP client connects to Wowza after configured using Properties in the above MPEG-TS article.
```auto
comment server INFO 200 - RTPPacketizerMPEGTS.handleAMFPacket: mpegtsFlushEveryPacket:true
```
```auto
tc[0]: 2816:2816:48000
tc[0]: 2837:2837:48000
tc[0]: 2859:2859:48000
```
The Properties which log the above will need to be set as true for the logging to take place, they are both false by default.
Regards,
Jason
---
### Author:  [@Ben\_Watson](https://community.wowza.com/u/Ben_Watson)
#### Post date: [March 6, 2014, 10:08am UTC](https://community.wowza.com/t/mpeg2-ts-h-264-for-brighsigns/37457/7 "2014-03-06T10:08:13Z")
> Hi,
>
> There is a way to stream MPEG-TS using RTSP, there are properties discussed in [this article here](https://www.wowza.com/docs/how-to-generate-and-control-mpeg-ts-output-for-set-top-boxes) that enable
>
> this.
>
> According to your link, HLS is also supported.
>
> Wowza can deliver HLS streams to supporting HLS players.
>
> A typical URL would look like this:
>
> ```auto
> http://[wowza-ip-address]:1935/live/myStream/playlist.m3u8
>
> ```
>
> There’s more information [here](https://www.wowza.com/docs/how-to-playback-on-apple-ios-devices-cupertino-apple-hls%28Cupertino-Apple-HLS%29), on how to playback HLS streams for iOS and other supporting devices
>
> Daren
Yeah, after MUCH trial and error, I ended up using the HLS. It seems to work well for this application. I just wonder how it will fair during peak network hours.
I’ll be testing this weekend! Thanks for your help!
-Ben
---
### Author:  [@Ben\_Watson](https://community.wowza.com/u/Ben_Watson)
#### Post date: [March 17, 2014, 11:32am UTC](https://community.wowza.com/t/mpeg2-ts-h-264-for-brighsigns/37457/8 "2014-03-17T11:32:29Z")
It looks like this is not a viable option for us. The webstream stops playing sometime after 10 mins.
Here is our scenario: We use an Amazon Machine Image from wowzas website (launch Sun morn, terminate Sun afternoon), so our options are limited on forcing MPEG2-TS. Can this be done (using the [mentioned article above](https://www.wowza.com/docs/how-to-generate-and-control-mpeg-ts-output-for-set-top-boxes) ) with an devpay AMI? I wonder if we need to create our own AMI to launch each weekend? This is getting a little over my experience level, but def up for the challenge…
TIA.
-Ben
---
### Author:  [@Ben\_Watson](https://community.wowza.com/u/Ben_Watson)
#### Post date: [March 18, 2014, 9:11am UTC](https://community.wowza.com/t/mpeg2-ts-h-264-for-brighsigns/37457/9 "2014-03-18T09:11:38Z")
> Hi,
>
> Be sure to restart after editing the application. If you’re using Wowza Streaming Engine 4, you can add these Properties using the Wowza Streaming Engine Manager.
>
> You may need the correct permissions to add Properties, please take a look at the [Managing Sign-In credentials](https://www.wowza.com/docs/how-to-install-and-configure-wowza-streaming-engine#signinManager) in our Quick Start Guide.
>
> The logging below will only appear when a RTSP client connects to Wowza after configured using Properties in the above MPEG-TS article.
>
> ```auto
> comment server INFO 200 - RTPPacketizerMPEGTS.handleAMFPacket: mpegtsFlushEveryPacket:true
>
> ```
>
> ```auto
> tc[0]: 2816:2816:48000
> tc[0]: 2837:2837:48000
> tc[0]: 2859:2859:48000
>
> ```
>
> The Properties which log the above will need to be set as true for the logging to take place, they are both false by default.
>
> Regards,
>
> Jason
I have tried to get the Streaming Engine Manager to work with Amazon AMIs, but it doesn’t come up. It may be as simple as a security port not set, so I’ll dig a little…
- Ben
//EDITED - I launched our usual DevPay AMI, and it looks like the stream engine manager is disabled on DevPay. I guess I need to call Wowza to see what our best option is.
---
### Author:  [@Ben\_Watson](https://community.wowza.com/u/Ben_Watson)
#### Post date: [March 19, 2014, 1:20pm UTC](https://community.wowza.com/t/mpeg2-ts-h-264-for-brighsigns/37457/10 "2014-03-19T13:20:47Z")
> Hi,
>
> You just need to add a Custom TCP Rule to your Security Group to open port 8088.
>
> Once that’s open, if you you go to http://[YourEC2IPaddress]:8088
>
> You’ll be Presented with the Wowza Streaming Engiine Manager intro page.
>
> You can skip the intro if you wish and go to the login page.
>
> Enter username: wowza
>
> password: (yourAmazonInstance ID) ← get this from your Amazon AWS console)
>
> You should then be taken to the manager home page.
>
> You can then configure, as Jason directed, from there.
>
> Daren
Hey Daren,
Tried this again today after adding the TCp rule and using DevPay AMI again, **but nothing happens**. I’m thinking the stream manager is disabled in DevPay.
I used this AMI:
[https://console.aws.amazon.com/ec2/home?region=us-east-1#launchAmi=ami-f50e0f9c](https://console.aws.amazon.com/ec2/home?region=us-east-1#launchAmi=ami-f50e0f9c)
Which is the first one in the DevPay AMI listing here:
> **[Wowza Streaming Engine on Amazon](https://www.wowza.com/docs/amazon)**
>
> Deploy Wowza Streaming Engine on Amazon Elastic Compute Cloud (Amazon EC2) virtual machines.
-Ben
---
### Author:  [@Ben\_Watson](https://community.wowza.com/u/Ben_Watson)
#### Post date: [March 19, 2014, 1:48pm UTC](https://community.wowza.com/t/mpeg2-ts-h-264-for-brighsigns/37457/11 "2014-03-19T13:48:30Z")
> Ben,
>
> The classic StreamManager is still there, but it uses port 8086:
>
> ```auto
> http://[wowza-ec2-public-dns]:8086/streammanager/index.html
>
> ```
>
> The default username is “wowza” and the password is the instanceid. You can change or add in /conf/admin.password file, or in the manager.
>
> Richard
Nope. same thing. nothing running on that port either. Both 8088 and 8086 are open.
[http://23.23.114.227:8086/streammanager/index.html](http://23.23.114.227:8086/streammanager/index.html)
I’ll leave it running for a few hours.
---
### Author:  [@Ben\_Watson](https://community.wowza.com/u/Ben_Watson)
#### Post date: [March 19, 2014, 1:50pm UTC](https://community.wowza.com/t/mpeg2-ts-h-264-for-brighsigns/37457/12 "2014-03-19T13:50:48Z")
> Nope. same thing. nothing running on that port either. Both 8088 and 8086 are open.
>
> [http://23.23.114.227:8086/streammanager/index.html](http://23.23.114.227:8086/streammanager/index.html)
>
> I’ll leave it running for a few hours.
Uh, that’s weird. The prob must be on my end. I opened it on my celphone using cel network and it comes up…
great. time to call IT.
Sorry for the trouble.
-Ben