# MPEG-TS from  Cisco D9854

**URL:** <https://community.wowza.com/t/mpeg-ts-from-cisco-d9854/38331>\
**Category:** Wowza Streaming Engine\
**Created:** [November 20, 2012, 6:09pm UTC](https://community.wowza.com/t/mpeg-ts-from-cisco-d9854/38331 "2012-11-20T18:09:19Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![Guilherme\_Lacerda](https://avatars.discourse-cdn.com/v4/letter/g/c5a1d2/32.png) [@Guilherme\_Lacerda](https://community.wowza.com/u/Guilherme_Lacerda)\
**Post date:** [November 20, 2012, 6:09pm UTC](https://community.wowza.com/t/mpeg-ts-from-cisco-d9854/38331/1 "2012-11-20T18:09:19Z")

</div>

Hi,

I’m trying to play stream from Cisco D9854 [decoder - multicast UDP] but with no sucess. Create a mpegts.stream with udp://0.0.0.0:10000 and with udp://ip:5001 - decoder ip, publish in stream manager, but i can’t play.

Nothing in logs. The UDP packets coming to interface.

I tested a MPEG-TS in VLC and play ok.

Regards,

Guilherme

---

<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:** [November 21, 2012, 1:28pm UTC](https://community.wowza.com/t/mpeg-ts-from-cisco-d9854/38331/2 "2012-11-21T13:28:43Z")

</div>

I think you have to point the stream to the same server:

udp://[wowza-address]:10000

Then re-stream in Wowza from udp://0.0.0.0:10000 or udp://127.0.0.1:10000

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:** [November 21, 2012, 5:24pm UTC](https://community.wowza.com/t/mpeg-ts-from-cisco-d9854/38331/3 "2012-11-21T17:24:43Z")

</div>

What about on the encoder side? Did you put the IP address of the Wowza machine in the UDP url that you are publishing to?

Is this Windows or Linux? You can use tcpdump on Linux or Wireshark on Windows to see if packets are reaching Wowza from the encoder.

Rihard

---

<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:** [November 21, 2012, 5:43pm UTC](https://community.wowza.com/t/mpeg-ts-from-cisco-d9854/38331/4 "2012-11-21T17:43:01Z")

</div>

Instead of the 239.x.x.x address use the IP of the Wowza machine. And if you use port 50001 playback would be udp://127.0.0.1:5001

Richard

---

<div class="post-metadata">

**Author:** ![Jason\_Hilton](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/jason_hilton/32/437_2.png) [@Jason\_Hilton](https://community.wowza.com/u/Jason_Hilton)\
**Post date:** [November 21, 2012, 4:45pm UTC](https://community.wowza.com/t/mpeg-ts-from-cisco-d9854/38331/5 "2012-11-21T16:45:53Z")

</div>

Hi

Wowza does this when it tries to play a stream and can’t find it.

You must have some multicast configurations wrong (a typo maybe or you’re looking on the wrong port?).

Try checking your configuration in the VHost.xml against this guide,

[https://www.wowza.com/docs/how-to-listen-for-a-multicast-stream-on-a-particular-network-interface](https://www.wowza.com/docs/how-to-listen-for-a-multicast-stream-on-a-particular-network-interface)

There’s a tutorial for MPEG-TS based encoders to help you (if you need it) here,

[https://www.wowza.com/docs/how-to-publish-and-play-a-live-stream-mpeg-ts-based-encoder](https://www.wowza.com/docs/how-to-publish-and-play-a-live-stream-mpeg-ts-based-encoder)

Jason

---

<div class="post-metadata">

**Author:** ![Jason\_Hilton](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/jason_hilton/32/437_2.png) [@Jason\_Hilton](https://community.wowza.com/u/Jason_Hilton)\
**Post date:** [November 22, 2012, 12:49pm UTC](https://community.wowza.com/t/mpeg-ts-from-cisco-d9854/38331/6 "2012-11-22T12:49:15Z")

</div>

Hi

This sound like a routing issue to me.

You can try adding a network route, the command is:

route add 224.0.0.0 netmask 240.0.0.0 dev eth1

You may have to use eth0 rather than eth1 but I’m not 100% sure if it will work with eth1.

Jason

---

<div class="post-metadata">

**Author:** ![Guilherme\_Lacerda](https://avatars.discourse-cdn.com/v4/letter/g/c5a1d2/32.png) [@Guilherme\_Lacerda](https://community.wowza.com/u/Guilherme_Lacerda)\
**Post date:** [November 21, 2012, 12:47pm UTC](https://community.wowza.com/t/mpeg-ts-from-cisco-d9854/38331/7 "2012-11-21T12:47:34Z")

</div>

Hi Richard,

I’m tried udp://127.0.0.1:10000 and udp://:10000.

Log:

INFO server comment - RTPMediaCaster.Reconnector[21039081:teste/_definst_:mpegts.stream]: start: 3

INFO server comment - RTPSessionDescriptionDataProviderBasic.getStreamInfo[teste/_definst_]: URI: udp://127.0.0.1:10000

INFO stream create - -

INFO server comment - RTPUDPTransport.bind[teste/_definst_]: /127.0.0.1:10000

INFO stream publish mpegts.stream -

INFO server comment - RTPMediaCaster.Reconnector[21039081:teste/_definst_:mpegts.stream]: done: 3

INFO server comment - RTPMediaCaster.streamTimeout[21039081:teste/_definst_:mpegts.stream]: timeout:12000 diff:12007 reason:101

INFO server comment - RTPMediaCaster.resetConnection[21039081:teste/_definst_:mpegts.stream]:

INFO server comment - RTPMediaCaster.closeRTPSession[21039081:teste/_definst_:mpegts.stream]

INFO server comment - RTPUDPTransport.unbind[teste/_definst_]: /127.0.0.1:10000 sent:0 recv:0

INFO stream unpublish mpegts.stream -

INFO stream destroy mpegts.stream -

Wowza create the stream and detroy in seconds. It’s a Linux box (virtual machine) with Wowza 3.1.0 build1410. I have 2 network interfaces: eth0 to access Wowza and eth1 to multicast (with multicast and promiscuos mode).

Guilherme

---

<div class="post-metadata">

**Author:** ![Guilherme\_Lacerda](https://avatars.discourse-cdn.com/v4/letter/g/c5a1d2/32.png) [@Guilherme\_Lacerda](https://community.wowza.com/u/Guilherme_Lacerda)\
**Post date:** [November 21, 2012, 2:08pm UTC](https://community.wowza.com/t/mpeg-ts-from-cisco-d9854/38331/8 "2012-11-21T14:08:39Z")

</div>

Hi Jason,

I configure my VHost.xml and the error is the same.

Does exist a way to force publish this stream from a multicast IP to wowza? A Addon maybe?

Regards,

Guilherme

---

<div class="post-metadata">

**Author:** ![Guilherme\_Lacerda](https://avatars.discourse-cdn.com/v4/letter/g/c5a1d2/32.png) [@Guilherme\_Lacerda](https://community.wowza.com/u/Guilherme_Lacerda)\
**Post date:** [November 21, 2012, 2:14pm UTC](https://community.wowza.com/t/mpeg-ts-from-cisco-d9854/38331/9 "2012-11-21T14:14:32Z")

</div>

This is my cenario:

IRD (MPEG-TS - multicast 239.20.1.1:5001) --\> Wowza (2 IP - one to the internet and other only for multicast - 192.254.1.1) --\> Akamai --\> Flash players.

For now, if i plays in VLC (not pushing to Akamai), I will very happy!

if this really works, I will try transcode this MPEG-TS to H264/ACC.

---

<div class="post-metadata">

**Author:** ![Guilherme\_Lacerda](https://avatars.discourse-cdn.com/v4/letter/g/c5a1d2/32.png) [@Guilherme\_Lacerda](https://community.wowza.com/u/Guilherme_Lacerda)\
**Post date:** [November 21, 2012, 6:25pm UTC](https://community.wowza.com/t/mpeg-ts-from-cisco-d9854/38331/10 "2012-11-21T18:25:01Z")

</div>

Richard,

Unfortunately, the Cisco’s IRD not especify a ip to publish, only a multicast ip. I’m tried to set the wowza’s ip, but the same error.

It’s a Linux box (virtual machine) with Wowza 3.1.0 build1410. I have 2 network interfaces: eth0 to access Wowza and eth1 to multicast (with multicast and promiscuos mode). The packets reaching Wowza machine. I’m tried wowza on Windows and is the same error.

Guilherme

---

<div class="post-metadata">

**Author:** ![Guilherme\_Lacerda](https://avatars.discourse-cdn.com/v4/letter/g/c5a1d2/32.png) [@Guilherme\_Lacerda](https://community.wowza.com/u/Guilherme_Lacerda)\
**Post date:** [November 22, 2012, 2:46pm UTC](https://community.wowza.com/t/mpeg-ts-from-cisco-d9854/38331/11 "2012-11-22T14:46:47Z")

</div>

Hi Jason,

I inserted this route. Nothing.

If I open multicast UDP flow in VLC and re-send in MPEGTS over RTP, it works. But I do not trust in VLC. It’s too unstable.

I’m tried generate a stream in VLC and send to Wowza in UDP. Same error. Very odd.

Guilherme

---

<div class="post-metadata">

**Author:** ![Guilherme\_Lacerda](https://avatars.discourse-cdn.com/v4/letter/g/c5a1d2/32.png) [@Guilherme\_Lacerda](https://community.wowza.com/u/Guilherme_Lacerda)\
**Post date:** [November 26, 2012, 1:21pm UTC](https://community.wowza.com/t/mpeg-ts-from-cisco-d9854/38331/12 "2012-11-26T13:21:09Z")

</div>

Jason and Richard,

I’ve resolved this issue.

The problem is the IRD [Cisco D9854]. This device have a lot network configs. Our staff change unknow settings in this IRD and suddenly, the packts run into Wowza.

After this unknow changes, with Jason’s tip [route add], Wowza works fine. Now I can transcode this MPEG\_TS, send to Akamai, etc.

Thanks for your help, guys.

Regards,

---

<div class="post-metadata">

**Author:** ![Armando\_Delewg](https://avatars.discourse-cdn.com/v4/letter/a/90ced4/32.png) [@Armando\_Delewg](https://community.wowza.com/u/Armando_Delewg)\
**Post date:** [June 10, 2017, 1:29pm UTC](https://community.wowza.com/t/mpeg-ts-from-cisco-d9854/38331/13 "2017-06-10T13:29:03Z")

</div>

hello can you share the cisco config please
