# FFmpeg RTSP send audio stream to Wowza Streaming Cloud

**URL:** <https://community.wowza.com/t/ffmpeg-rtsp-send-audio-stream-to-wowza-streaming-cloud/48435>\
**Category:** Wowza Video (Formerly Streaming Cloud)\
**Created:** [April 3, 2017, 9:18am UTC](https://community.wowza.com/t/ffmpeg-rtsp-send-audio-stream-to-wowza-streaming-cloud/48435 "2017-04-03T09:18:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mikael\_Osterhed](https://avatars.discourse-cdn.com/v4/letter/m/35a633/32.png) [@Mikael\_Osterhed](https://community.wowza.com/u/Mikael_Osterhed)\
**Post date:** [April 3, 2017, 9:18am UTC](https://community.wowza.com/t/ffmpeg-rtsp-send-audio-stream-to-wowza-streaming-cloud/48435/1 "2017-04-03T09:18:09Z")

</div>

I am trying to send an audio-stream to my Wowza Cloud Service (trial account) using RTSP. This works fine using LibStreamer library for Android. I am now trying to do the same with FFmpeg on my desktop streaming my webcam’s audio. I have tried the following command (authentication disabled on Wowza):

```auto
ffmpeg -f dshow -re -i audio="Desktop Microphone (HD-3000 - Microsoft LifeCam.)" -acodec aac -strict -2 -f rtsp -muxdelay 0.1 rtsp://52.57.81.141:1935/app-xxx/yyyyyy

```

FFmpeg seems to do its thing however I would have expected that the webconsole of Wowza would show “connected” when receiving the stream from FFMpeg.

Any ideas? It might actually be a problem with Wowza but I checked this forum and I couldn’t find any post describing my problem.

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/system/32/447_2.png) [@system](https://community.wowza.com/u/system)\
**Post date:** [April 15, 2017, 2:13am UTC](https://community.wowza.com/t/ffmpeg-rtsp-send-audio-stream-to-wowza-streaming-cloud/48435/2 "2017-04-15T02:13:01Z")

</div>

You should add the following to force RTSP to use TCP delivery for both the control and data channels. If you do not then you may incur packet loss.

```auto
-rtsp_transport tcp

```

It is also important to specify the parameters of the audio such as bitrate, frequency and channels. In addition the built in AAC codec included with FFmpeg is no longer experimental so you if you are running a newer build you can skip that option.

```auto
ffmpeg -f dshow -re -i audio="Desktop Microphone (HD-3000 - Microsoft LifeCam.)" -acodec aac -b:a 192k -ac 2 -ar 44100 -af "aresample=async=1:min_hard_comp=0.100000:first_pts=0" -f rtsp -rtsp_transport tcp -muxdelay 0.1 rtsp://52.57.81.141:1935/app-xxx/yyyyyy

```

You should also be able to both stream your content and make a local copy of your output if you specify two outputs as shown below:

```auto
ffmpeg -f dshow -re -i audio="Desktop Microphone (HD-3000 - Microsoft LifeCam.)" -acodec aac -b:a 192k -ac 2 -ar 44100 -af "aresample=async=1:min_hard_comp=0.100000:first_pts=0" -f rtsp -rtsp_transport tcp -muxdelay 0.1 rtsp://52.57.81.141:1935/app-xxx/yyyyyy -acodec aac -b:a 192k -ac 2 -ar 44100 -af "aresample=async=1:min_hard_comp=0.100000:first_pts=0" -f mp4 -y out.mp4

```

I hope that helps to resolve your issue.

---

<div class="post-metadata">

**Author:** ![FLUZO\_Root](https://avatars.discourse-cdn.com/v4/letter/f/87869e/32.png) [@FLUZO\_Root](https://community.wowza.com/u/FLUZO_Root)\
**Post date:** [September 9, 2018, 4:30pm UTC](https://community.wowza.com/t/ffmpeg-rtsp-send-audio-stream-to-wowza-streaming-cloud/48435/3 "2018-09-09T16:30:01Z")

</div>

Works fine. Thanks.