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

    This tutorial provides the basic steps for using Wowza Streaming Engine™ software to re-stream an IP camera that supports H.264 video and AAC or MP3 audio. 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.

    Contents



    Tutorial

    Troubleshooting


    Related Articles

    Tutorial


    Configuration


    Wowza Streaming Engine Manager configuration
    This section shows you how to set up a live streaming application in Wowza Streaming Engine Manager. Users play the live stream to view an event as it happens. Live streams are sent to the streaming engine from an encoder that delivers a stream in the MPEG-2 Transport Stream (MPEG-TS) format. The example uses an application named live, which is included in default installations of Wowza Streaming Engine software 4.0. The procedure is the same if you want to create a new live streaming application.

    You can use the Streaming Engine manager with the latest versions of most web browsers that support HTML5 and Cascading Style Sheets level 3 (CSS 3). We recommend the Google Chrome browser.

    1. Start Wowza Streaming Engine Manager.

    2. In the manager Welcome page, click Applications at the top of the page.

    3. Configure the live application:

      1. In the contents pane, click live. (This example uses the installed live application. If you want to create a new live streaming application, Click Add, then Live, and then follow the instructions in the UI.)

      2. On the Setup tab, click Edit.


      3. Select the following Playback Types options: MPEG-DASH, Adobe HDS, Apple HLS, Microsoft Smooth Streaming, and RTSP/RTP. Accept the defaults for other settings.


      4. Click Save.

        The following alert will appear after each configuration change. Wait until all changes are complete before you restart.


      5. Configure outgoing (playback) authentication:

        1. In the contents pane, click Outgoing Security.

        2. Click Edit.


        3. Under Client restrictions, select No client restrictions.


        4. Click Save.

      6. Configure encoder publishing authentication:

        1. In the contents pane, click Incoming Security.

        2. Click Edit.



        3. Under RTMP Publishing, select Require password authentication.

        4. Under RTSP Publishing, select Require password authentication.

        5. Under Client Restrictions, select No client restrictions.
        6. Click Save.

      7. Restart the application.



    The application runs whenever Streaming Engine software is running.

    Configuration in XML

    This section provides the basic steps for setting up an application for live streaming and configuring Application.xml.
    Note: If you created your application as described in the previous section, skip this section. Earlier versions of the server software donít support the manager, so you must edit Application.xml in a text editor. If you make changes to Application.xml and youíre using the Streaming Engine software, any supported settings will be displayed in the manager the next time itís started.
    1. Create application folder [install-dir]/applications/live.

    2. Create configuration folder [install-dir]/conf/live and copy [install-dir]/conf/Application.xml to this new folder.

    3. Edit the newly copied Application.xml file and make the following changes (some of these settings may already be present):

      1. Set the Streams/StreamType property to:
        Code:
        <StreamType>live</StreamType>
      2. Set the HTTPStreamers property to:
        Code:
        <LiveStreamPacketizers>cupertinostreamingpacketizer, smoothstreamingpacketizer, sanjosestreamingpacketizer, 
             mpegdashstreamingpacketizer</LiveStreamPacketizers>
      3. Set the Streams/LiveStreamPacketizers property to:
        Code:
        <LiveStreamPacketizers>cupertinostreamingpacketizer, smoothstreamingpacketizer, 
           sanjosestreamingpacketizer, mpegdashstreamingpacketizer
           </LiveStreamPacketizers>
      4. Set the RTP/Authentication/PlayMethod property to:
        Code:
        <PlayMethod>none</PlayMethod>
        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>
                       <!-- udp, interleave -->
             		<RTPTransportMode>interleave</RTPTransportMode>
                  </RTSP>
             </RTP>
             <!-- Properties defined here will override any properties defined in conf/MediaCasters.xml for any MediaCasters loaded by this application -->
             <Properties>
             </Properties>
        </MediaCaster>
    4. Start the Streaming Engine software.


    Publishing the stream

    This section provides the basic steps for creating a .stream file to publish your live stream to the Streaming Engine software.

    Publishing the Stream in Wowza Streaming Engine manager


    1. Consult your MPEG-TS encoder documentation to configure an outgoing live stream.

    2. Create .stream file:

      1. In the contents pane, click Stream Files.

      2. Under Virtual Host Stream Files, click Add Stream File.



      3. In the Add Stream File dialog box, enter a name for the stream.

      4. Enter the URI of the stream.


      5. Click Add.

      6. In the contents pane, click Startup Streams.

      7. Under Virtual Host Startup Streams, click Add Startup Stream.



      8. In the Add to Startup Streams dialog, enter the name of the stream you created in step c. For Application Name, enter live. Select the Mediacaster Type and the Application Instance.



      9. In the contents pane, click Server Setup.

      10. Restart the server, using the Restart button.




    Publishing the stream in XML


    This section provides the basic steps for creating a .stream file to publish your live stream to the Streaming Engine software.
    Note: If you published a stream as described in the previous section, skip this section. Earlier versions of the server software donít support the Streaming Engine manager, so you must edit Application.xml in a text editor. If you make changes to Application.xml and youíre using the Streaming Engine software, any supported settings will be displayed in the manager the next time itís started.
    1. 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.
    2. 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
    3. Start the Streaming Engine software.

    4. 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 in Wowza Streaming Engine Manager

    1. In the Applications contents pane, click live.

    2. Click Test Players.



    3. Enter Server and Stream.

    4. Click Start.


    The players are also online at www.wowza.com/testplayers

    Example players

    You can also use the players installed at [install-dir]/examples/ to test your streaming applications.

    For more information see the following articles:



    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 by using the VideoLAN VLC player:

    1. Open the VLC player.

    2. Select menu item Media > Open Network Stream, enter your camera's RTSP URL, and then click Play.

    3. 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 the Streaming Engine software. See How to use VLC as a live stream encoder with Wowza Streaming Engine (MPEG-TS) for an example that uses VLC.
    RTSP/RTP

    RTSP/RTP streaming is used to stream to Android and BlackBerry mobile devices. Android mobile devices formerly supported Adobe Flash player, but Android no longer supports Flash. Newer Android devices now support Apple HLS. HLS works best on Android 4.0 devices and above.

    To stream to RTSP/RTP, be sure that UDP ports 0-65535 are open and properly mapped to the server that is running Wowza Streaming Engine software.
    Note: To configure Wowza Streaming Engine software properly for RTSP/RTP streaming, carefully follow the instructions provided in How to troubleshoot RTSP/RTP playback.

    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. For more information, see How to generate and control MPEG-TS output for set-top boxes.

    Some IP cameras may fail when Wowza Streaming Engine software 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 Streaming Engine software 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: Wowza Media Server software 3.0.5 or later is required.
    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.

    Missing Audio or Video

    If audio or video is missing from the IP camera, check the logs to see if either of the following warning log statements are present:

    Code:
    RTPSessionDescriptionDataProviderBasicRTSPWorker.b  uildSDPData: SDP data missing rtpmap entry for [audio] track. Try adding MediaCaster/Property rtspDefaultAudioRTPMap with track media information. 
    RTPSessionDescriptionDataProviderBasicRTSPWorker.b  uildSDPData: SDP data missing rtpmap entry for [video] track. Try adding MediaCaster/Property rtspDefaultVideoRTPMap with track media information.
    Add the following property to the MediaCaster/Properties in [install-dir]/conf/[application]/Application.xml with the proper media definition information. For example: for a G.711 mu-law audio track, the entry might look like this:

    Code:
       <Property> 
          <Name>rtspDefaultAudioRTPMap</Name> 
          <Value>PCMU/8000</Value> 
       </Property>
    How to add additional logging for RTSP debugging

    You can log extra debug information to the log file about the RTSP handshake between the Streaming Engine software 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 Streaming Engine software can output AAC audio by 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.RTPPacketizerMPEG4LAT  M</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 Streaming Engine software 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 Streaming Engine 4.0.0 on 02-11-2014
    Comments 140 Comments
    1. rrlanham -
      How are you using the CDN?

      Richard
    1. cbasics -
      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?
    1. rrlanham -
      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
    1. alexpfo -
      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
    1. whiteday910 -
      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 ㅠㅠ
    1. rrlanham -
      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
    1. some user -
      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.
    1. rrlanham -
      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
    1. pronat -
      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
    1. rrlanham -
      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
    1. rtoensing -
      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!
    1. tim_d -
      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
    1. rtoensing -
      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.
    1. Jimbolino -
      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
    1. rrlanham -
      It's a connectivity problem. Perhaps TCP port 554 needs to be opened

      Richard
    1. Jimbolino -
      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?
    1. rrlanham -
      Yes, that's right. So it is a network issue, or problem with the source.

      Richard
    1. Jimbolino -
      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.doConnect: hostname:192.168.1.76 port:554 timeout:4 rtspBindIpAddress:null path:/1/stream3
    1. Jimbolino -
      I've upgraded the server from java 1.6 to 1.7 and the problem seems resolved.
    1. mpr310 -
      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+gAACcQ6EAElAACkzLvLjQgAkoAAUmZd5cE+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.buildSDPData: sessionId:30E909722FA2F8A96BC0AF79D0DFC5 sessionTimeout:20000 - - - 717.326 - - - - - - - - - - - - - - - - - - - - - - - - -
      2013-02-26 16:30:39 YEKT comment server INFO 200 - RTPSessionDescriptionDataProviderBasic.getStreamInfo[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+gAACcQ6EAElAACkzLvLjQgAkoAAUmZd5cE+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?