SharpRTSP | A RTSP handling library | Video Utils library

by ngraziano C# Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | SharpRTSP Summary

SharpRTSP is a C# library typically used in Video, Video Utils applications. SharpRTSP has no bugs, it has no vulnerabilities and it has low support. However SharpRTSP has a Non-SPDX License. You can download it from GitHub.

[Coverage Status] A C# library to build RTSP Clients, RTSP Servers and handle RTP data streams. The library has several examples. * RTSP Client Example - will connect to a RTSP server and receive Video and Audio in H264, H265/HEVC, G711, AAC and AMR formats. UDP, TCP and Multicast are supported. The data received is written to files. * RTSP Camera Server Example - A YUV Image Generator and a very simple H264 Encoder generate H264 NALs which are then delivered via a RTSP Server to clients * RTP Receiver - will recieve RTP and RTCP packets and pass them to a transport handler * RTSP Server - will accept RTSP connections and talk to clients * RTP Sender - will send RTP packets to clients * Transport Handler - Transport hanlders for H264, H265/HEVC, G711 and AMR are provided.

Support

Quality

Security

License

Reuse

Support

SharpRTSP has a low active ecosystem.

It has 327 star(s) with 141 fork(s). There are 42 watchers for this library.

It had no major release in the last 6 months.

There are 17 open issues and 36 have been closed. On average issues are closed in 145 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of SharpRTSP is current.

Quality

SharpRTSP has 0 bugs and 0 code smells.

Security

SharpRTSP has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

SharpRTSP code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

SharpRTSP has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

SharpRTSP releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

SharpRTSP saves you 1417 person hours of effort in developing the same functionality from scratch.

It has 3168 lines of code, 0 functions and 82 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of SharpRTSP

Get all kandi verified functions for this library.

SharpRTSP Key Features

No Key Features are available at this moment for SharpRTSP.

SharpRTSP Examples and Code Snippets

No Code Snippets are available at this moment for SharpRTSP.

Community Discussions

Trending Discussions on SharpRTSP

Wireshark show a yellow row on the parameter line of SDP

QUESTION

Wireshark show a yellow row on the parameter line of SDP

Asked 2017-Feb-02 at 16:15

The context : I'm building an RTSP / RTP server in C#, i saw that there was two main libs that can help me, the first is Managed Media Aggregation. The second is SharpRTSP. I use the first for the packetization of data for RTP and the second to handle the RTSP side with the SDP.

I analyzed packet with wireshark because when i try to access the video content of my server, it success to connect but i have no data incoming, so i look to everything that can be the cause. The analisys show me that the following line in the SDP (on the describe answer of the server) is marked with yellow.

...

ANSWER

Answered 2017-Feb-02 at 16:15

If you expand the packet details, you should see an "Expert Info" indication as to why Wireshark categorized the packet as a warning. You can also open the "Expert Infos" dialog via Analyze -> Expert Info or by clicking on the small circle in the lower left hand side of the status bar. That dialog will show you all the "Expert Infos" for all packets, grouped by severity.

Further, you can even apply a display filter for expert infos. The syntax differs depending on what version of Wireshark you're using, but it's one of these two:

Wireshark's SDP dissector adds several "Expert Info" entries; you can always browse the packet-sdp.c source code to try to find out more information as to why Wireshark might have added a particular one. The expert info details begin down around line 3153 and the only entry that is categorized as PI_WARN is for an "Invalid conversion", the logic which determines this being up around lines 1338-1370. So is that the "Expert Info" you're seeing? If so, then there would appear to be something wrong with the profile-level-id, but without a packet capture to look at, I wouldn't be able to tell you exactly what that is.

It's also possible there was a Wireshark bug with the conversion? You haven't stated which version of Wireshark you're running, but you could try to update to the latest available version of Wireshark to see if the warning goes away. If it doesn't and you're confident that the packet is correctly formatted, you could open a Wireshark bug report and supply a capture file for the developers to use for testing.

Source https://stackoverflow.com/questions/41997286

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install SharpRTSP

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: