Re: ttyId (was: mISDNuser patch discussion?)
Christoph Schulz <[email protected]> Mon, 13 Feb 2017 06:27:20 +0100
| Newsgroups | gmane.linux.isdn.i4l.user |
|---|---|
| Message-ID | <20170213062720.Horde.ry2fFhj6f1mVIG7lMkFZoLT@localhost> |
Hello! [email protected] schrieb am So 12 Feb 2017 22:19:15 CET: >> I'm a bit surprised... Surely you refer to the (obviously working)=20=20 >> kernel-space=20i4l implementation of the ISDN ttyI* modems, but not to=20= >> =20 >> the=20(unfinished) user-space ttyId daemon which doesn't work because=20=20 >> big=20parts of the code are commented out. > > You are absolutely right. > Actually I didn't even notice its existence until right now. > So I just assumed you might have had the experience that voice over the > ttyI* didn'd work with the wrong hardware. > Just out of interest: Has that ever been fixed? Well, mISDN just doesn't provide any ttyI* devices as isdn4linux did. So voice applications need to use CAPI (like capisuite or cvm do). If they are not CAPI aware (like vbox), they simply don't work. I don't know whether anyone has ever finished something like ttyId, i.e. an ISDN modem emulator in user space. At least I am not aware of it. And I would be very interested in using it, because it would make the migration from isdn4linux to mISDN smoother. Best regards, Christoph _______________________________________________ isdn4linux mailing list [email protected] https://www.isdn4linux.de/mailman/listinfo/isdn4linux
signature.asc
(application/pgp-signature, 181 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEABECAAYFAlihQ7cACgkQL11jCnyQ5OyB7wCfaxttii3Y23L229gEwUtnsJbY KgoAn0ky9+6ozswZL8c0RGByZhduOU6S =HX3t -----END PGP SIGNATURE-----