The log file under microsoft may have a similar CID call which you can interpret MarvS On 9/7/07, C M Ackerman <c.m.ackerman@xxxxxxxxx> wrote: > > But why does the log file shows CID stuff? Look at this excerpt from > the logfile below: > > >> <177.541382> slusb0: modem_ring... > >> <177.541455> slusb0: modem_cid_start: timeout = 400... > >> <177.541470> cid: create... > >> <177.541488> FSK CID Creating > >> <177.541500> FSK CID Reset ! > >> <177.541516> FSK CID Setting Fs = 8000 Threshold = 2 ! > >> <177.541531> slusb0: modem set hook: 0 --> 2... > > and the slmodemd source code is peppered with > #ifdef MODEM_CONFIG_CID > > It seems so close, I can almost taste it. > > -Chaim > > ----- Original Message ----- > From: "Marvin Stodolsky" <marvin.stodolsky@xxxxxxxxx> > To: "C M Ackerman" <c.m.ackerman@xxxxxxxxx> > Cc: <DISCUSS@xxxxxxxxxxxxx> > Sent: Thursday, September 06, 2007 11:59 PM > Subject: Re: Chaim, No CID, USA, Debian GNU/Linux 4.0, kernel 2.6.18-5-486 > > > > Chaim, > > > > Caller ID was never implemented under Linux in the Smartlink software. > > Such accessory functionality would be in the pre-compiled compenents > > that we have no effective access too. > > > > MarvS > > scanModem maintainer > > > > On 9/6/07, C M Ackerman <c.m.ackerman@xxxxxxxxx> wrote: > >> Hi LinModemers, > >> > >> The Problem: The modem works, but it's not reporting Caller ID on Linux > >> (using /dev/slusb0). > >> Some Background: It reports Caller ID using HyperTerm under Windows XP > >> with > >> the exact same configuration. > >> Therefore the modem h/w must support it and the telco line is working > >> correctly. > >> > >> I tried switching to alsa, and I can communicate with the modem, but it > >> doesn't even report RING, > >> so I figured on staying with slusb > >> > >> ati7 reports back the following on both Linux and Windows: > >> Country: USA > >> I added more detailed info below. > >> > >> Hope somebody can help... > >> Chaim > >> > >> ========== Windows HyperTerm Log ==================== > >> at > >> OK > >> at#cid=1 > >> OK > >> > >> RING > >> > >> DATE = 0831 > >> TIME = 1223 > >> NMBR = 7325551212 > >> NAME = HOWELL NJ > >> > >> RING > >> > >> RING > >> > >> ========= Here's info on my Linux installed packages > >> ========================== > >> > >> $ dpkg -l | grep modem > >> ii sl-modem-daemon 2.9.9d+e-pre2-10 > >> SmartLink software modem daemon > >> ii sl-modem-modules-2.6.18-5-486 > >> 2.9.9d+e-pre2-10+2.6.18.dfsg.1-13etch1 > >> Smart Link modem modules for Linux (kernel 2 > >> ii sl-modem-source 2.9.9d+e-pre2-10 > >> SmartLink software modem driver - module bui > >> > >> > >> ========= Here's the results of starting it up with slmodemd -d5 -c USA > >> /dev/slusb0 ============================== > >> SmartLink Soft Modem: version 2.9.11 Sep 3 2007 03:40:16 > >> > >> > >> picocom /dev/ttySL0 > >> picocom v1.4 > >> > >> port is : /dev/ttySL0 > >> flowcontrol : none > >> baudrate is : 9600 > >> parity is : none > >> databits are : 8 > >> escape is : C-a > >> noinit is : no > >> noreset is : no > >> nolock is : no > >> send_cmd is : ascii_xfr -s -v -l10 > >> receive_cmd is : rz -vv > >> > >> Terminal ready > >> <153.505740> main: termios changed. > >> <153.505775> slusb0: update termios... > >> at > >> <157.225516> slusb0: run cmd: at > >> <157.225553> slusb0: modem report result: 0 (OK) > >> OK > >> at#cid=1 > >> <163.222422> slusb0: run cmd: at#cid=1 > >> <163.222461> slusb0: modem report result: 0 (OK) > >> OK > >> <177.541382> slusb0: modem_ring... > >> <177.541455> slusb0: modem_cid_start: timeout = 400... > >> <177.541470> cid: create... > >> <177.541488> FSK CID Creating > >> <177.541500> FSK CID Reset ! > >> <177.541516> FSK CID Setting Fs = 8000 Threshold = 2 ! > >> <177.541531> slusb0: modem set hook: 0 --> 2... > >> <177.541545> main: modemap_ioctl: cmd 2, arg 2... > >> <177.541561> main: modemap_ioctl: cmd 4, arg 2580... > >> <177.541575> main: modemap_ioctl: cmd 7, arg 30... > >> <177.541589> main: modemap_start... > >> <180.056416> slusb0: modem_event: 1... > >> <180.056465> slusb0: ring valid. > >> <180.056484> slusb0: modem report result: 2 (RING) > >> RING > >> <181.060570> Tone 1200 Detected > >> <181.560455> slusb0: modem_cid_stop... > >> <181.560502> slusb0: modem_stop.. > >> <181.560514> main: modemap_stop... > >> <181.564380> slusb0: modem set hook: 0 --> 0... > >> <181.564456> main: modemap_ioctl: cmd 8, arg 0... > >> <181.564481> cid: delete... > >> <181.564505> slusb0: modem set state: 1 --> 1... > >> <183.539900> slusb0: modem_ring... > >> <186.052373> slusb0: modem_event: 1... > >> <186.052425> slusb0: ring valid. > >> <186.052437> slusb0: modem report result: 2 (RING) > >> RING > >> <189.539541> slusb0: modem_ring... > >> <192.052355> slusb0: modem_event: 1... > >> <192.052406> slusb0: ring valid. > >> <192.052417> slusb0: modem report result: 2 (RING) > >> RING > >> <198.564348> slusb0: modem_event: 1... > >> <198.564395> slusb0: ring cancel... > >> > >> > >
