Re: [hylafax-users] Parsing 'raw' caller-id strings

[Ron Isaacson <isaacson@xxxxxxxxx>]

Lee Howard wrote:
> 
> Ron Isaacson wrote:
> > I'm just getting started with HylaFax. My modem is an old US Robotics
> > (external) from 1998. ATI3 says 'U.S. Robotics 56K FAX EXT V4.9.1'.
> >
> > When I turn on caller id with AT#CID=2, I get what looks like the raw 
> > CND message. After turning tracing on:
> >
> >   FaxGetty[26886]: STATE CHANGE: RUNNING -> LISTENING
> >   FaxGetty[26886]: --> [4:RING]
> >   FaxGetty[26886]: --> [30:<80>'^A^H08142203^G^ODOE,J          ^B]
> >   FaxGetty[26886]: --> [11:2125551212O]
> >
> > Looking at the docs, I can't seem to figure out how to construct a 
> > CallIDPattern to match this. Any hints?
> 
> Why not use AT#CID=1 instead?

Yes, of course that's easier to parse. I thought I wasn't getting the
name coming through with #CID=1, but it must have been the number I
was calling from, as I tried from a different number and the name was
reported just fine. Thanks!

--
Ron Isaacson
isaacson@xxxxxxxxx


____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*