Streaming video from vsom using bwims://

[sparklemotion]

I am trying to use vlc to view video of the VSOM,  in Cisco's Urban Security Design Guide (link at bottom),  it describes how you can connect to feeds in windows  media player using  a bwims:// format.   I have searched high and low on the interwebs and cant find what this means.  I am able to get the video feeds from vsom --> Windows Media Player, but am unable to get them into VLC where it is of real value.  Can anyone shed some light on what Bwims is?

http://www.cisco.com/en/US/docs/solutions/Verticals/Government/Urban_Security_DG/CH_5_Urb_Sec.html

[jfiranzi]

Rather than answer the bwims:// part of this question, let me instead direct you to a method of viewing video via vlc, as it sounds as if that is your ultimate objective.  Taken from a couple of tech tips:

Using VLC media player to view a standard definition IP Camera video stream

Step 1.

Open VLC media player.

Step 2.

Click the File menu and click Open File.

Step 3.

Click the Network tab and select RTSP as the protocol.

Step 4.

In the URL field, type the name location of the streaming video.

This example streams both video and audio from the same source:

rtsp://[IP ADDRESS]/img/media.sav.

This example streams video only:

rtsp://[IP ADDRESS]/img/video.sav.

All contents are Copyright © 1992–2008 Cisco Systems, Inc. All rights reserved. Page 1 of 2 Updated September 15, 2008 by Philip Schrupp

Step 5.

Click OK. Video appears in the VLC media player.

You may be prompted for the username and password.

It's a little different to view HD camera feeds...

High Definition (HD) IP Camera

As with the SD IP camera example, VLC Media Player can also be used to view the video streams from Channel 1

and Channel 2 from the HD IP camera. Accessing the Video Stream on the HD IP camera requires gathering additional

information from the HD IP Camera. You must access the HD IP Camera via HTTP to gather the following

parameters: sessionID, ChannelName for Both Channels.

• Navigate to the Streaming Settings on the Camera web page and get the sessionID parameter from the “URL”

ie. HTTP to HD IP Camera

http://10.1.1.1/home.cs?version=1.0&sessionID=12345678&action=get

• Confirm & Record the Channel Name (s). For Example, "Channel1" or “Channel2”.

URL Location: rtsp://< HD CAMERA IP ADDRESS >/StreamingSetting

StreamingSetting = ?version=1.0&action=getRTSPStream&sessionID=< SESSION-ID >&ChannelID=< 1 or 2

>&ChannelName=< Channe1 or 2>

ie.

rtsp://10.1.1.1/StreamingSetting?version=1.0&action=getRTSPStream&sessionID=12345678&ChannelID=1&ChannelName=

Channel1

In the example above,

10.1.1.1 is the HD Camera IP Address.
‣ 12345678 is the sessionID from the URL. This will be different for each new session.
‣ Channel ID is “1” and ChannelName is “Channel1”

Follow the SAME steps for VLC that are listed in the SD IP Camera section above. The ONLY change is the “Media
Resource Locator (MRL)” address. Just use the HD IP Camera URL format shown above.

I hope that helps...

[sparklemotion]

thanks for the help

I want to connect to VSOM streams rather then go diretly from the camera, that way its a one stop shop and wont change depending on the model of the camera.  Also I want to get a uniform output rather then MJpeg sometimes and H.264  or MP4 other times.   I assume bwims is a proprietary wrapper developed by broadware before it was bought by cisco.  As it turns out I just needed to connect to the VSMS instead of the actual VSOM  to get the feed I wanted.    I used  http://[ipaddress]/info.bwt?type=proxy&display=html to get a list of all the proxys and then view the rtsp stream using rtsp://[ipaddress]:554/live/[proxyname] using the proxy name of the feed I needed.   The only real question now is if I can get VSMS to give the video stream to me in a different format. I would prefer H264 so i can natively consume it in a application rather then having to transcode it.  Any idea if i can send a flag in the URL to give me H264?  I have succesfully converted the video using FFMPEG but dont want to have that added dependancy for this.

[jimather · Accepted solution]

Hi,

A vsms proxy entity is tied to a particular encoding method. As such, when you're requesting live viewing using RTSP in VLC, your request is proxy-specific, hence the video is streamed to VLC using the proxy-specific encoding method. Here is an example of an MPEG-4 proxy:

RTP-MSP-1RU-2:~ # more /usr/BWhttpd/conf/proxy/10.p_jpeg_test.xml

  p_jpeg_test
  proxy
  cisco_avg
 
  0
  3
  80
  14.2.11.2
  0
  0
 
  admin
  cisco123
jpeg
  1.000000
  640
  50
  704
  480
  ntsc
  4cif
  1.000000
  8000

Here is an example of an MPEG-4 proxy:

RTP-MSP-1RU-2:~ # more /usr/BWhttpd/conf/proxy/10.p_s1_CIVS-IPC-2500-1_1.xml

  p_s1_CIVS-IPC-2500-1_1
  proxy
  cisco-2500
 
  0
  1_1
  80
  14.2.10.53
  1
  0
 
  admin
  cisco123!
  mpeg4-v
  5.000000
  640
  20
  720
  480
  ntsc
  d1
  5.000000
  8000

Given this information, there isn't a method (I'm aware of) to request a non-proxy-native encoding scheme in an RTSP request for a given proxy's live viewing.

Does this help?

[jfiranzi]

Jim M's answer is correct.   The way VSM works, the VSOM server is used to configure a proxy (camera feed) and an archive definition (an .xml file) on the VSMS server.  The video codec, resolution, bitrate (or in the case of MJPEG, framerate) are configured in VSOM, and that configuration is pushed to the camera.  The camera then streams this primary feed to the VSMS server where it is recorded (assuming an archive has been defined.)

You can view the feed via the method you discovered, but you cannot change the configuration of the feed except through VSOM (or directly through the camera web interface or encoder, depending on the type of camera.)

Your post sounds as if you want to be able to retrieve H.264 video streams via http commands.  The only way this will work is to configure your proxies to stream H.264 as your primary or secondary feed.  The VSMS server does not have the ability to transcode video (except when creating a .WMV clip through VSOM, but that's a different case.)  You will only ever be able to view feeds via http as they are encoded by either an IP camera or an encoder in the case of analog cameras.

Some cameras can natively encode in H.264 while others can only encode MPEG4 and MJPEG.  You would need to review the documentation on the specific camera models you have deployed to see if primary (or even secondary) feeds can be set to use H.264 for your purpose.

I hope that helps...

[sparklemotion]

You guys are awesome. You have any good resources for all this stuff? pdfs, or websites?

[jfiranzi]

One exceptional resource is the Emerging Technologies Partner Resource Center, though access is restricted to Emerging Technology focus partners.

http://www.ciscoet.com

If your company qualifies, you may request access via the pushtile labeled Request Access located on the home page.  If you are looking for white paper level details, I'm afraid that information is not publicly posted.  Your best bet is to ask via these forums or contact a Cisco Advanced Technology Partner specializing in Video Surveillance.

The other option if you are a partner or if your Cisco Account Team (SE usually) is willing to open a case is to request information via the PDI Help Desk for Physical Security (a new resource for this technology.)