caller id in m/vgetty

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

(please don't send mgetty mails to me personally.  Send them to the list,
give other people the chance to take some of the load away from me).

Marques Johansson wrote:
> where i am in the world it is now 4:12am.. i have been trying to find an 
> app to convert ps to g3... know of something? 

Ghostscript is nice.  At least the docs say this :-)

> i am going to try to attach my vgetty log (if you dont get it i dont 
> think you will be missing much...) .. i did some fooling around with 
> vgetty + minicom...
> 
> if i send the init string with the #CID in it- the CID does not get 
> activated... it seems to want to be on a seperate line...

Well, then put it on a separate line :-)

> vgetty says it sends the cid=1 then all the fax commands- in minicom i 
> set cid=1 then ran all the fax commands.. cid was still 1...

Good.

> after exiting minicom (mgetty ofcourse reinits upon the removed lock 
> file) if i start minicom back up (with -o so that it does not send any 
> modem commands) i find that cid=0 ??? strange, eh...

Bad. But one would have to look at the log file to see what m/vgetty really
sent to the modem.

> i have the debian distro version of mgetty now.. the guy who compiled it 
> set the "force-init-chat" to \dob\d\d\d++\dATQ0V1H0 OK 

Perfectly fine.

> hmm- now i see something- he has illegal characters in that...the "ob" 
> on my screen is actually weird ascii...

Perfectly fine.  Actually, who put it in there, that was me.

> could that command be causing the cid=1 to go away? does that force-init 
> ever get executed? the log doesnt seem to show it in mdm_sends...

Please read what the documentation says about "force-init-chat", and under
what conditions this is used (NB: you're stealing my time).

> ps. just added the attachment- that was suprisingly painless.. html has 
> come a long way...

Your logfile is pretty painful to me.  Instead of just looking over it
quickly, I have to safe it somewhere, uudecode it, uncompress it, and then
throw away all the unnecessary crap.

If you had just included the *relevant* parts (everything from startup to
an incoming call, for ONE call only), it would have been less data and
much less wasted time.  *sigh*.

> begin 644 vg_modem.log.gz
> M'XL(".7NF34``W9G7VUO9&5M+FQO9P#-G7V3&\>UWO_(?ZQ*53["Q*ZZ*UE+

Grrr... *extracting, finding 2500 lines, looking through it, grumbling*

While the log file is *long*, it's just 2500 lines of pretty useless crap.

What good is it for if you send me 50 modem initializations if there is no
difference between them? [Look pretty fine, btw, except that the log level
is too low].  What good is it for if you send me the logs of about 30
dial-out events, that show no RING whatsoever?

And finall, what good is a log file where the log level is set so low that
the important data is not even there????

Do it again.  Set "vgetty -x6". And then send me the log of ONE call, from 
the startup message ("vgetty: experimental test release...") to the next
such startup message.

Do not compress the log.  Do not encode it.  Do not put into MIME
attachments.

*still fuming*

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-35655025                        gert.doering@physik.tu-muenchen.de