# mpeg-ts TCP

**URL:** <https://community.wowza.com/t/mpeg-ts-tcp/33865>\
**Category:** Wowza Streaming Engine\
**Created:** [October 15, 2016, 10:25am UTC](https://community.wowza.com/t/mpeg-ts-tcp/33865 "2016-10-15T10:25:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kv\_pham](https://avatars.discourse-cdn.com/v4/letter/k/7bcc69/32.png) [@kv\_pham](https://community.wowza.com/u/kv_pham)\
**Post date:** [October 15, 2016, 10:25am UTC](https://community.wowza.com/t/mpeg-ts-tcp/33865/1 "2016-10-15T10:25:20Z")

</div>

Hello

I’ve been testing the new mpeg-ts by TCP feature introduced in 4.5.0.02 (I was among those who requested it).

Unfortunately this fails to work.

**setup:**

**encoder:** ffmpeg pushes mpeg-ts to URI: [http://IP\_dedicated\_server](http://IP_dedicated_server:port):PORT

**stream file:** set to URI: [http://IP\_dedicated\_server](http://IP_dedicated_server:port):PORT

with relevant audio and video PID selected in Properties.

**In the logs** I have the following error message once the stream file is started as mpegtstcp:

MPEGTSTCPReceiver.internalConnect: Failed to connect[IP\_dedicated\_server:PORT] : org.apache.mina.common.RuntimeIOException: Failed to get the session[ConnectException: Connexion refusée].|at org.apache.mina.common.support.DefaultConnectFuture.getSession(DefaultConnectFuture.java:71)|at com.wowza.wms.mediacaster.MediaCasterConnection.connect(MediaCasterConnection.java:67)|at com.wowza.wms.mediacaster.MediaCasterConnection.connect(MediaCasterConnection.java:38)|at com.wowza.wms.mediacaster.mpegtstcp.MPEGTSTCPReceiver.c(MPEGTSTCPReceiver.java:313)|at com.wowza.wms.mediacaster.mpegtstcp.MPEGTSTCPReceiver.h(MPEGTSTCPReceiver.java:25)|

The same setup works fine in udp …

Is mpeg-ts tcp designed in PUSH or PULL from the encoder ?

Thanks for any insights.

---

<div class="post-metadata">

**Author:** ![kv\_pham](https://avatars.discourse-cdn.com/v4/letter/k/7bcc69/32.png) [@kv\_pham](https://community.wowza.com/u/kv_pham)\
**Post date:** [October 19, 2016, 2:15pm UTC](https://community.wowza.com/t/mpeg-ts-tcp/33865/2 "2016-10-19T14:15:22Z")

</div>

same issues with wms 4.5.0.03 which supposedly did a few fixes for the mpeg-ts tcp .

but ingest from ffmpeg still fails

---

<div class="post-metadata">

**Author:** ![Alex\_C](https://avatars.discourse-cdn.com/v4/letter/a/bbe5ce/32.png) [@Alex\_C](https://community.wowza.com/u/Alex_C)\
**Post date:** [December 16, 2016, 8:46pm UTC](https://community.wowza.com/t/mpeg-ts-tcp/33865/3 "2016-12-16T20:46:34Z")

</div>

Hello phamkv,

I know that this question was addressed via a ticket, I wanted to post answers to your questions for other customers.

The MPEG-TS is a Pull from the encoder.

This would be a pull style of stream where the source is listening for a connection. This works only for TCP.

_ffmpeg -re -i inputfile.mp4 -vcodec copy -acodec copy -f mpegts tcp://[encoder\_address]:10000?listen_

_Regards,_

_Alex_