I have a new installation with 4.1/6.2. Everything works great locally. I created a child feed for one camera that only displays 1 fps and only consumes about 290kbps so viewing it over the WAN would not be an issue. Works great locally, however accessing VSOM over the WAN the camera view comes up "connection failed". Tried this from difference sites and same issue. All sites have T1's.
I think you have misconfigured the camera. You need to first configure dual stream on the camera. Make sure that you use the correct CODEC because some cameras only support MPEG4@4CIF for the primary stream and MJPEG@CIF for the secondary stream.
Confirm this topology - VSMS and VSOM locally on site, 1 x camera running 1fps@290k/s. Remote sites have dedicated bandwidth at over 1mb/s, where you're running a client (VSOM webpage with ActiveX?)
- From the client (WAN) site, can you ping the VSMS server?
- Make note of any firewalls or NAT devices in-between the client and VSMS server. Take a packet capture at either end at the same time and compare them to see what's going on (one capture at the client, one at the VSMS)
With the packet capture you can see if the request from the client is reaching the VSMS and if the RTP stream is coming back. If a device along the way is eating these packets and discarding them, you'll have a good indication here.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...