CAPI 2.0 Proxy (Remote CAPI port) / News: Recent posts

as a result of having spent the whole last friday reading info pages our project now has automake and autoconf which makes it look REALLY professional ;)
now you can build it as usual with "./configure; make all install"
there's also a small spec file that could help you building an rpm if you want

Yesterday I started debugging the linux client module... open/close on the device node works at least...

Hi guys, in order to find bugs and add new features we need your feedback.
What do you like, what is missing, what does not work at all? We'll do our best to satisfy you :-)

Some minor changes to the .dll itself have been made (e.g. now supporting a "port" registry entry)

A control panel applet has been added to make configuration easier

Fritzle has written a new version of the Linux server.
I didn't test it but I trust him ;-)
Changes:
- The program has been split up into many source files.
- An init-script has been added. The script was made for
Debian 3.0 but it should work with any other distro, too.
- PThread code was removed completely.
- Command-Line arguments were added. I also tried out some
code on config-files but it proofed to be not stable
enough to go into mainstream capifwd.
- A problem with zombies beeing created by handlers was
removed by adding a SIGCHLD handler.
- New "chackdep.sh"-script that checks for libcapi.
- The Code was cleaned up everywhere.

For amny people had major problems copying a file into the system folder :-)) and adding some registry values I released the 0.6.3 win32 client with an installer!

Hi,
Gerald now started writing the Linux client module for good. The stuff I (Adam) wrote was not working yet (I didn't even try to compile it for I knew what would happen :-) ).
So maybe in a few days/weeks you'll be able to test some pre-alpha.
It will supply an interface for accessing the kernelcapi at device driver level.
Then still a deamon has to be written that does the networking stuff and forwards the resulting data to the module.

Sorry, the last version released had a bug and hung on reiving the first message, because all incoming messages were deleted immediately...
It should work better now

I just released new versions of the linux server and the win32 client.
the timeout feature has been disabled now, because it just caused a lot of errors. maybe it'll work better now, please test it.
the linux server has now a kind of auto-app-release, when the connection to the client breaks, like the win32 server.
I would really be happy if you post some bugs, comments etc to the trackers.
have fun

Please only use the latest 0.6.x version, for all other ones have more bugs.
And you can't use the 0.5 client/server with the 0.6.x client/server! they use a completely different network protocol.

I know there are plenty of bugs in the Win32 Server/Client and even more in the Linux Server!! So pleeeez send me some feedback or stuff.
Were you able to install it? Did it work? Why didn't it work? Ok, this one's my job :-)

The linux daemon for the CAPI 2.0 Proxy has been released.
For compiling it you need at least the libcapi20 and libpthread installed. I wrote a small makefile to make it easier to compile.
To shutdown the server try "killall capi20server".
I tested it with the Win32 cleint and it seemed to work.
Important: It is not enough to have just ISDN4Linux installed and configured. You need to load the CAPI driver for your card instead of the normal ISDN driver!!! To use the ISDN devices again you'll have to load additionally the "capidrv" module and add some aliases to you modules.conf.

A new release of the CAPI 2.0 Proxy Win32 client is available.
It should run on Windows 95 (Winsock2), 98, ME, 2000, NT4, XP. But I only tested it on Win32.
New features:
and tray mode
- better performance and stability
- timeout for receiving messages from server, so the .dll will only hang for 20 seconds or so :-) and then will report an CAPI error to the app. It's up to the app to handle that error...

A new release of the CAPI 2.0 Proxy Win32 server is available.
It should run on Windows 95 (Winsock2), 98, ME, 2000, NT4, XP. But I only tested it on Win32.
New features:
- better support for Win9x (you can minimize the server to a tray icon so you don't have to see the console)
- some improvements in the NT-service mode
- debug mode available in service and tray mode
- better performance and stability

I posted a new verison of the Win32 server & client to our CVS.
There are still a few problems with it, but most features already work. Perhaps we'll make a release soon.

We're also trying to write a linux client. It will be implemented as kernel module with a daemon that handles the communication with the capi20proxy server.
The generic interface of the module will allow to write daemons perhaps for other LAN-CAPI protocols.

We are developing now a new protocol for the network. With this new protocol we will be able to offer authorization, encryption and much more security.

I have posted a new linux server version in CVS, but it is not yet in any way functional. please do not use it yet except if you want to help to develop it. cheers...

OK,
I really need someone who knows a liite bit about writing modules in linux.
I'm planning to write a client for LINUX!!!!!
I think it's possible
(we could take a look at the fcpci driver or stuff)

Hi guys,
I would really be happy if you sent me a little bit feedback whether the stuff i wrote really works.
No feedback - no improvement

Hi guys,
I would really be happy if you sent me a little bit feedback whether the stuff i wrote really works.
No feedback - no improvement