On Tuesday 20 November 2001 02:19, Pong wrote:
> 2) your modem supports the AT#CID=1 (does that mean that the
> modem has that caller-id chip?)
i saw some websites that indicated that what you could do for some US
Robotics models was upgrade the firmware to understand CID.
> i tried typing AT#CID=1 on a USR Courier V.Everything modem with
> flash software dating back to 1996 and it responded with OK. the
> next thing i need to do is use similar software above and test it
> with a caller-id enabled line to see if it can capture the info from
> the modem.
i saw a website (lost URL, sorry) that indicated that different modems
report the CID in different ways. in this case, i think he said that
the particular model of US Robotics he was working with reported it in
the same line as the line speed/protocols, etc. it was just an extra
field delimited with forward slash. so you could get radius to store
that information, but you'd have to hack the RADIUS code (or get some
radius that had support for that feature). since there's more than one
way (apparently) to receive the CID, i'd just edit the RADIUS code to
store the CID in the Calling-Station-ID attribute pair, or wherever.
i was going to go ahead and do that here, but the guy configuring the
dialup server gave up on linux/cyclom-y/portslave and installed W2K
advanced server instead. if i can get him to go with linux then i may
get around to trying that yet. (i have influence here, but i don't
make the final decision on linux since it's his department, his box,
oh well).
tiger
--
Gerald Timothy Quimpo [EMAIL PROTECTED] [EMAIL PROTECTED]
Entia non sunt multiplicanda praetere necessitatem
Mene sakhet ur seveh
_
Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph
To leave: send "unsubscribe" in the body to [EMAIL PROTECTED]
To subscribe to the Linux Newbies' List: send "subscribe" in the body to
[EMAIL PROTECTED]
