How to re-stream video from an IP camera (RTSP/RTP re-streaming)

Published on 10-02-2010 12:39 PM Number of Views: 129495

126 Comments

This tutorial provides the basic steps for re-streaming an IP camera that supports H.264 video and AAC or MP3 audio through Wowza Media Server®. Use this tutorial to set up an application named live to stream live content to Adobe® Flash® Player, Microsoft® Silverlight® player, Apple® iOS devices, and RTSP/RTP-based players.

Tutorial

Troubleshooting

Related Articles

Tutorial

Configuration

This section provides the basic steps for setting up an application for live streaming and configuring Application.xml.

Create application folder [install-dir]/applications/live.
Create configuration folder [install-dir]/conf/live and copy [install-dir]/conf/Application.xml to this new folder.
Edit the newly copied Application.xml file and make the following changes (some of these settings may already be present):

Note: Right-click HERE to download a pre-configured version of Application.xml.
1. Set the Streams/StreamType property to:
  Code:
```
<StreamType>live</StreamType>
```
2. Set the HTTPStreamers property to:
  Code:
```
<HTTPStreamers>cupertinostreaming,smoothstreaming,sanjosestreaming</HTTPStreamers>
```
3. Set the Streams/LiveStreamPacketizers property to:
  Code:
```
<LiveStreamPacketizers>cupertinostreamingpacketizer,smoothstreamingpacketizer,sanjosestreamingpacketizer</LiveStreamPacketizers>
```
4. Set the RTP/Authentication/PlayMethod property to:
  Code:
```
<PlayMethod>none</PlayMethod>
```
5. If you are using a Wowza Media Server version earlier than 3.0.4, add the following property to the MediaCaster/Properties container (be sure to get the correct <Properties> container, there are several in the Application.xml file):
  Code:
```
<Property>
    <Name>forceInterleaved</Name>
    <Value>true</Value>
    <Type>Boolean</Type>
</Property>
```
  Starting with Wowza Media Server 3.0.4, the forceInterleaved property isn't needed as the built-in default configuration comes with the settings below. This will work for most cameras.
  Note: If your camera doesn't support RTSP/RTP interleaved (RTP over TCP), then you must change the RTPTransportMode value from interleave to udp:
  Code:
```
<MediaCaster>
     <RTP>
          <RTSP>
               
     		<RTPTransportMode>interleave</RTPTransportMode>
          </RTSP>
     </RTP>
     
     <Properties>
     </Properties>
</MediaCaster>
```

Publishing the stream

This section provides the basic steps for creating a .stream file to publish your live stream to Wowza Media Server.

Use a text editor to create the file [install-dir]/content/camera.stream and set the contents of this file to the full RTSP/RTP URL of the camera. The file must have a .stream filename extension. For this tutorial, the file used is camera.stream.

Note: SoleraTec has a reference of IP cameras and RTSP URLs.
Using a text editor, edit the [install-dir]/conf/admin.password file and add a username and password that will be used to start and stop the publishing of the camera (below is an example of the file with the username myuser and password mypassword):
Code:
```
# Admin password file (format [username][space][password])
# username password
myuser mypassword
```
Start Wowza Media Server.
Use Stream Manager to start the stream:
1. Enter the following URL in a web browser:
  
  URL: http://[wowza-ip-address]:8086/streammanager
2. In the Security dialog box, enter your admin username and password from above.
3. In the Stream Manager webpage, click the [start-receiving-stream] link just below the live application folder.
4. In the Start Receiving Stream dialog box, select the following MediaCaster Type option: rtp
5. In the Stream Name field, enter camera.stream.
6. Click OK.

Playback

Note: In the following examples, [wowza-ip-address] is the IP address or domain name of the server running Wowza Media Server.

Adobe Flash Player (RTMP)

In Wowza Media Server 3.5, double-click [install-dir]/examples/LiveVideoStreaming/FlashRTMPPlayer/player.html, enter the information below, and then click the Connect button.

Server: rtmp://[wowza-ip-address]/live
Stream: camera.stream

To play the stream from a remote computer, copy the FlashRTMPPlayer folder to a web server, and then connect to: http://<webserver>/FlashRTMPPlayer/player.html.

Note: In Wowza Media Server 3.1.2 and earlier, double-click [install-dir]/examples/LiveVideoStreaming/client/live.html, enter the information below, and then click the Play button.

Server: rtmp://[wowza-ip-address]/live
Stream: camera.stream

To play the stream from a remote computer, copy the client folder to a web server, and then connect to: http://<webserver>/client/live.html.

Note: If your application will only stream to Flash RTMP clients, see Flash RTMP clients only.

Adobe Flash Player (San Jose/Adobe HDS)

In Wowza Media Server 3.5, double-click [install-dir]/examples/LiveVideoStreaming/FlashHTTPPlayer/player.html, enter the information below, and then click the Connect button.

Stream: http://[wowza-ip-address]:1935/live/camera.stream/manifest.f4m

To play the stream from a remote computer, copy the FlashHTTPPlayer folder to a web server, and then connect to: http://<webserver>/FlashHTTPPlayer/player.html.

Note: In Wowza Media Server 3.1.2 and earlier, double-click [install-dir]/examples/LiveVideoStreaming/clientOSMF/bin-release/LiveOSMFPlayer.html, enter the information below, and then click the Play button.

Stream: http://[wowza-ip-address]:1935/live/camera.stream/manifest.f4m

To play the stream from a remote computer, copy the clientOSMF/bin-release folder to a web server, and then connect to: http://<webserver>/bin-release/LiveOSMFPlayer.html.

Note: The stream can only be played from an OSMF-based Flash player that's embedded in a webpage.

Apple iOS device (Cupertino/Apple HLS)

Enter the following URL into the Safari® web browser on the device:

URL: http://[wowza-ip-address]:1935/live/camera.stream/playlist.m3u8

Note: The Apple iPhone® 3GS (and older) and iPod touch® devices require that video be encoded using H.264 format (Baseline profile level 3 or lower) and AAC or MP3 stereo audio. iPhone 3GS and newer devices support Baseline profile. For encoding guidance for playback on Apple iOS devices, see How to find Apple iOS device supported profile and level information.

Note: This stream can also be played using the Safari web browser or QuickTime 10.x on a computer running Mac OS® X Snow Leopard version 10.6 and later.

Microsoft Silverlight (Smooth Streaming)

In Wowza Media Server 3.5, double-click [install-dir]/examples/LiveVideoStreaming/SilverlightPlayer/player.html, enter the information below, and then click the Connect button.

Stream: http://[wowza-ip-address]:1935/live/camera.stream/Manifest

To play the stream from a remote computer, copy the SilverlightPlayer folder to a web server, and then connect to: http://<webserver>/SilverlightPlayer/player.html.

Note: In Wowza Media Server 3.1.2 and earlier, double-click [install-dir]/examples/LiveVideoStreaming/clientSilverlight/Default.html, enter the information below, and then click the Play button.

Stream: http://[wowza-ip-address]:1935/live/camera.stream/Manifest

To play the stream from a remote computer, copy the clientSilverlight folder to a web server, and then connect to: http://<webserver>/clientSilverlight/Default.html

Note: The Silverlight player requires that both audio and video be present for playback. For live streaming only, the key frame frequency (which can be set directly in some encoders or is gop/fps) must be between 1 and 4 seconds (2 seconds is recommended). Anything greater than 4 seconds may cause playback to freeze.

RTSP/RTP player

Enter the following URL into the RTSP/RTP player:

URL: rtsp://[wowza-ip-address]:1935/live/camera.stream

Flash RTMP clients only

(Optional) If your application will only stream to Flash RTMP clients, in [install-dir]/conf/live/Application.xml, you can set the Streams/StreamType property to:

Code:

<StreamType>rtp-live</StreamType>

If you do this, then you won't need to use StreamManager (see Publishing the stream). The first Flash client that plays the stream will trigger Wowza Media Server to start re-streaming.

Also, in [install-dir]/conf/live/Application.xml, make sure that the Streams/LiveStreamPacketizers property is empty:

Code:

<LiveStreamPacketizers></LiveStreamPacketizers>

Troubleshooting

Check your IP camera source using VLC

It's best to first make sure that your camera can send H.264, AAC, or MP3 content. You can do this using the VideoLAN VLC player:

Open the VLC player.
Select menu item Media > Open Network Stream, enter your camera's RTSP URL, and then click Play.
After the stream starts playing, select menu item Tools > Codec Information and make sure that one or two of the following
codecs are listed:
- H.264 or AVC1 or MPEG4 Part10
- AAC
- MP3

Note: If your camera doesn't support the proper formats, then the stream must be transcoded before it's sent to Wowza Media Server. See How to use VLC as a live stream encoder with Wowza Media Server (MPEG-TS) for an example using VLC.

RTSP/RTP

RTSP/RTP streaming is used to stream to Android™ and BlackBerry® mobile devices. Newer Android-based phones also support Adobe Flash Player 10.1 and later, along with RTMP and Adobe HTTP Dynamic Streaming (Adobe HDS).
To stream to RTSP/RTP, be sure that UDP ports 0-65535 are open and properly mapped to the server running Wowza Media Server.
It's very important to carefully follow the instructions provided in How to troubleshoot RTSP/RTP playback to properly configure Wowza Media Server for RTSP/RTP streaming.

Additional property configuration needed for some cameras

When streaming out using RTSP/RTP, you can force the output to MPEG-TS (which is required by many set-top boxes) by adding the following properties to the RTP/Properties container in [install-dir]/conf/[application]/Application.xml (be sure to get the correct <Properties> container, there are several in the Application.xml file):
Code:
```
<Property>
    <Name>forceMPEGTSOut</Name>
    <Value>true</Value>
    <Type>Boolean</Type>
</Property>
<Property>
    <Name>rtpWrapMPEGTS</Name>
    <Value>true</Value>
    <Type>Boolean</Type>
</Property>
```
Some IP cameras may fail when Wowza Media Server tries to periodically validate the RTSP/RTP connection. The camera will disconnect and then reconnect every 15-30 seconds. You can turn off RTSP/RTP validation by adding the following property to the MediaCaster/Properties container in [install-dir]/conf/[application]/Application.xml (be sure to get the correct <Properties> container, there are several in the Application.xml file):
Code:
```
<Property>
    <Name>rtspValidationFrequency</Name>
    <Value>0</Value>
    <Type>Integer</Type>
</Property>
```
Some IP cameras send additional application tracks that Wowza Media Server can't understand. You can filter out these tracks by adding the following property to the MediaCaster/Properties container in [install-dir]/conf/[application]/Application.xml (be sure to get the correct <Properties> container, there are several in the Application.xml file):
Code:
```
<Property>
    <Name>rtspFilterUnknownTracks</Name>
    <Value>true</Value>
    <Type>Boolean</Type>
</Property>
```

How to turn on/off audio and video tracks

Note: For use with Wowza Media Server 3.0.5 and later.

You can turn off audio or video tracks by adding the following properties to the MediaCaster/Properties container in [install-dir]/conf/[application]/Application.xml (be sure to get the correct <Properties> container, there are several in the Application.xml file):

Code:

<Property>
	<Name>rtspStreamAudioTrack</Name>
	<Value>false</Value>
	<Type>Boolean</Type>
</Property>
<Property>
	<Name>rtspStreamVideoTrack</Name>
	<Value>false</Value>
	<Type>Boolean</Type>
</Property>

To turn on audio or video tracks, set the above property values to true.

How to add additional logging for RTSP debugging

You can log extra debug information to the log file about the RTSP handshake between Wowza Media Server and the IP camera (RTSP/RTP source) by adding the following property to the MediaCaster/Properties container in [install-dir]/conf/[application]/Application.xml (be sure to get the correct <Properties> container, there are several in the Application.xml file):

Code:

<Property>
    <Name>debugRTSPSession</Name>
    <Value>true</Value>
    <Type>Boolean</Type>
</Property>

Common problems with .stream files

Many text editors will append a .txt filename extension to the camera.stream filename. This will result in an error message similar to the following:

SDP file missing: c:/program files/wowzamediasystems/wowzamediaserver[version]/content/camera.stream

To fix this, go to the [install-dir]/content folder and remove the .txt filename extension from the file.

Property to change AAC packetization method

Wowza Media Server can output AAC audio using the mpeg4-generic and mp4a-latm (3gpp) packetization methods. The default packetization method is mpeg4-generic. To switch to mp4a-latm (3gpp), add the following property to the RTP/Properties container in [install-dir]/[application]/Application.xml (be sure to get the correct <Properties> container, there are several in the Application.xml file):

Code:

<Property>
    <Name>audioPacketizerAAC</Name>
    <Value>com.wowza.wms.rtp.packetizer.RTPPacketizerMPEG4LATM</Value>
</Property>

Flash playback

Some IP cameras send proprietary data as part of the H.264 stream that may cause playback problems (pauses or glitches during playback) in Flash. You can filter out these extensions by adding the following property to the Streams/Properties container in [install-dir]/conf/[application]/Application.xml (be sure to get the correct <Properties> container, there are several in the Application.xml file):

Code:

<Property>
    <Name>nalUnitFilter</Name>
    <Value>13</Value>
    <Type>Integer</Type>
</Property>

Problematic SDP files

Many IP cameras incorrectly publish the H.264 profile-level-id value in the Session Description Protocol (SDP) message. This can cause the video to be either blank or corrupted. You can configure Wowza Media Server to ignore the profile-level-id value in the SDP data and instead derive this value from the sprop-parameter-sets value by adding the following property to the RTP/Properties container in [install-dir]/conf/[application]/Application.xml (be sure to get the correct <Properties> container, there are several in the Application.xml file):

Code:

<Property>
    <Name>rtpIgnoreProfileLevelId</Name>
    <Value>true</Value>
    <Type>Boolean</Type>
</Property>

Updated: For Wowza Media Server 3.5.0 on 11-08-2012

Click here, if you are having problems or would like to discuss this article.
Leave a comment below, if there is some aspect of this article you would like to see changed or improved.

126 Comments

rrlanham - 12-01-2011, 06:28 AM
- Reply
How are you using the CDN?

Richard

cbasics - 04-22-2012, 05:25 AM
- Reply
Hi,

"re-streaming an IP camera that supports H.264 video and AAC or MP3 audio"

We use Grandstream cameras that supports H264 but uses G711 as the audio codec. Can we still restream the audio and video from this camera if we use the transcoder add-on? Do we have to use any special settings in the application.xml for this?

rrlanham - 04-22-2012, 07:43 AM
- Reply
Yes, Wowza Transcoder supports G711 audio for decode. It will be transcoded to AAC. If your clients are recent versions of Flash only, G711 might work without transcoding.

Richard

alexpfo - 05-08-2012, 07:05 PM
- Reply
recently installed Wowza, I did not settings of applications, only the examples installed. Only if I set up a flash player for shoutcast relaying using the following addresses:
rtmp :/ / radioexemplo.com.br: 1835/shoutcast
http://radioexemplo.com.br:8005

usually it transmits, such as blocking it and accept only the applications I create.

thank you

whiteday910 - 05-13-2012, 09:43 PM
- Reply
I`m a newbie programer ㅠㅠ , I followed this guide but I couldn't play video , so I have a question . where I write my IP cam's RTSP URL like rtsp://device-ip/profile4/media.smp (samsung IP CAM style) .
http://211.221.225.24/for_link_other...ion/image1.png
http://211.221.225.24/for_link_other...ion/image2.png
http://211.221.225.24/for_link_other...ion/image3.png

I don't know . please help me ㅠㅠ

rrlanham - 05-14-2012, 05:27 AM
- Reply
Use a text file in the content folder with a .stream extension. Put the rtsp url in that file on one line, then use the file name as stream name. Use it in StreamManager to start the stream and in your players to play the live stream. Make sure that file is plain text and that it has a .stream extension not a .txt extension.

Richard

some user - 06-01-2012, 03:16 AM
- Reply
Just installed ami-8c1dc6e5 (64 bit, byol)

No examples folder was included.

Made this part confusing:

Playback

To play using Adobe Flash player (RTMP)

Double-click [install-dir]/examples/LiveVideoStreaming/client/live.html, enter the information below and click the Play button.

Double-click? I guess that was a windows-specific tip but just confused me more.

rrlanham - 06-01-2012, 05:41 AM
- Reply
Examples are not included in EC2 because you need to run them from either a web server or your local file system. Install a copy of Wowza using a Developer license on your local computer to get them

Richard

pronat - 10-23-2012, 10:15 PM
- Reply
Hi,

How can we secure the stream from an IP camera to a Wowza server?

Ex: if someone knows the publish url, he can publish a stream to Wowza server.

Thanks,
Anh

rrlanham - 10-24-2012, 05:25 AM
- Reply
Anh,

Use StreamNameAlias addon:

http://www.wowza.com/forums/content....ameAlias-AddOn

There is a security aspect to this addon. You will remove the default rule from the stream alias map file and add your allowed camera IP(s)

Richard

rtoensing - 12-14-2012, 07:03 AM
- Reply
I've went through the above instructions multiple times but when I log in to the stream manager and try to "start receiving stream" nothing happens. I'm using Amazon EC2 Windows 2008 server. I've also opened the proper ports on the server.

Any ideas?

Thanks!

tim_d - 12-14-2012, 09:46 AM
- Reply
rtoensing,

What do you mean by "nothing happens?" Does the URL not respond? Are you unable to view your stream? Please describe this in a little more detail. Also, do you see statements in your logs that might indicate something is happening that you don't see?

-Tim

rtoensing - 12-19-2012, 01:52 PM
- Reply
I actually got this working. I do have another question. I'm using EC2 with Windows Server 2008, the stream is running locally on the server with Wowza, but I'm wondering how I can use Flash or JW player to post it on a web page.

Jimbolino - 01-31-2013, 09:19 AM
- Reply
Hi, i can't figure out what i'm doing wrong.

I've been connecting with ip cameras via the MediaCaster API.
The streams are being started via mediacaster.startStream("rtsp://usernameassword@x.x.x.x/y/stream1:554", "rtp");

On my development machine (Windows) this works without problems.

However on our test server (Ubuntu Linux), the streams are continuously timing out with the following message:
INFO server comment - RTPMediaCaster.streamTimeout[1004028121bserver/_definst_:rtsp://usernameassword@x.x.x.x/y/stream1:554]: timeout:12000 diff:12011 reason:101

rrlanham - 02-02-2013, 04:15 PM
- Reply
It's a connectivity problem. Perhaps TCP port 554 needs to be opened

Richard

Jimbolino - 02-04-2013, 02:07 AM
- Reply
Server and ip cams are on the same network, there is no firewall.

If i enable rtsp debugging, i'm seeing "RTSP/1.0 200 OK", so the connection is established right?

rrlanham - 02-05-2013, 04:45 AM
- Reply
Yes, that's right. So it is a network issue, or problem with the source.

Richard

Jimbolino - 02-11-2013, 07:24 AM
- Reply
If it's a network problem, how come i see the RTSP handshake (RTSP/1.0 200 OK) ?
- i am able to connect with telnet to the cameras
- the cameras are on local network, there are no firewalls
- wowza running on windows is able to connect perfectly

I've noticed the folowing error on the server:
- RTPSessionDescriptionDataProviderBasicRTSPHandler: exceptionCaught: java.lang.NoClassDefFoundError: java/nio/charset/StandardCharsets

Also i've tried binding to a specified ip, with setting the rtspBindIpAddress value in Application.xml and Applications.xml, without result (it remains null) :
- DEBUG server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.d oConnect: hostname:192.168.1.76 port:554 timeout:4 rtspBindIpAddress:null path:/1/stream3

Jimbolino - 02-12-2013, 01:56 AM
- Reply
I've upgraded the server from java 1.6 to 1.7 and the problem seems resolved.

mpr310 - 02-26-2013, 04:21 AM
- Reply
Helo,

I'v installed WMS 3.5.2 and made all exactly according to this HOWTO. "[install-dir]/conf/live/Application.xml" downloaded from this page. But "re-streaming" isn't work. Wowza connected to camera and don't "re-streaming". There is that in access.log:
...
2013-02-26 16:30:38 YEKT comment server DEBUG 200 - v=0
o=- 1 1 IN IP4 127.0.0.1
s=Media Server
a=type:broadcast
t=0 0
a=x-timezone=GMT+06:00 Asia/Dhaka;index=25;dst=0
m=video 0 RTP/AVP 96
a=proto:RTP/AVP/TCP;interleaved=0-1
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1;profile-level-id=4D401F;sprop-parameter-sets=J01AH42NKBQHtgLUBAQFAAADA+gAACcQ6EAElAACkzLvL jQgAkoAAUmZd5cE+iw=,KO48gA==
a=control:track0
m=application 0 RTP/AVP 97
a=proto:RTP/AVP/TCP;interleaved=2-3
a=rtpmap:97 VND.ONVIF.METADATA/8000
a=control:track1
- - - 717.325 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:30:38 YEKT comment server INFO 200 - RTPSessionDescriptionDataProviderBasicRTSPWorker.b uildSDPData: sessionId:30E909722FA2F8A96BC0AF79D0DFC5 sessionTimeout:20000 - - - 717.326 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:30:39 YEKT comment server INFO 200 - RTPSessionDescriptionDataProviderBasic.getStreamIn fo[live/kumz1]: RTSP/RTP re-streaming. Success, received SDP data. - - - 717.446 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:30:39 YEKT comment server DEBUG 200 - sdp: v=0 - - - 717.447 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:30:39 YEKT comment server DEBUG 200 - sdp: o=- 1 1 IN IP4 127.0.0.1 - - - 717.447 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:30:39 YEKT comment server DEBUG 200 - sdp: s=Media Server - - - 717.447 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:30:39 YEKT comment server DEBUG 200 - sdp: a=type:broadcast - - - 717.448 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:30:39 YEKT comment server DEBUG 200 - sdp: t=0 0 - - - 717.448 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:30:39 YEKT comment server DEBUG 200 - sdp: a=x-timezone=GMT+06:00 Asia/Dhaka;index=25;dst=0 - - - 717.448 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:30:39 YEKT comment server DEBUG 200 - sdp: m=video 0 RTP/AVP 96 - - - 717.449 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:30:39 YEKT comment server DEBUG 200 - sdp: a=proto:RTP/AVP/TCP;interleaved=0-1 - - - 717.449 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:30:39 YEKT comment server DEBUG 200 - sdp: a=rtpmap:96 H264/90000 - - - 717.449 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:30:39 YEKT comment server DEBUG 200 - sdp: a=fmtp:96 packetization-mode=1;profile-level-id=4D401F;sprop-parameter-sets=J01AH42NKBQHtgLUBAQFAAADA+gAACcQ6EAElAACkzLvL jQgAkoAAUmZd5cE+iw=,KO48gA== - - - 717.449 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:30:39 YEKT comment server DEBUG 200 - sdp: a=control:track0 - - - 717.45 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:30:39 YEKT comment server DEBUG 200 - sdp: m=application 0 RTP/AVP 97 - - - 717.45 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:30:39 YEKT comment server DEBUG 200 - sdp: a=proto:RTP/AVP/TCP;interleaved=2-3 - - - 717.45 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:30:39 YEKT comment server DEBUG 200 - sdp: a=rtpmap:97 VND.ONVIF.METADATA/8000 - - - 717.451 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:30:39 YEKT comment server DEBUG 200 - sdp: a=control:track1 - - - 717.451 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:30:39 YEKT comment server DEBUG 200 - LiveReceiver.onFlushNotifyClients[live/kumz1/]: false - - - 717.452 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:29:11 YEKT comment server DEBUG 200 - LiveReceiver.flushInterval[live/kumz1/]: 50 - - - 629.873 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:29:11 YEKT comment server DEBUG 200 - LiveReceiver.verboseDebug[live/kumz1/]: false - - - 629.873 - - - - - - - - - - - - - - - - - - - - - - - - -
2013-02-26 16:29:11 YEKT create stream INFO 200 - - _defaultVHost_ live kumz1 0.001 - 80 null 127.0.0.1 rtsp - known 209580319 0 0 47 0 0 0 kumz1.stream - - - - - null null - null -
2013-02-26 16:29:11 YEKT comment server WARN 200 - Failed to find an appropriate depacketizer for this track (VND.ONVIF.METADATA) _defaultVHost_ live kumz1 629.874 - 80 null 127.0.0.1 rtsp - known 209580319 0 0 - - - - - - - - - - - - - null -
2013-02-26 16:29:11 YEKT comment server WARN 200 - Failed to find an appropriate depacketizer for this track (H264) _defaultVHost_ live kumz1 629.875 - 80 null 127.0.0.1 rtsp - known 209580319 0 0 - - - - - - - - - - - - - null -
2013-02-26 16:29:11 YEKT publish stream INFO 200 kumz1.stream - _defaultVHost_ live kumz1 0.002 - 80 null 127.0.0.1 rtsp - known 209580319 0 0 47 0 0 0 kumz1.stream - - - - - null null - null -
2013-02-26 16:29:11 YEKT comment server DEBUG 200 - *** RTSPMessageSend ***
...

Text is bolded by me. Is Wowza not understand rtsp stream from my camera? (LTV-423). May be I do something wrong.
Can anybody comment?

How to re-stream video from an IP camera (RTSP/RTP re-streaming)

Contents

Tutorial

Configuration

Publishing the stream

Playback

Adobe Flash Player (RTMP)

Adobe Flash Player (San Jose/Adobe HDS)

Apple iOS device (Cupertino/Apple HLS)

Microsoft Silverlight (Smooth Streaming)

RTSP/RTP player

Flash RTMP clients only

Troubleshooting

Check your IP camera source using VLC

RTSP/RTP

Additional property configuration needed for some cameras

How to turn on/off audio and video tracks

How to add additional logging for RTSP debugging

Common problems with .stream files

Property to change AAC packetization method

Flash playback

Problematic SDP files

Wowza Media

Article List

Categories