Do you have a question? Post it now! No Registration Necessary. Now with pictures!
- Mike Carr
August 22, 2004, 3:24 am
rate this thread
I'm currently working on a module to parse raw caller id information as
reported by my (relatively generic) USR data modem when running in
AT#CID=2 mode (raw caller id mode). The modem spits out things like
"MESG = 802801..." where ... means many more characters (50-100
characters depending on whether it's a local call, private or long
Writing code to do this is silly because the modem will report all the
information in a pretty format when running in AT#CID=1 mode (pretty
caller id mode). But, hey, why not? Maybe it will scratch somebodies
itch out there.
I'm using the code within another application to provide caller id
services (meaning, notification real-time of incoming calls with
callerid info through instant messaging, email. user-controlled web
reporting has also been completed). I'm not sure if I'm going to release
my app with the module or not.
I've noted that Cosimo is releasing a callerid script with Device::Modem
v1.39 but I haven't had a chance to check if he's doing formatted CID
mode or raw CID mode. My Callerid module will be strictly concerned with
parsing/interpreting the hex string, no more no less. I'll leave the
heavy lifting to Device::Modem, thanks ;)
If there's anyone out there that's interested in raw callerid, please
feel free to contact me at email@example.com . I'd
particularly like feedback on whether other modems return similarly
formatted strings. Or indeed, whether this is a foolish task in the end. ;)
Re: Callerid processing
> I've noted that Cosimo is releasing a callerid script with Device::Modem
> v1.39 but I haven't had a chance to check if he's doing formatted CID
> mode or raw CID mode.
The `caller-id.pl' script that is included in Device::Modem 1.39
prints out the exact string that is coming out of the modem
(I also use a US Robotics modem), without any formatting.
BTW, I didn't know of AT#CID=2, thanks.