I'm using the PVC2300 camera in a 'soft' real-time application which requires a minimum of timing information. The relation of NPT and RTP time stamps in the video data and RTSP packets SHOULD be specified by a RTCP-SR packet (according to RFC3550). But while viewing video from the PVC2300 with a RTSP client, the camera isn't emitting any RTCP-SR packet. I checked this with Wireshark. Are there any options in the camera setup that I missed? Are there any plans by Cisco to fix this issue in a future firmware release?
the realtime problem in my application is that I would like to store the synchronized A/V streams of more than one camera into a single MP4 container. The clocks of the cameras are syncronized by NTP to the clock of the recording PC. The RTP packets only contain RTP time stamps. The relationship of the NTP to the RTP timestamps has to be specified by the cameras in there RTCP sender reports (see RFC3550).
The problem is that the PVC2300 isn't emitting any RTCP packet in my case.
The test setup is quite easy:
Take the PVC2300.
Connect it to a PC.
Start WireShark or any other network monitor on the port to which the camera is connected.
Start watching video with VLC: vlc.exe rtsp://admin:firstname.lastname@example.org/img/media.sav
Watch the output in the network monitor: You will see, that the only RTCP packets are receiver reports issued by the PC. But no sender report from the camera at all.
Cameras of other brands are emitting the sender reports as specified in RFC3550.
Ok I am going to try and run this in our lab here at the Small Business Support Center. One thing you can look at if you have not already..........
Each RTP session is identified by a network address and a pair of ports: one for RTP data and one for RTCP data. The RTP data port should be even, and the RTCP port should be one above the RTP port. For example, if media data is being sent on UDP port 5004, the control channel will be sent to the same address on UDP port 5005. I know that the latest revision of the RTP specification relaxes the requirement that the RTCP port is odd-numbered, and allows nonadjacent RTP and RTCP ports. For compatibility with older implementations, it is still wise to use adjacent ports where possible, with the RTCP data being sent on the higher, odd-numbered, port.
So that said, just double check that the odd number UDP port above the UDP port that RTP is using is not blocked or being hindered in any way maybe check for any blocked ports possibly. WIllupdate after I get a lab going..
Hi every one!!!When you are configuring a remote VPN connection, there
are some steps that are lost on the path. Here you can see those steps.
A) In your Cisco device: 1. Ensure you don´t have any rule denying the
traffic between the device and the remote...
Introduction: This document describes how to connect SG300 with Catalyst
switch via STP. Spanning Tree Protocol (STP) is a Layer 2 protocol that
runs on mainly on switches. The specification for STP is IEEE 802.1D.
The main purpose of STP is to ensure tha...
You have a Cisco Unified Communications Manager (CUCM) system and want
to configure a SPA112 analog telephone adaptor (ATA) to register to the
CUCM so that you can use up to two analog phones or similar FXS devices
with the CUCM.In this application note, ...