Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
I saw a similar question from 1.5 years ago and I am hoping there is something better.
I am looking for a totally managed C# implementation because I need it for the .NET Microframework, so I can't have .NET wrappers around C code.
Has anyone run into a good C# implementation of the SIP protocol. I should not that I don't care about codecs, mostly will be dealing with call control.
My own C# SIP stack is at sipsorcery. It's far from perfect but as far as the RFC3261 core SIP standard goes it should be pretty good and you can hook into that using only SIPSorcery.Core assembly. The server applications can be disregarded if you're looking at doing some specialised call control.
I am using the ozeki voip sip sdk. It is written in c# and it provides a complete SIP implementation with all RFCs. The others I have tried were partial implementations only and didn't work with all my PBXs.
If you wish to be familiar with SIP protocol implementation then I suggest you to first read more useful information about the background of the VoIP technology. I used some examples for my project as well. I have found this explanation earlier:
The Session Initiation Protocol (SIP) is an IETF-defined signaling protocol widely used for controlling communication sessions such as voice and video calls over Internet Protocol. SIP helps in establishing communication sessions which involve various media types such as audio, video, or collaborative multimedia.
I mean, SIP protocol is very important to use when we would like to build an audio or video based application. (For example: Ozeki VoIP SIP SDK is appropriate to create SIP VoIP call services.)
The info derives from this webpage: http://voip-sip-sdk.com/p_304-sip-protocol-implementation-voip.html. I always use this website because this SDK has the best documentation which is plain and transparent to understand it.
This .NET SIP SDK is probably the most comprehensive.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
Right now I'm looking for a way to securely transfer a file between a client and a server in c#. I've looked around a bit and I can't seem to find exactly what I'm looking for. Basically, I'm looking preferably for a library, if not that a technique I can do this. It is worth bearing in mind I have to do both the client and the server for this. The language I'm using is c# so everything will either be on windows or using mono.
About library, you can take a look at WinSCP .NET Assembly.
It's a simple wrapper around WinSCP and you can easily implement a small but fully functional FTP/SFTP client over it.
It seems you need not one, but two things.
A server to act as a storage place for files to be uploaded to and downloaded from
Code to help your code interact with the aforementioned server.
For the server, I'd suggest an FTP server. You can either setup your own or pay a 3rd-party provider to host one for you. So that the FTP server is accessed securely, you'll want to specify FTPS or SFTP protocols for the connections it accepts. Both of these provide encrypted end-to-end communication channels between the client and the server.
Windows Server includes and FTP server. It supports FTPS, but it does not support SFTP. If you want/need to use SFTP, there are 3rd-party FTP servers available for Windows that support it.
Regarding code to access the server, there are numerous .NET libraries available. You can build it from scratch using .NET, or you can buy software components, such as ChilKat or EnterpriseDT. I have had a good experience using both. There are others available, I'm sure.
There is probably no need to reinvent what will turn out to be a pretty expensive wheel.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
My question may be seem too wide, but am kindly requesting for a guide or rather a starting point.
I have a project in which am required to develop a system that will control a Cash Deposit Machine. All activities like getting the amount of notes in the machine and others can easily be done from the system.
During my research, i found out that the machine uses a dll called libglorycolx2010.dll and many other modules, and that i can use Serial Port Communication to communicate with the machine.
Has anyone here ever handled such a project? How can this be implemented.Reference tutorials or links will be of great help.
Edit: I searched for documentation related to that dll and was only able to find phishy looking download sites. Assuming you don't have the documentation, your best bet is to contact the manufacturer and/or distributor of the deposit machine and find out who makes the software, and from them obtain the documentation.
The framework has built-in support for serial port comm. See the documentation and a simple example. Make sure to read up on the documentation of the deposit machine to ensure you're using the right port settings.
SerialPort provide everything you need as a turnkey solution in the .NET Framework. It easily take cares of parameters (Serial Port name, baud rate, and so on), communication, etc. I always use it when doing Serial Communication.
If you need to experiment with SerialPort, install TeraTerm and any software allowing you to virtualize paired serial port on your developing system, so you can experiment quickly and independantly from your target Cash Deposit Machine.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I have already created my server in System.Net.WebSockets and now after transferring it between machines I had noticed Windows Server 2008 is not supported, are there any other implemetations which support an X509Certificate as authentication and would require minimal conversation.
I have been googling for this in the past 2 hours but haven't found anything meaningful, just a collection of poorly written, poorly documented libraries that throw exceptions on the regular, specifically SuperSocket, the server implementation of which seems to be complete buggy bull.
Could anyone post some sample client code from a decent library? I am growing desperate.
Frameworks include:
SignalR
XSockets
Super WebSocket
Alchemy WebSockets
Fleck
More options available via the realtime web tech guide
I know it is a little bit late, but I created a WebSocket C# implementation and it may be interesting for somebody.
There is also:
https://github.com/sta/websocket-sharp - sharp implements RFC6455 and is very popular amongst Unity3d developers
https://github.com/StackExchange/NetGain/ - stackoverflow's implementation of RFC6455
SignalR provides you a great way to add real-time features to your application. Under the hood, it uses either Web Sockets, Server-sent events, Long Polling or Forever Frames based on what the client and the server support. The coming version, scheduled to be released in the coming weeks, will support client-side (X509Certificate) certificates. You can refer to the following links for more details:
http://www.asp.net/signalr
https://github.com/SignalR/SignalR/wiki
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
Is there an API in .NET (C#) for using USB HID (human interface) devices?
HidLibrary wraps up all the P/Invoke calls for you. But no, it doesn't look there are any nice framework APIs for dealing with USB devices.
Here's mine little library for dealing with HID devices.
It might be useful, especially when you are trying to communicate using raw HID reports. I've also included a simple demonstration of how to use it.
There's nothing direct or high-level. There are some things you can do through the managed WMI API, but I've personally found a lot of WMI interaction with hardware to be cryptic at best and requiring a lot of trial-and-error to get it to do what you want.
Someone on The Code Project has developed a .NET component for USB HID you can try out that's probably going to fit the bill better than WMI.
I would suggest you follow this example instead. It was invaluable in getting me up and running with HiD dev in C#.
I suggest you start here: http://wiimotelib.codeplex.com/
Try looking at this: Simple HID Library. The main page has a list of other open source libraries.
Take a look at this library on Google Code:
C# USB HID driver
I was also searching for it. I'm using the code I found here:
http://janaxelson.com/hidpage.htm
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I'm porting old VB6 code that uses the Winsock control to C#. I haven't done any socket programming and I wonder if anyone has a good reference/tutorial/howto that I can use to start getting up to speed.
I'm appealing to the hive mind while I proceed with my generally unproductive googling.
I'm using UDP, not TCP at this time.
The August 2005 MSDN Magazine had an article about System.Net.Sockets and WinSock:
http://msdn.microsoft.com/en-us/magazine/cc300760.aspx
I recommend the asynchronous model for most applications, especially if you want performance or applications that don't hang as soon there is a network problem. For this the MSDN articles on Socket.BeginConnect and Socket.BeginReceive are good places to start.
The following link is not .NET, but many of the recommendations still hold: http://tangentsoft.net/wskfaq/articles/lame-list.html
MSDN is a good place to start
Are you working on:
a client (TCPClient)
or a server (TCPListener)
Just a heads up:
I would recommend first working with TCP rather than UDP. UDP doesn't automatically redeliver lost packets like TCP so it will add another element to the equation that will probably just confuse you as you're just starting out.
Building a socket client is relatively easy using the TCPClient class available in the .Net library. TCPListener is easy enough to use for a single client but if you're hoping to develop some server type application (IE: Handling multiple connections.) the real hurdle you'll have to overcome is understanding multithreading.
Once you've played around with single connection sockets I suggest you read up on multithreading.