Results 1 to 7 of 7

Thread: 2.2.4 RTPMediaCaster timeout reason 101

  1. #1
    Join Date
    May 2011
    Posts
    21

    Default 2.2.4 RTPMediaCaster timeout reason 101

    I'm seeing this in my logs. Wowza goes and gets the rtsp stream but seems to not be able to push it out to flash or iphone client.

    INFO server comment - LivePlayer.play[train/_definst_/train.stream]: Dynamic Stream Markers are on.
    INFO server comment - firstPacket: TCP:$2
    INFO server comment - firstPacket: TCP:$3
    INFO server comment - firstPacket: TCP:$0
    INFO server comment - firstPacket: TCP:$1
    INFO server comment - RTPMediaCaster.streamTimeout[1945910404:train/_definst_:train.stream]: timeout:12000 diff:12397 reason:101
    INFO server comment - RTPMediaCaster.resetConnection[1945910404:train/_definst_:train.stream]:
    INFO server comment - RTPMediaCaster.closeRTPSession[1945910404:train/_definst_:train.stream]
    INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.c lose closeSession
    INFO stream unpublish train.stream -

  2. #2
    Join Date
    May 2011
    Posts
    21

    Default

    I should add I copied the 2.2.1 Server.xml, would that be a problem? Is there a way to get Server.xml from 2.2.4 without reinstalling everything?

  3. #3
    Join Date
    Dec 2007
    Posts
    25,637

    Default

    Copying old Server.xml wasn't a good idea, and we don't have back up files, but it's probably not a factor in this case. It just looks like a problem connecting to that stream, a network issue or problem with the source maybe.

    Richard

  4. #4
    Join Date
    May 2011
    Posts
    21

    Default

    I've adjusted the source by requesting /mpqvga instead of /video.cgi

    The camera is a Planet ICA-H312

    Now I see:


    INFO stream create - -
    INFO server comment - MediaStreamMediaCasterPlay: startPlay
    INFO server comment - LivePlayer.play[train/_definst_/train.stream]: Dynamic Stream Markers are on.
    INFO stream play train.stream -
    WARN server comment - RTPDePacketizerRFC3984H264.handleRTPPacket: Unsupported packet type: STAP-B
    WARN server comment - RTPDePacketizerRFC3984H264.handleRTPPacket: Unsupported packet type: FU-B
    INFO server comment - LiveStreamPacketizerCupertino.endChunkTS[train/_definst_/train.stream]: Add chunk: id:2 a/v/k:0/240/12 duration:9983
    WARN server comment - RTPDePacketizerRFC3984H264.handleRTPPacket: Unsupported packet type: FU-B
    WARN server comment - RTPDePacketizerRFC3984H264.handleRTPPacket: Unsupported packet type: STAP-B
    WARN server comment - RTPDePacketizerRFC3984H264.handleRTPPacket: Unsupported packet type: FU-B
    INFO server comment - LiveStreamPacketizerCupertino.endChunkTS[train/_definst_/train.stream]: Add chunk: id:3 a/v/k:0/231/14 duration:9611
    WARN server comment - RTPDePacketizerRFC3984H264.handleRTPPacket: Unsupported packet type: STAP-B

    I'm definitely getting a stream, but black screen shows on my desktop player.

  5. #5
    Join Date
    May 2011
    Posts
    21

    Default

    Just updating. I am now pulling this stream with http, not h264, and piping through ffmpeg. It's pulling a stream. Seeing this in the log.

    2011-06-02 21:41:03 GMT play stream INFO 200 camera.sdp - _defaultVHost_ train _definst_ 0.433 [any] 1935 rtmp://example.net:1935/train/_definst_ x.x.x.x rtmp http://example.com/jwplayer/player.swf MAC 10,2,153,1 1258119952 3643 3493 1 0 0 0 camera.sdp - - - - - rtmp://example.net:1935/train/_definst_/camera.sdp rtmp://example.net:1935/train/_definst_/camera.sdp rtmp://example.net:1935/train/_definst_ -
    2011-06-02 21:41:04 GMT comment server WARN 200 - RTPDePacketizerRFC3984H264.handleRTPPacket: Unsupported packet type: MTAP-24 - - - 64766.186 - - - - - - - - - - - -
    2011-06-02 21:41:08 GMT comment server WARN 200 - RTPDePacketizerRFC3984H264.handleRTPPacket: Unsupported packet type: FU-B - - - 64769.722 - - - - - - - - - - - -

  6. #6
    Join Date
    Dec 2007
    Posts
    25,637

  7. #7
    Join Date
    Feb 2012
    Posts
    6

    Default

    Hello
    we also have a problem with this reason )

    maybe problem is because of port ?..

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •