ffmpeg error: UDP timeout, retrying with TCP

In many cases I need to open a rtsp stream:

ffmpeg  -i rtsp://user:pass@X.X.X.X:554

but I have following error:

[rtsp @ 0x80670e000] UDP timeout, retrying with TCP
[rtsp @ 0x80670e000] method PAUSE failed: 551 Option not supported
[rtsp @ 0x80670e000] Could not find codec parameters for stream 0 (Video: h264, none): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
Guessed Channel Layout for Input Stream #0.1 : mono
Input #0, rtsp, from 'rtsp://stream:c0L3g!u2021@X.X.X.X:554':
  Metadata:
    title           : Media Presentation
  Duration: N/A, bitrate: 64 kb/s
    Stream #0:0: Video: h264, none, 90k tbr, 90k tbn, 180k tbc
    Stream #0:1: Audio: pcm_mulaw, 8000 Hz, mono, s16, 64 kb/s
Stream mapping:
  Stream #0:0 -> #0:0 (copy)
  Stream #0:1 -> #0:1 (pcm_mulaw (native) -> aac (native))
Press [q] to stop, [?] for help
[rtsp @ 0x80670e000] UDP timeout, retrying with TCP
[rtsp @ 0x80670e000] method PAUSE failed: 551 Option not supported
rtsp://stream:c0L3g!u2021@X.X.X.X:554: Operation not permitted
[aac @ 0x8066a5100] Too many bits 8832.000000 > 6144 per frame requested, clamping to max
[segment @ 0x80670f200] dimensions not set
Could not write header for output file #0 (incorrect codec parameters ?): Invalid argument

In this case stream is on TCP but ffmpeg try first time with UDP. The problem is the ffmpeg not open the stream in this conditions.

To force ffmpeg to try in TCP only we use -rtsp_transport option tcp.

In this case we will have:

ffmpeg -rtsp_transport tcp -i rtsp://user:pass@X.X.X.X:554

 

This parameter work for following error:

Invalid data found when processing input