# Mpeg-TS stream target as source specific multicast

**URL:** <https://community.wowza.com/t/mpeg-ts-stream-target-as-source-specific-multicast/102799>\
**Category:** Wowza Streaming Engine\
**Tags:** stream-targets\
**Created:** [November 29, 2025, 7:11pm UTC](https://community.wowza.com/t/mpeg-ts-stream-target-as-source-specific-multicast/102799 "2025-11-29T19:11:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Daniel\_Rossi1](https://avatars.discourse-cdn.com/v4/letter/d/35a633/32.png) [@Daniel\_Rossi1](https://community.wowza.com/u/Daniel_Rossi1)\
**Post date:** [November 29, 2025, 7:11pm UTC](https://community.wowza.com/t/mpeg-ts-stream-target-as-source-specific-multicast/102799/1 "2025-11-29T19:11:50Z")

</div>

I am pretty sure I had this working at one stage. I am trying to publish an mpeg-ts stream target as a source specific multicast. To be picked up properly over the network, For some reason pimd does not detect the wowza multicast group, only if it’s published by ffmpeg am I getting something.

You can configure a source specific address for a stream file to ingest multicast but what about for stream target multicast publishing ? It might explain why I am not able to subscribe to the wowza stream as source specific multicast with ffmpeg. I am only able to pickup the wowza stream locally not on the network.

I am using an address of 232.255.255.116 with port 9998

Is there a special config required to set a source specific address ?

With ffmpeg publishing on windows like

./ffmpeg -re -stream\_loop -1 -i “D:\just do it.mp4” -c:v h264 -bsf:v h264\_mp4toannexb -profile:v baseline -c:a aac -b:a 128k -ar 44100 -f mpegts “udp://232.255.255.116:9998?pkt\_size=188&localaddr=thelocalip”

I get it showing up in pimd like this but not for wowza.

thelocalip 232.255.255.116 SSM CACHE SG