Re-streaming an RTSP stream through Wowza Pro (RTSP/RTP)

Wowza Streaming Engine
201

Need some hints here…I have Wowza Media Server Pro10 1.7.2 build12107 installed and running well with live and rtplive apps. No problems with “live” app streaming from FMLE 3.0 all is well. No problem connecting to stream with rtplive app via RTSP from Axis M1011 cameras, but I have a problem that may fall somewhere in the middle, so any suggestions appreciated. Utilizing Wowza’s ability to connect directly to RTSP/h.264 stream, I get tremendous tiling and loss of partial video out of Wowza viewing on JWPlayer via h.264. When I view the video directly via the Axis Live View screen by going directly to the camera the video is perfect in h.264

I have installed components StreamNameAlias (works great) and UDP “jitter” filter (did not find any improvements). I do see packet loss in the jitter filter log entries

My setup is that I am going through a wireless IP bridge between the camera and the Wowza server, but all on the same LAN. To clarify, the video directly from the Axis Live View screen going through the wireless IP bridge is perfect, but when I use rtp-live with Wowza to connect I get the tiling and video dropouts.

My theory is that when I go directly to the camera IP via the wireless bridge, it utlizes Axis Media Control (AMC) and selects RTSP via RTP and I believe TCP transport…when I connect to the camera stream via the wireless bridge to Wowza, there is no selection available for transport protocol therefore I assume uses unicast UDP…so does my theory make any sense, has anyone experienced this and does anyone (help Charlie) have any suggestions…I do not want to just say it is Wowza because the wireless bridge is there also…OK I knew you were going to ask…if you bypass the bridge and hardwire directly to the camera, its not half as bad but not anywhere as good as with the Axis Live View

Thanks,

The Wowza Forum is one of the best

Richard

202

It sounds like you application is not setup properly. You should not be getting packet loss if you are using interleaved mode. Post your Application.xml file so we can take a look at it.

Charlie

C:\Program Files\Wowza Media Systems\Wowza Media Server Pro 1.7.2\conf\rtplive\Application.xml as follows below:

true

rtp-live

${com.wowza.wms.context.VHostConfigHome}/content

sortPackets

true

Boolean

sortBufferSize

500

Integer

-1

*

*

*

*

digest

senderreport

12000

rtpDePacketizerWrapper

com.wowza.wms.rtp.depacketizer.RTPDePacketizerWrapperPacketSorter

rtpDePacketizerPacketSorterBufferTime

500

Integer

rtpDePacketizerPacketSorterFlushTime

10

Integer

rtpDePacketizerPacketSorterLogPacketLoss

false

Boolean

base

Base

com.wowza.wms.module.ModuleCore

properties

Properties

com.wowza.wms.module.ModuleProperties

logging

Client Logging

com.wowza.wms.module.ModuleClientLogging

flvplayback

FLVPlayback

com.wowza.wms.module.ModuleFLVPlayback

ModuleStreamNameAlias

ModuleStreamNameAlias

com.wowza.wms.plugin.streamnamealias.ModuleStreamNameAlias

streamNameAliasFile

${com.wowza.wms.context.VHostConfigHome}/conf/StreamNameAliasMap.txt

streamNameAliasPathDelimiter

/

streamNameAliasNameDelimiter

=

streamNameAliasDebug

true

Boolean

203

You have the interleaved property commented out. Change this:

To this:

Richard

Made the following change per your information:

forceInterleaved

true

Boolean

saved and refreshed Flash client…problem with tiling remains…

I can send you link to the website if you would like to observe the tiling…do you have an email that I can send link to?

204

The loss of video is displayed here (note the black bands of video at the bottom of right flash video display) and the AMC control that sets the transport protocol for the camera when viewing direct is also pictured here.

http://i710.photobucket.com/albums/ww103/tenrocdoc/Tiling.jpg

http://i710.photobucket.com/albums/ww103/tenrocdoc/AMC.jpg

205

Sure, send link to support@wowza.com

Did you restart Wowza after change? (it’s not always necessary with Application.xml change but it can’t hurt)

Richard

Richard,

I think you solved the problem…I did not Stop/Restart Wowza…did not know I needed to, but following restart both streams are looking good…awesome…

I am also seeing a different “firstPacket” response than I normally see:

INFO server comment 2009-10-20 20:21:38 - - - - - 13.984 - - - - - - - firstPacket: TCP:$1

INFO server comment 2009-10-20 20:21:38 - - - - - 14.0 - - - - - - - RTCPHandler.sendFirstRTCPRR[677056552,1,null]

INFO server comment 2009-10-20 20:21:39 - - - - - 15.141 - - - - - - - firstPacket: TCP:$1

INFO server comment 2009-10-20 20:21:39 - - - - - 15.141 - - - - - - - RTCPHandler.sendFirstRTCPRR[2380142032,1,null]

The TCP:$1 is new…please explain

Take a look at the website I sent email to you but tiling and block video loss is gone…I am running a very low bitrate at the moment on purpose.

What lead you to think of the interleaving issue?

Richard

206

What do you seen in the logs when Wowza connects to the stream? If you are truley using interleaved mode the log entries should look different. Post the log entries that show the connection since you have changed this setting.

Charlie

Charlie,

I caught your response after sending my last…I did post some of the log, see my last post…could you explain the difference I am seeing in the FirstPacket responses…I am interested in the technical aspects of this…although having the video looking good is great also…

Thanks guys! Both Richard and Charlie!!!

207

We always suggest interleaving. It was just misconfigured (commented out) in your config. It avoids packet loss by sending the video/audio packets over lossless TCP rather then UDP.

Charlie

That is exactly what I wanted to accomplish TCP rather than UDP. The 900MHz radios we are streaming the video from the Axis cameras have a problem with unthrottled UDP also…this is a real plus…

BTW, the rtplive app was, I believe, exactly as I initially modified it from the original per the forum without commenting out the interleaving…I added the StreamNameAlias and Jitter Filter lines…would there have been any reason you can think of that I would have commented out the interleaving for some other reason or did it come out of the box that way…just curious…I am running Wowza Media Server Pro10 1.7.2 build12107

208

Thanks for all the help regarding interleaving and TCP…reviewing the setup instructions from the initial forum post to set up rtplive, I see now where the error was made with commenting out the interleave code…things are working nicely now that is resolved…Regards, til next time. Richard

209

Back again…RTSP (h.264) ingest from Axis M1011 series that was discussed above working wonderfully…that was the prototype camera…unfortunately the camera we need to use in the final version just arrived this morning…a new Sony SNC-RZ50N PTZ that can handle a single output of h.264 as single codec or dual codec MJPEG/MPEG-4…the MJPEG works normal.

The syntax for the Sony is rtsp:///media/video0 and if the camera is set via its controls to h.264 it streams good looking video to VLC 1.0.2 Goldeneye without a problem although the debug log shows lots of errors in the VLC debugger log:

sps_id out of range

sps_id out of range

number of reference frames exceeds max (probably corrupt input), discarding one

sps_id (32) out of range

sps_id out of range

sps_id out of range

sps_id out of range

sps_id out of range

sps_id (32) out of range

sps_id out of range

sps_id out of range

sps_id out of range

sps_id out of range

non-existing PPS 223 referenced

decode_slice_header error

no frame!

non-existing PPS 223 referenced

decode_slice_header error

no frame!

non-existing PPS 223 referenced

decode_slice_header error

no frame!

When I attempt to stream the Sony 50RZ through Wowza, I do not get any video nor any first packets as I do with the Axis M1011:

The Wowza log shows this:

INFO server comment - ModuleStreamNameAlias.onAppStart: streamNameAliasFile: C:\

Program Files\Wowza Media Systems\Wowza Media Server Pro 1.7.2\conf\StreamNameAl

iasMap.txt

INFO application app-start definst rtplive/definst

INFO session connect-pending 192.168.0.14 -

INFO session connect 192.168.0.14 -

INFO server comment - sortPackets[1]: sortBufferSize:500

INFO stream create - -

INFO server comment - ModuleStreamNameAlias.streamNameToAlias: streamName:sony2

alias:{pattern: “sony2” alias:“rtsp://192.168.0.100/media/video0” wildcardMatche

s:null} result:rtsp://192.168.0.100/media/video0

INFO server comment - ModuleStreamNameAlias.play: sony2=rtsp://192.168.0.100/med

ia/video0

INFO server comment - MediaStreamMediaCasterPlay: startPlay

INFO server comment - RTPMediaCaster.create

INFO server comment - RTPMediaCaster.init

INFO server comment - RTPMediaCaster.Reconnector: start

INFO server comment - RTPSessionTracker.add[rtsp://192.168.0.100/media/video0]:

1

INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.buildSDPD

ata: sessionId:1257115582 sessionTimeout:30000

INFO server comment - RTPSessionDescriptionDataProviderBasic.getStreamInfo: RTSP

/RTP re-streaming. Success, received SDP data.

INFO server comment - sortPackets[1]: sortBufferSize:500

INFO stream create - -

INFO stream create - -

INFO server comment - RTPDePacketizerWrapperPacketSorter.init: rtpDePacketizerPa

cketSorterBufferTime: 500

INFO server comment - RTPDePacketizerWrapperPacketSorter.init: rtpDePacketizerPa

cketSorterFlushTime: 10

INFO server comment - RTPDePacketizerWrapperPacketSorter.init: rtpDePacketizerPa

cketSorterLogPacketLoss: false

INFO stream publish rtsp://192.168.0.100/media/video0 -

INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.sessionSt

art: PLAY: rtsp://192.168.0.100/media/video0

INFO server comment - RTPMediaCaster.Reconnector: stop

I tried with interleave “true” and “false” but not difference…the JWplayer just “whirly-birds” but never times out.

I would really like to get the Sony going this weekend with RTSP…any hints of what the problem may be…I have read some of the forum posts about Soney packet problems, but the cam works with VLC fine.

Richard :confused:

210

The Sony cameras use a proprietary packetization scheme that we do not yet support. We may add support early in 2010.

Charlie

Boy, thats not good…both VLC and my surveillance software (Luxriot) can accept the Sony h.264 stream…no work-arounds at all for Wowza?

Charlie, you always have some good answer!! Nothing to adjust in Wowza that would help right now?

Thanks always for your fast replies…

Richard

VideoICU

211

Looks like we will stream MJPEG with the Sony then until possibly Wowza can accept it…dissappointing that Sony would do that…I thought the concept of an open spec (h.264/AVC) was for everyone to follow it.

Also unfortunately, Axis does not have but one h.264 PTZ for outdoor use at this time and the one they have is a little too “environmental” for our project. The little Axis M1011’s are great h.264 cameras and work wonderfully with Wowza but I need the PTZ capability they do not have.

Thanks for your quick response. Until next time…

Regards,

Richard

212

Back again with questions…I have two identical Axis IP cams that are streaming h.264 via RTSP/RTP, one is connected via wireless bridge to Wowza and works fine, the other is connected to Wowza via a Sprint 3G Broadband connection…

If you look back on prior posts on this topic, I use rtplive and SteamNameAlias and all works fine to ingest RTSP (h.264) via Wowza…we have worked all the bugs out of this.

Problem is that Wowza appears to connect to the 3G stream but only displays a blank flash player but does not time out…

Could you look at the Wowza log and see if it tells you anything regarding why the stream is not playing…for reference the icuvet1 stream is the 3G stream and does not play, the icuvet2 streams plays normally

Configure logging: file:///C:/Program Files/Wowza Media Systems/Wowza Media Serv
er Pro 1.7.2/conf/log4j.properties
INFO server server-start Wowza Media Server Pro10 1.7.2 build12107 -
INFO server comment - Serial number: XXXXX-XXXXX-XXXXX-XXXXX-TV4PB
INFO server comment - Maximum connections: 10
INFO server comment - Hardware Available Processors: 2
INFO server comment - Hardware Physical Memory: 253MB/1013MB
INFO server comment - Hardware Swap Space: 1683MB/2440MB
INFO server comment - Max File Descriptor Count: Unlimited
INFO server comment - OS Name: Windows XP
INFO server comment - OS Version: 5.1
INFO server comment - OS Architecture: x86
INFO server comment - OS CPU: pentium_pro+mmx pentium_pro pentium+mmx pentium i4
86 i386 i86
INFO server comment - Java Name: Java HotSpot(TM) Client VM
INFO server comment - Java Vendor: Sun Microsystems Inc.
INFO server comment - Java Version: 1.6.0_17
INFO server comment - Java VM Version: 14.3-b01
INFO server comment - Java Spec Version: 1.6
INFO server comment - Java Home: C:\Program Files\Java\jre6
INFO server comment - Java Max Heap Size: 762MB
INFO server comment - Java Architecture: 32
INFO server comment - CMDInterface now listening: [any]:8083
INFO server comment - vhost home directory: C:\Program Files\Wowza Media Systems
\Wowza Media Server Pro 1.7.2
INFO vhost vhost-start _defaultVHost_ -
INFO vhost comment _defaultVHost_ RTMP/RTMPT bind attempt ([any]:1935)
INFO vhost comment _defaultVHost_ Bind successful ([any]:1935)
INFO server comment - ModuleStreamNameAlias.onAppStart: streamNameAliasFile: C:\
Program Files\Wowza Media Systems\Wowza Media Server Pro 1.7.2\conf\StreamNameAl
iasMap.txt
INFO application app-start _definst_ rtplive/_definst_
INFO session connect-pending 192.168.0.14 -
INFO session connect-pending 192.168.0.14 -
INFO session connect 192.168.0.14 -
INFO session connect 192.168.0.14 -
INFO server comment - ModuleStreamNameAlias.onAppStart: streamNameAliasFile: C:\
Program Files\Wowza Media Systems\Wowza Media Server Pro 1.7.2\conf\StreamNameAl
iasMap.txt
INFO application app-start _definst_ live/_definst_
INFO session connect-pending 192.168.0.14 -
INFO session connect 192.168.0.14 -
INFO server comment - sortPackets[1]: sortBufferSize:500
INFO server comment - sortPackets[1]: sortBufferSize:500
INFO stream create - -
INFO stream create - -
INFO stream create - -
INFO server comment - ModuleStreamNameAlias.streamNameToAlias: streamName:*flv:i
cuvet2.flv alias:{pattern: "*flv:icuvet2.flv" alias:"rtsp://192.168.0.21:554/axi
s-media/media.amp?videocodec=h264&resolution=480x360&videobitrate=500&videomaxbi
trate=650&fps=24&compression=25&videokeyframeinterval=32" wildcardMatches:{[0]:
"*"}} result:rtsp://192.168.0.21:554/axis-media/media.amp?videocodec=h264&resolu
tion=480x360&videobitrate=500&videomaxbitrate=650&fps=24&compression=25&videokey
frameinterval=32
INFO server comment - ModuleStreamNameAlias.streamNameToAlias: streamName:*flv:i
cuvet1.flv alias:{pattern: "*flv:icuvet1.flv" alias:"rtsp://remotecam.dyndns.org
:554/axis-media/media.amp?videocodec=h264&resolution=480x360&videobitrate=500&vi
deomaxbitrate=650&fps=24&compression=25&videokeyframeinterval=32" wildcardMatche
s:{[0]: "*"}} result:rtsp://remotecam.dyndns.org:554/axis-media/media.amp?videoc
odec=h264&resolution=480x360&videobitrate=500&videomaxbitrate=650&fps=24&compres
sion=25&videokeyframeinterval=32
INFO server comment - ModuleStreamNameAlias.streamNameToAlias: streamName:*flv:m
yStream.flv alias:{pattern: "*flv:myStream.flv" alias:"myStream" wildcardMatches
:{[0]: "*"}} result:myStream
INFO server comment - ModuleStreamNameAlias.play: *flv:myStream.flv=myStream
INFO server comment - ModuleStreamNameAlias.play: *flv:icuvet1.flv=rtsp://remote
cam.dyndns.org:554/axis-media/media.amp?videocodec=h264&resolution=480x360&video
bitrate=500&videomaxbitrate=650&fps=24&compression=25&videokeyframeinterval=32
INFO server comment - ModuleStreamNameAlias.play: *flv:icuvet2.flv=rtsp://192.16
8.0.21:554/axis-media/media.amp?videocodec=h264&resolution=480x360&videobitrate=
500&videomaxbitrate=650&fps=24&compression=25&videokeyframeinterval=32
INFO server comment - MediaStreamMediaCasterPlay: startPlay
INFO server comment - MediaStreamMediaCasterPlay: startPlay
INFO server comment - RTPMediaCaster.create
INFO server comment - RTPMediaCaster.create
INFO server comment - RTPMediaCaster.init
INFO server comment - RTPMediaCaster.init
INFO server comment - RTPMediaCaster.Reconnector: start
INFO server comment - RTPMediaCaster.Reconnector: start
INFO server comment - RTPSessionTracker.add[rtsp://192.168.0.21:554/axis-media/m
edia.amp?videocodec=h264&resolution=480x360&videobitrate=500&videomaxbitrate=650
&fps=24&compression=25&videokeyframeinterval=32]: 1
INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.buildSDPD
ata: sessionId:6958E06E sessionTimeout:60000
INFO server comment - RTPSessionDescriptionDataProviderBasic.getStreamInfo: RTSP
/RTP re-streaming. Success, received SDP data.
INFO server comment - sortPackets[1]: sortBufferSize:500
INFO stream create - -
INFO stream create - -
INFO server comment - RTPDePacketizerWrapperPacketSorter.init: rtpDePacketizerPa
cketSorterBufferTime: 500
INFO server comment - RTPDePacketizerWrapperPacketSorter.init: rtpDePacketizerPa
cketSorterFlushTime: 10
INFO server comment - RTPDePacketizerWrapperPacketSorter.init: rtpDePacketizerPa
cketSorterLogPacketLoss: false
INFO stream publish rtsp://192.168.0.21:554/axis-media/media.amp?videocodec=h264
&resolution=480x360&videobitrate=500&videomaxbitrate=650&fps=24&compression=25&v
ideokeyframeinterval=32 -
INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.sessionSt
art: PLAY: rtsp://192.168.0.21:554/axis-media/media.amp?videocodec=h264&resoluti
on=480x360&videobitrate=500&videomaxbitrate=650&fps=24&compression=25&videokeyfr
ameinterval=32
INFO server comment - RTPMediaCaster.Reconnector: stop
INFO server comment - firstPacket: TCP:$0
INFO stream play rtsp://192.168.0.21:554/axis-media/media.amp?videocodec=h264&re
solution=480x360&videobitrate=500&videomaxbitrate=650&fps=24&compression=25&vide
okeyframeinterval=32 -
INFO server comment - RTPSessionTracker.add[rtsp://remotecam.dyndns.org:554/axis
-media/media.amp?videocodec=h264&resolution=480x360&videobitrate=500&videomaxbit
rate=650&fps=24&compression=25&videokeyframeinterval=32]: 1
INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.buildSDPD
ata: sessionId:14127907 sessionTimeout:60000
INFO server comment - RTPSessionDescriptionDataProviderBasic.getStreamInfo: RTSP
/RTP re-streaming. Success, received SDP data.
INFO server comment - sortPackets[2]: sortBufferSize:500
INFO stream create - -
INFO stream create - -
INFO server comment - RTPDePacketizerWrapperPacketSorter.init: rtpDePacketizerPa
cketSorterBufferTime: 500
INFO server comment - RTPDePacketizerWrapperPacketSorter.init: rtpDePacketizerPa
cketSorterFlushTime: 10
INFO server comment - RTPDePacketizerWrapperPacketSorter.init: rtpDePacketizerPa
cketSorterLogPacketLoss: false
INFO stream publish rtsp://remotecam.dyndns.org:554/axis-media/media.amp?videoco
dec=h264&resolution=480x360&videobitrate=500&videomaxbitrate=650&fps=24&compress
ion=25&videokeyframeinterval=32 -
INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.sessionSt
art: PLAY: rtsp://remotecam.dyndns.org:554/axis-media/media.amp?videocodec=h264&
resolution=480x360&videobitrate=500&videomaxbitrate=650&fps=24&compression=25&vi
deokeyframeinterval=32
INFO server comment - RTPMediaCaster.Reconnector: stop
INFO server comment - firstPacket: TCP:$0
INFO server comment - firstPacket: TCP:$1
INFO server comment - RTCPHandler.sendFirstRTCPRR[2763802736,1,null]
INFO server comment - firstPacket: TCP:$1
INFO server comment - RTCPHandler.sendFirstRTCPRR[3354752087,1,null]
INFO stream play rtsp://remotecam.dyndns.org:554/axis-media/media.amp?videocodec
=h264&resolution=480x360&videobitrate=500&videomaxbitrate=650&fps=24&compression
=25&videokeyframeinterval=32 -

Thanks for all of the great assistance on this project…we are close!

Richard

213

Charlie…we are very close…jsut a little more tweeking

I instituted all changes you reccommended on last post.

I reduced bandwidth to minimal as you can see in Wowza Log below.

We are now getting video (great!) via the 3G but it runs for a couple of seconds, freezes for several seconds and restarts but does not seem to be synchronized with MediaCaster restarts per the added code you reccommended. I am receiving some packet loss per the log.

INFO stream play rtsp://remotecam.dyndns.org:554/axis-media/media.amp?videocodec

=h264&resolution=480x360&videobitrate=150&videomaxbitrate=250&fps=24&compression

=25&videokeyframeinterval=32 -

WARN server comment - packetLoss[rtsp://remotecam.dyndns.org:554/axis-media/medi

a.amp/trackID=1?videocodec=h264&resolution=480x360&videobitrate=150&videomaxbitr

ate=250&fps=24&compression=25&videokeyframeinterval=32]: last:120013 curr:120033

WARN server comment - packetLoss[rtsp://remotecam.dyndns.org:554/axis-media/medi

a.amp/trackID=1?videocodec=h264&resolution=480x360&videobitrate=150&videomaxbitr

ate=250&fps=24&compression=25&videokeyframeinterval=32]: last:120042 curr:120073

WARN server comment - packetLoss[rtsp://remotecam.dyndns.org:554/axis-media/medi

a.amp/trackID=1?videocodec=h264&resolution=480x360&videobitrate=150&videomaxbitr

ate=250&fps=24&compression=25&videokeyframeinterval=32]: last:120480 curr:120511

WARN server comment - packetLoss[rtsp://remotecam.dyndns.org:554/axis-media/medi

a.amp/trackID=1?videocodec=h264&resolution=480x360&videobitrate=150&videomaxbitr

ate=250&fps=24&compression=25&videokeyframeinterval=32]: last:120519 curr:120639

WARN server comment - LiveReceiver.resetSortBuffer[rtsp://remotecam.dyndns.org:5

54/axis-media/media.amp?videocodec=h264&resolution=480x360&videobitrate=150&vide

omaxbitrate=250&fps=24&compression=25&videokeyframeinterval=32]: 3531

INFO server comment - RTPMediaCaster.resetConnection:

INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.close clo

seSession

INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.onClose

INFO stream unpublish rtsp://remotecam.dyndns.org:554/axis-media/media.amp?video

codec=h264&resolution=480x360&videobitrate=150&videomaxbitrate=250&fps=24&compre

ssion=25&videokeyframeinterval=32 -

INFO server comment - RTPSessionTracker.remove[rtsp://remotecam.dyndns.org:554/a

xis-media/media.amp?videocodec=h264&resolution=480x360&videobitrate=150&videomax

bitrate=250&fps=24&compression=25&videokeyframeinterval=32]: 0:true

INFO stream destroy rtsp://remotecam.dyndns.org:554/axis-media/media.amp?videoco

dec=h264&resolution=480x360&videobitrate=150&videomaxbitrate=250&fps=24&compress

ion=25&videokeyframeinterval=32 -

INFO server comment - RTPMediaCaster.Reconnector: start

INFO server comment - RTPSessionTracker.add[rtsp://remotecam.dyndns.org:554/axis

-media/media.amp?videocodec=h264&resolution=480x360&videobitrate=150&videomaxbit

rate=250&fps=24&compression=25&videokeyframeinterval=32]: 1

INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.buildSDPD

ata: sessionId:2FD48026 sessionTimeout:60000

INFO server comment - RTPSessionDescriptionDataProviderBasic.getStreamInfo: RTSP

/RTP re-streaming. Success, received SDP data.

INFO server comment - sortPackets[10]: sortBufferSize:500

INFO stream create - -

INFO stream create - -

INFO server comment - RTPDePacketizerWrapperPacketSorter.init: rtpDePacketizerPa

cketSorterBufferTime: 500

INFO server comment - RTPDePacketizerWrapperPacketSorter.init: rtpDePacketizerPa

cketSorterFlushTime: 10

INFO server comment - RTPDePacketizerWrapperPacketSorter.init: rtpDePacketizerPa

cketSorterLogPacketLoss: true

INFO stream stop rtsp://remotecam.dyndns.org:554/axis-media/media.amp?videocodec

=h264&resolution=480x360&videobitrate=150&videomaxbitrate=250&fps=24&compression

=25&videokeyframeinterval=32 -

INFO stream publish rtsp://remotecam.dyndns.org:554/axis-media/media.amp?videoco

dec=h264&resolution=480x360&videobitrate=150&videomaxbitrate=250&fps=24&compress

ion=25&videokeyframeinterval=32 -

INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.sessionSt

art: PLAY: rtsp://remotecam.dyndns.org:554/axis-media/media.amp?videocodec=h264&

resolution=480x360&videobitrate=150&videomaxbitrate=250&fps=24&compression=25&vi

deokeyframeinterval=32

INFO server comment - RTPMediaCaster.Reconnector: stop

INFO server comment - firstPacket: TCP:$0

INFO server comment - firstPacket: TCP:$1

INFO server comment - RTCPHandler.sendFirstRTCPRR[288506997,1,null]

INFO stream play rtsp://remotecam.dyndns.org:554/axis-media/media.amp?videocodec

=h264&resolution=480x360&videobitrate=150&videomaxbitrate=250&fps=24&compression

=25&videokeyframeinterval=32 -

INFO server comment - RTPMediaCaster.resetConnection:

INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.close clo

seSession

INFO stream unpublish rtsp://remotecam.dyndns.org:554/axis-media/media.amp?video

codec=h264&resolution=480x360&videobitrate=150&videomaxbitrate=250&fps=24&compre

ssion=25&videokeyframeinterval=32 -

INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.onClose

INFO stream destroy rtsp://remotecam.dyndns.org:554/axis-media/media.amp?videoco

dec=h264&resolution=480x360&videobitrate=150&videomaxbitrate=250&fps=24&compress

ion=25&videokeyframeinterval=32 -

INFO server comment - RTPSessionTracker.remove[rtsp://remotecam.dyndns.org:554/a

xis-media/media.amp?videocodec=h264&resolution=480x360&videobitrate=150&videomax

bitrate=250&fps=24&compression=25&videokeyframeinterval=32]: 0:true

INFO server comment - RTPMediaCaster.Reconnector: start

INFO server comment - RTPSessionTracker.add[rtsp://remotecam.dyndns.org:554/axis

-media/media.amp?videocodec=h264&resolution=480x360&videobitrate=150&videomaxbit

rate=250&fps=24&compression=25&videokeyframeinterval=32]: 1

INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.buildSDPD

ata: sessionId:04C7263D sessionTimeout:60000

INFO server comment - RTPSessionDescriptionDataProviderBasic.getStreamInfo: RTSP

/RTP re-streaming. Success, received SDP data.

INFO server comment - sortPackets[11]: sortBufferSize:500

INFO stream create - -

INFO stream create - -

INFO server comment - RTPDePacketizerWrapperPacketSorter.init: rtpDePacketizerPa

cketSorterBufferTime: 500

INFO server comment - RTPDePacketizerWrapperPacketSorter.init: rtpDePacketizerPa

cketSorterFlushTime: 10

INFO server comment - RTPDePacketizerWrapperPacketSorter.init: rtpDePacketizerPa

cketSorterLogPacketLoss: true

INFO stream stop rtsp://remotecam.dyndns.org:554/axis-media/media.amp?videocodec

=h264&resolution=480x360&videobitrate=150&videomaxbitrate=250&fps=24&compression

=25&videokeyframeinterval=32 -

INFO stream publish rtsp://remotecam.dyndns.org:554/axis-media/media.amp?videoco

dec=h264&resolution=480x360&videobitrate=150&videomaxbitrate=250&fps=24&compress

ion=25&videokeyframeinterval=32 -

INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.sessionSt

art: PLAY: rtsp://remotecam.dyndns.org:554/axis-media/media.amp?videocodec=h264&

resolution=480x360&videobitrate=150&videomaxbitrate=250&fps=24&compression=25&vi

deokeyframeinterval=32

INFO server comment - RTPMediaCaster.Reconnector: stop

INFO server comment - firstPacket: TCP:$0

INFO server comment - firstPacket: TCP:$1

INFO server comment - RTCPHandler.sendFirstRTCPRR[794911971,1,null]

INFO stream play rtsp://remotecam.dyndns.org:554/axis-media/media.amp?videocodec

=h264&resolution=480x360&videobitrate=150&videomaxbitrate=250&fps=24&compression

=25&videokeyframeinterval=32 -

Any further thoughts…project requires 3G cellular remote data…we are close!

Richard

214

A couple of observations, since now seeing some video via the 3G link to compare to the direct camera viewer…

If you observe the camera directly via 3G using its built-in viewer (Axis uses a plug-in called Axis Media Control AMC) the AMC gives you options of RTSP connection type when you right-click the video pane itself…namely RTP over RTSP, RTP over RTSP over HTTP, RTP Unicast, RTP Multicast.

The connection type that corresponds to Wowza is RTP over RTSP and using that connection with the built in camera viewer gives the same results…video freezes every few seconds and viewer attempts to reconnect…just like Wowza.

If the built-in viewer is set to RTP over RTSP over HTTP then the video steams normally in the viewer with no freezes or reconnects…

Somewhere, I think this question was posed before…so how do we get Wowza to mimic what the viewer is doing and why is tunneling solving the problem?

Richard

215

If you wanted to investigate this more…what direction would you take…if I exclude this approach the elegance of the Wowza solution sort of goes out the window and we are left using multiple instances if FMLE…not good at all. I understand if Wowza will not do 3.) above then it won’t but any thoughts on adjustments to any of the parameters in Wowza that might affect the packetization, etc…

R

216

Charlie/Richard

With no joy in streaming RTP/RTSP via 3g (just large packet losses and stopping and starting of the stream) I am forced to revert back to a former possibility…UDP via Wowza…I believe that was the default out of the box.

As we have already covered before, RTP via HTTP works fine via 3G but I know Wowza does not support this ingest type.

Axis Unicast RTP (UDP per Wireshark capture) streams very well via 3G to the Axis viewer set to h.264 Unicast RTP also. I would like to try that via Wowza if possible.

I need help in getting back to that UDP mode in Wowza…I changed ‘forceInterleaved’ back to “false” but I still do not see any info in the server log comments regarding UDP setup ports as I recall a while back before installing the forceInterleave feature. I get no video at all from a stream that was publishing (albeit, poorly) with RTP/RTSP and all I changed was interleaved from true to false.

Server Log:

INFO server comment - RTPSessionTracker.remove[rtsp://remotecam.dyndns.org/axis-

media/media.amp?videocodec=h264]: 0:true

WARN server comment - RTPSessionDescriptionDataProviderBasic.getStreamInfo: RTSP

/RTP re-streaming timeout.

INFO server comment - RTPSessionTracker.add[rtsp://remotecam.dyndns.org/axis-med

ia/media.amp?videocodec=h264]: 1

INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.onClose

INFO server comment - RTPSessionTracker.remove[rtsp://remotecam.dyndns.org/axis-

media/media.amp?videocodec=h264]: 0:true

WARN server comment - RTPSessionDescriptionDataProviderBasic.getStreamInfo: RTSP

/RTP re-streaming timeout.

Could you give me a little guidance on what/where I might have changed other parameters that are slipping my mind at the moment as I moved away from UDP to interleaved RTP over the past month?

BTW, I looked into several hardware appliances you mentioned generically to stream via 3G cellular…they all only stream ONE stream…how bout I need to stream dozens live simultaneously? Any suggestions, I am open but for now thats why I am hanging my hat on Wowza…we are 90% there. Just got to get the video pushed through 3G to Wowza successfully. Directly via LAN we are 100%, 3G is not playing nice with Wowza in h.264 mode.

Regards, and as always thanks for the excellent support.

Richard

217

Anyone had any experience with streaming h.264 RTP/RTSP via TCP interleaving for Wowza ingest and traversing a NAT FW/Router?

RTP/RTSP works great with Wowza as long as the source and the Wowza server are on the same LAN. When you specify a stream on the WAN side of the FW/NAT Router for Wowza ingest seems to be significant problem.

This is the FW/NAT Router setup with RTSP (554) open, UDP(6970-9999 not necessary but open), Wowza set to use TCP interleaving:

RTP/RTSP source h.264 --> LAN --> FW/NAT Router --> WAN internet–> FW/NAT Router --> LAN --> Wowza Server

Also remember this is ingest for Wowza not streaming output…output is not problem for NAT, can even use RTMPT if necessary…ingest to Wowza is the issue…

Thanks

Richard

218

I don’t have any experience with this exact setup. I guess I would track the connection along the path to see where the packets are getting blocked. I guess that is where I would start.

Charlie

Been chasing packets all day…Wireshark reports the following which looks correct:

Request: SETUP rtsp://WANip:554/axis-media/media.amp/trackID=1?videocodec=h264&resolution=480x360 RTSP/1.0\r\n

Transport: RTP/AVP/TCP;interleaved=0-1

CSeq: 2\r\n

User-Agent: Wowza Media Server Pro (Wowza Media Server Pro10 1.7.2 build12264)\r\n

then follows the PLAY command from Wowza and RTP packets arrive at the LAN adapter of the Wowza server…

WANip 192.168.0.18 RTP PT=DynamicRTP-Type-96, SSRC=0xED41877D, Seq=41796, Time=485593566

Wowza log reports some packet loss but video starts but is choppy and distorted.

INFO server comment - RTPDePacketizerWrapperPacketSorter.init: rtpDePacketizerPa

cketSorterBufferTime: 500

INFO server comment - RTPDePacketizerWrapperPacketSorter.init: rtpDePacketizerPa

cketSorterFlushTime: 10

INFO server comment - RTPDePacketizerWrapperPacketSorter.init: rtpDePacketizerPa

cketSorterLogPacketLoss: true

INFO stream publish rtsp://WANip:554/axis-media/media.amp?videocodec=h26

4&resolution=480x360 -

INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.sessionSt

art: PLAY: rtsp://WANip:554/axis-media/media.amp?videocodec=h264&resolut

ion=480x360

INFO server comment - RTPMediaCaster.Reconnector: stop

INFO server comment - firstPacket: TCP:$0

WARN server comment - packetLoss[rtsp://WANip:554/axis-media/media.amp/t

rackID=1?videocodec=h264&resolution=480x360]: last:105494 curr:105825

INFO stream play rtsp://WANip:554/axis-media/media.amp?videocodec=h264&r

esolution=480x360 -

WARN server comment - packetLoss[rtsp://WANip:554/axis-media/media.amp/t

rackID=1?videocodec=h264&resolution=480x360]: last:105891 curr:106271

INFO server comment - firstPacket: TCP:$1

INFO server comment - RTCPHandler.sendFirstRTCPRR[3863769306,1,null]

WARN server comment - packetLoss[rtsp://WANip:554/axis-media/media.amp/t

rackID=1?videocodec=h264&resolution=480x360]: last:106294 curr:106720

WARN server comment - packetLoss[rtsp://WANip:554/axis-media/media.amp/t

rackID=1?videocodec=h264&resolution=480x360]: last:106812 curr:107167

WARN server comment - packetLoss[rtsp://WANip:554/axis-media/media.amp/t

rackID=1?videocodec=h264&resolution=480x360]: last:107246 curr:107613

WARN server comment - packetLoss[rtsp://WANip:554/axis-media/media.amp/t

rackID=1?videocodec=h264&resolution=480x360]: last:107692 curr:108049

When I switch to IP source on the LAN with Wowza then get beautiful streaming video and no packet loss and Wireshark reports this

9314 136.992724 192.168.0.21 192.168.0.18 TCP Interleaved channel 0x00, 1400 bytes

RTSP Interleaved Frame, Channel: 0x00, 1400 bytes

Wowza SETUP string is exactly as reported above except for LAN address

I really do not see anything else in the packet stream that is different. I have tried multiple sources on both the WAN side and the LAN side…all LAN side devices stream normally…all WAN side devices have packet loss and poor video…

There are some papers published regarding issues with RTP/RTSP behind NAT routers but no specific answers…anyone heard of this problem either…

Charlie have you ever ingested a stream that a forum user has put up…if so, did it work in your company’s setting or do you guys use a proxy server rather than a NAT FW/Router…just thinking if a RTSP proxy server would help? At a loss at the moment.

Richard

219

I suggest you start over to make a UDP application instead of re-winding from where you got to.

Richard

Set up additional Wowza server on port 2035 with standard setting for UDP and installed StreamNameAlias package, everything else default per your advice above. All UDP streaming checks out normal when the camera is on the same LAN as the server. All streams referenced here come from Axis M1011 IP camera.

When same camera is placed outside the LAN on another network the same setup does not work. If I address the camera directly to its internal viewer via a browser pointed to the WAN address and set it to Unicast RTP (UDP) its streams normally, but it will not connect to Wowza correctly. All firewall ports are open during the tests, both ends in DMZ.

If I tell Wowza to do the same thing, no video, I get this in the log

Configure logging: file:///C:/Program Files/Wowza Media Systems/Wowza Media Serv

er Pro 1.7.2/conf/log4j.properties

INFO server server-start Wowza Media Server Pro10 1.7.2 build12107 -

INFO server comment - Serial number: XXXXX-XXXXX-XXXXX-XXXXX-DN7K9

INFO server comment - Maximum connections: 10

INFO server comment - Hardware Available Processors: 1

INFO server comment - Hardware Physical Memory: 494MB/1279MB

INFO server comment - Hardware Swap Space: 1858MB/2413MB

INFO server comment - Max File Descriptor Count: Unlimited

INFO server comment - OS Name: Windows XP

INFO server comment - OS Version: 5.1

INFO server comment - OS Architecture: x86

INFO server comment - Java Name: Java HotSpot™ Client VM

INFO server comment - Java Vendor: Sun Microsystems Inc.

INFO server comment - Java Version: 1.6.0_15

INFO server comment - Java VM Version: 14.1-b02

INFO server comment - Java Spec Version: 1.6

INFO server comment - Java Home: C:\Program Files\Java\jre6

INFO server comment - Java Max Heap Size: 762MB

INFO server comment - Java Architecture: 32

INFO server comment - CMDInterface now listening: [any]:8083

INFO server comment - vhost home directory: C:\Program Files\Wowza Media Systems

\Wowza Media Server Pro 1.7.2

INFO vhost vhost-start defaultVHost -

INFO vhost comment defaultVHost RTMP/RTMPT bind attempt ([any]:2035)

INFO vhost comment defaultVHost Bind successful ([any]:2035)

INFO server comment - ModuleStreamNameAlias.onAppStart: streamNameAliasFile: C:\

Program Files\Wowza Media Systems\Wowza Media Server Pro 1.7.2\conf\StreamNameAl

iasMap.txt

INFO application app-start definst rtplive/definst

INFO session connect-pending 24.96.210.14 -

INFO session connect 24.96.210.14 -

INFO stream create - -

INFO server comment - ModuleStreamNameAlias.streamNameToAlias: streamName:udp al

ias:{pattern: “udp” alias:"rtsp://74.246.138.96/axis-media/media.amp?videocodec=

h264" wildcardMatches:null} result:rtsp://74.246.138.96/axis-media/media.amp?vid

eocodec=h264

INFO server comment - ModuleStreamNameAlias.play: udp=rtsp://74.246.138.96/axis-

media/media.amp?videocodec=h264

INFO server comment - MediaStreamMediaCasterPlay: startPlay

INFO server comment - RTPMediaCaster.create

INFO server comment - RTPMediaCaster.init

INFO server comment - RTPMediaCaster.Reconnector: start

INFO server comment - RTPSessionTracker.add[rtsp://74.246.138.96/axis-media/medi

a.amp?videocodec=h264]: 1

INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.onClose

INFO server comment - RTPSessionTracker.remove[rtsp://74.246.138.96/axis-media/m

edia.amp?videocodec=h264]: 0:true

WARN server comment - RTPSessionDescriptionDataProviderBasic.getStreamInfo: RTSP

/RTP re-streaming timeout.

INFO server comment - RTPSessionTracker.add[rtsp://74.246.138.96/axis-media/medi

a.amp?videocodec=h264]: 1

INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.onClose

INFO server comment - RTPSessionTracker.remove[rtsp://74.246.138.96/axis-media/m

edia.amp?videocodec=h264]: 0:true

WireShark reports with Wowza UDP request:

DESCRIBE rtsp://74.246.138.96/axis-media/media.amp?videocodec=h264 RTSP/1.0

CSeq: 1

Accept: application/sdp

User-Agent: Wowza Media Server Pro (Wowza Media Server Pro10 1.7.2 build12107)

RTSP/1.0 200 OK

CSeq: 1

Content-Type: application/sdp

Content-Base: rtsp://74.246.138.96/axis-media/media.amp/

Date: Tue, 10 Nov 2009 05:42:55 GMT

Content-Length: 496

v=0

o=- 1257831775630772 1257831775630772 IN IP4 74.246.138.96

s=Media Presentation

e=NONE

c=IN IP4 0.0.0.0

b=AS:50000

t=0 0

a=control:rtsp://74.246.138.96/axis-media/media.amp?videocodec=h264

a=range:npt=0.000000-

m=video 0 RTP/AVP 96

b=AS:50000

a=framerate:20.0

a=control:rtsp://74.246.138.96/axis-media/media.amp/trackID=1?videocodec=h264

a=rtpmap:96 H264/90000

a=fmtp:96 packetization-mode=1; profile-level-id=420029; sprop-parameter-sets=Z0IAKeNQPBf8uAtwEBAaQeJEVA==,aM48gA==

SETUP rtsp://74.246.138.96/axis-media/media.amp/trackID=1?videocodec=h264 RTSP/1.0

Transport: RTP/AVP;unicast;client_port=6970-6971

CSeq: 2

User-Agent: Wowza Media Server Pro (Wowza Media Server Pro10 1.7.2 build12107)

WireShark reports with Axis internal viewer directly to the camera: NOTE THE play COMMAND IS ISSUED

DESCRIBE rtsp://74.246.138.96/axis-media/media.amp?videocodec=h264 RTSP/1.0

CSeq: 67

User-Agent: Axis AMC

Accept: application/sdp

RTSP/1.0 200 OK

CSeq: 67

Content-Type: application/sdp

Content-Base: rtsp://74.246.138.96/axis-media/media.amp/

Date: Tue, 10 Nov 2009 05:48:48 GMT

Content-Length: 496

v=0

o=- 1257832128221781 1257832128221781 IN IP4 74.246.138.96

s=Media Presentation

e=NONE

c=IN IP4 0.0.0.0

b=AS:50000

t=0 0

a=control:rtsp://74.246.138.96/axis-media/media.amp?videocodec=h264

a=range:npt=0.000000-

m=video 0 RTP/AVP 96

b=AS:50000

a=framerate:20.0

a=control:rtsp://74.246.138.96/axis-media/media.amp/trackID=1?videocodec=h264

a=rtpmap:96 H264/90000

a=fmtp:96 packetization-mode=1; profile-level-id=420029; sprop-parameter-sets=Z0IAKeNQPBf8uAtwEBAaQeJEVA==,aM48gA==

SETUP rtsp://74.246.138.96/axis-media/media.amp/trackID=1?videocodec=h264 RTSP/1.0

CSeq: 68

User-Agent: Axis AMC

Transport: RTP/AVP;unicast;client_port=18816-18817

RTSP/1.0 200 OK

CSeq: 68

Session: 020646BF; timeout=60

Transport: RTP/AVP;unicast;client_port=18816-18817;server_port=7174-7175;ssrc=AB434F0D;mode=“PLAY”

Date: Tue, 10 Nov 2009 05:48:48 GMT PLAY rtsp://74.246.138.96/axis-media/media.amp?videocodec=h264 RTSP/1.0

CSeq: 69

User-Agent: Axis AMC

Session: 020646BF

RTSP/1.0 200 OK

CSeq: 69

Session: 020646BF

Range: npt=0.339167-

RTP-Info: url=rtsp://74.246.138.96/axis-media/media.amp/trackID=1?videocodec=h264;seq=49299;rtptime=1328538398

Date: Tue, 10 Nov 2009 05:48:48 GMT

Could you provide any information as to why Wowza does not issue the RTSP PLAY command following the SETUP command that it issues?

The camera is available today on http://74.246.138.96:12345 to reach the Axis internal viewer via browser.

If any possible way you could verify what I am seeing by attaching your Wowza server to rtsp://74.246.138.96/axis-media/media.amp?videocodec=h264 any advice would be greatly appreciated.

Thanks

Richard

220

Try updating to the most recent patch:

https://www.wowza.com/devbuildpro.html

Charlie

Check me that the patch is applied please, I did not check the build number before I installed the patch…

Configure logging: file:///C:/Program Files/Wowza Media Systems/Wowza Media Serv

er Pro 1.7.2/conf/log4j.properties

INFO server server-start Wowza Media Server Pro10 1.7.2 build12295 -

INFO server comment - Serial number: XXXXX-XXXXX-XXXXX-XXXXX-DN7K9

INFO server comment - Maximum connections: 10

INFO server comment - Hardware Available Processors: 1

INFO server comment - Hardware Physical Memory: 482MB/1279MB

INFO server comment - Hardware Swap Space: 1867MB/2413MB

INFO server comment - Max File Descriptor Count: Unlimited

INFO server comment - OS Name: Windows XP

INFO server comment - OS Version: 5.1

INFO server comment - OS Architecture: x86

INFO server comment - Java Name: Java HotSpot™ Client VM

INFO server comment - Java Vendor: Sun Microsystems Inc.

INFO server comment - Java Version: 1.6.0_15

INFO server comment - Java VM Version: 14.1-b02

INFO server comment - Java Spec Version: 1.6

INFO server comment - Java Home: C:\Program Files\Java\jre6

INFO server comment - Java Max Heap Size: 762MB

INFO server comment - Java Architecture: 32

INFO server comment - CMDInterface now listening: [any]:8083

INFO server comment - vhost home directory: C:\Program Files\Wowza Media Systems

\Wowza Media Server Pro 1.7.2

INFO vhost vhost-start defaultVHost -

INFO vhost comment defaultVHost RTMP/RTMPT bind attempt ([any]:2035)

INFO vhost comment defaultVHost Bind successful ([any]:2035)

INFO server comment - ModuleStreamNameAlias.onAppStart: streamNameAliasFile: C:\

Program Files\Wowza Media Systems\Wowza Media Server Pro 1.7.2\conf\StreamNameAl

iasMap.txt

INFO application app-start definst rtplive/definst

INFO session connect-pending 24.96.210.14 -

INFO session connect 24.96.210.14 -

INFO stream create - -

INFO server comment - ModuleStreamNameAlias.streamNameToAlias: streamName:udp al

ias:{pattern: “udp” alias:"rtsp://74.246.138.96/axis-media/media.amp?videocodec=

h264" wildcardMatches:null} result:rtsp://74.246.138.96/axis-media/media.amp?vid

eocodec=h264

INFO server comment - ModuleStreamNameAlias.play: udp=rtsp://74.246.138.96/axis-

media/media.amp?videocodec=h264

INFO server comment - MediaStreamMediaCasterPlay: startPlay

INFO server comment - RTPMediaCaster.create

INFO server comment - RTPMediaCaster.init

INFO server comment - RTPMediaCaster.Reconnector: start

INFO server comment - RTPSessionTracker.add[rtsp://74.246.138.96/axis-media/medi

a.amp?videocodec=h264]: 1

INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.onClose

INFO server comment - RTPSessionTracker.remove[rtsp://74.246.138.96/axis-media/m

edia.amp?videocodec=h264]: 0:true

WARN server comment - RTPSessionDescriptionDataProviderBasic.getStreamInfo: RTSP

/RTP re-streaming timeout.

INFO server comment - RTPSessionTracker.add[rtsp://74.246.138.96/axis-media/medi

a.amp?videocodec=h264]: 1

INFO server comment - RTPSessionDescriptionDataProviderBasicRTSPWorker.onClose

INFO server comment - RTPSessionTracker.remove[rtsp://74.246.138.96/axis-media/m

edia.amp?videocodec=h264]: 0:true

WARN server comment - RTPSessionDescriptionDataProviderBasic.getStreamInfo: RTSP

/RTP re-streaming timeout.

Reaction by the Wowza server was the same though, would not connect correctly…willing to try anything else you reccommend and let me know if it appears patch not properly installed.

Thanks

Richard