search

ladendirekt / pjsip4net

A wrapper library exposing the pjsip library to the .NET world in a OO-friendly way.
71 stars 42 forks source link

Active development #2

Closed percramer closed 9 years ago

percramer commented 11 years ago

Hi,

is this being developed actively? I am starting a project using an embedded linux device and mono / c#. I looked at Sipek, but that doesn't seem to be under active developement.

The conference part and the media/conference bridge are importent for my project.

I am willing to help with psip4.net!

Regards,

Per

siniypin commented 11 years ago

Hi. I have currently brought this project to a halt. Nevertheless there are two major things waiting to be developed:

I'd suggest you to start with forking a repo and making a Mono build running. I use Rob Reynolds' UpperCut for running builds, yet a rather outdated version. As it appears from Release notes it supports Mono builds from version 1.0.5.0. If you run a build on windows you will get a Moma output report as part of build artifacts. You can use it as a starting point for development of Mono build. After you done, send me a pull request!

Any of your help will be much appretiated.

RobertT.

percramer commented 11 years ago

Hi Robert,

thank you for your quick answer. Did you do any actual mono testing already? To see what the issues might be in combination with mono?

regards,

Per

percramer commented 11 years ago

Hi Robert,

i did a quick mono scan and it showed only 1 issue. See the attached image.

mono test

Regards,

Per

siniypin commented 11 years ago

Please, checkout if pjsip4net.Interop assembly is included in this scan as well. I remeber having issues with that.

RobertT

percramer commented 11 years ago

aah yes, i see now. It gives met 81 pInvoke errors :-( I will search where they happen and see if there is a solution possible without pInvoke.

Per

siniypin commented 11 years ago

You can try to generate PInvoke code with SWIG. I've used PInvoke interop assistant

RobertT

percramer commented 11 years ago

Ok i will try that. But there shouldn't be any pinvoke usage for mono compatibility

Regards,

Per

siniypin commented 11 years ago

Alright. Please notice that the pjsip4net assembly itself has no dendencies on pjsip.Interop and vice versa. The least common denominator is pjsip4net.Core that keeps declarations of so called API providers, that are nothing more then wrappers on top of raw interop code. I've chosen this design in order to be able to swap pjsip.dll with newer (or older, who knows) versions without recompiling the application code. All you have to do is to craft your version of pjsip.Interop assembly compatible with Mono.

RobertT

siniypin commented 9 years ago

As I have no feedback, I'll close this one too.