Arthur The hardware+drivers we support do NOT include ISDN. and wvdialconf cannot detect ISDN modems. There is abundant literature on ISDN support. Just search Google with "ISDN Linux". MarvS On Mon, Sep 5, 2011 at 5:28 PM, Jacques Goldberg <Jacques.Goldberg@xxxxxxx> wrote: > Dear Arthur, > > Do you have any plan to try to understand what I keep answering to you > instead of repeating the same "information" again and again? > Don't you have a feeling about harassing us? > > Before I answered you for the first time out of many I *did* my work as > professionaly as I can with my limited intellect. > The first thing I did was to look up the so called Rob Clark's tables for > *EXTERNAL* modems located at > http://xmodem.org/modems/extlist.html > which indeed shows an entry: OEM/CIS WS-5614ES2B EXT for a model slighly > older than yours. > To completely identify your modem I then looked up its specifications on the > CIS site: > http://www.modem-help.co.uk/CIS/WS-5614ES3KV-56K-External-Data-Fax-Speakerphone.html > The CIS (manufacturer site) shows no sign that this is an ISDN modem. I do > not know and do not care from where you got that "information" as it is > almost certainly wrong since the manufacturer has no reason to mislead > customers by skipping a feature such that your modem would work only if > connected to an ISDN network if the "information" would be true. > I did tell you and repeat, how many times, that your *modem* (not like your > cable) does not need ANY driver as it is a fully fledged pure hardware > modem. Remember, this was when you were looking for an alternate scanModem > to make your modem work. > I then explained to you that your difficulties are entirely due to the > USB<->serial converter cable which you are trying to use. > Mind you, Arthur, you do not know me, I would not have the guts to discuss > the problems met with this adapter if I had not a long hands on experience > with this device, and at least twice I explained to you that I succeeded, > not trivially, to make it work for what I needed it, data acquisition into a > PC from an FPGA based data acquisition system. > Now you add fresh "information": you purchased your Prolific PL-2303 based > cable from a well known store named Jameco, sold under the name USC-2000 > which is the name of the package using that chip manufactured by QVS (the > package). > This additional blurb thus brings nothing new. Your PL-2303 software simply > does not support all the functionalities available on the 25 pins connector > of your excellent (and old) modem. > > Your problem might be as simple as discovering if the DB-25 terminal pin > handling on the cable side supports or ignores hardware flow control > (usually CTS-DTR but not necessarily this simple implementation only) and if > your modem allows several such protocols and how you make its settings match > the (as far as I know, undocumented) ones in your cable. > It may also be very much more complicated than that. > > So please, dear Arthur, stop harassing us with your informations and > questions which are irrelevant to your problem. > We do not have hardware iDentical to yours, and full technical documentation > of your hardware and software (I mainly mean the cable, and then the modem) > and therefore cannot invent why your setup does not work. > > I now close here my particiapation on this thread. > > Good luck working on your own. > Jacques >
