Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

VSOM failing over WAN

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.



New Member

Re: VSOM failing over WAN

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.


Re: VSOM failing over WAN

Have you confirmed that the VSOM workstation you are attempting to view with meets the minimum requirements to actually render a stream?

Can the workstation reach not only the VSOM server, but also the actual media server (VSMS) on which the feed is defined?

Both of these conditions are required.



Scott Olsen Solutions Specialist Bulletproof Solutions Inc. Web:
Cisco Employee

Re: VSOM failing over WAN

Hey Patrick,

Could you just run through the following:

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.