Cisco Systems 5.2.x manual Troubleshoot RTP Over Rtsp, Signature for interleaved RTP

Chapter 5 Cisco Hinter for RTSP

Reference

Click Browse or Choose File (depending on your browser) to find your MPEG2-TS file.

We populate the Output Name field automatically. It is identical to the name in the Source MPEG field except that the filename extension is MOV and not MPG.

Step 4 Click Generate, and then wait for the “Hinting finished successfully” message.

Step 5 Find your hinted MOV output file in the ..\hinted-filessubdirectory.

Step 6 Move or copy both the MPG file and its MOV derivative to the DSS root directory.

Step 7 Stop. You have completed this procedure.

Reference

•FAQs and Troubleshooting, page 5-6

FAQs and Troubleshooting

•Troubleshoot RTP Over RTSP, page 5-6

Troubleshoot RTP Over RTSP

These general troubleshooting ideas might help you to diagnose and resolve problems with this feature.

•Verify that both the MPG source file and its hinted MOV derivative are present together in the media root directory on your DSS.

•Use a utility like openRTSP to test both the MPG source file and its hinted MOV derivative. The correct Linux command line syntax in this case is

openRTSP -V -v -t rtsp://DSS_server_IP_address/filename.mov

•Use HexEdit, WinHex, or a similar utility to open your hinted MOV file and verify that it contains:

–An explicit reference to the full and literal filename of your MPG source.

–The signature for MOV output from Cisco Hinter:

Hinted MPEG1 Muxed Track

–The signature for interleaved RTP:

m=OTHER 0 RTP/AVP 96

•Check the system logs on your DSS.

Note	•	openRTSP — http://www.live555.com/openRTSP/
	•	HexEdit — http://hexedit.sourceforge.net/
	•	WinHex — http://www.winhex.com/winhex/

User Guide for Cisco Digital Media Manager 5.2.x

5-6 OL-15762-03