Heiko, The phone string is copied verbatim to the modem as per Hayes command set. You can test by sending the same string to the modem using a terminal program. You can also test using the NTP filegen facility and flag 4 set on the fudge command. The modem protocol and command responses are written to the clockstats file.
Dave Heiko Gerstung wrote: > Dave, > > thank you for your fast reply. I tried exactly that configuration, but > used the PTB phone number (which works in a test with cu, as described). > > When I first did not include the atdt string, ntpd said "no answer" in > the syslog. When I include the "atdt" I can see no modem activity at all > and I get zero log entries (reach stays at 0). > > I will try again tomorrow morning when I am back in the office and keep > you posted. > > Cheers, > Heiko > > > [EMAIL PROTECTED] schrieb: > >> Heiko, >> >> server 127.127.18.1 minpoll 12 maxpoll 17 >> phone atdt913034944774 atdt917195676742 >> >> The driver first tries NIST Boulder and if that fails USNO Boulder. >> Note from my office it first dials 9 for an outside line, then 1 for >> long distance. >> >> Dave >> >> Heiko Gerstung wrote: >> >>> Hi! >>> >>> I am currently trying to setup a box which uses the ACTS refclock >>> driver to use the PTB modem service as a time source. >>> >>> Unfortunately the documentation regarding this driver is not that >>> detailed and I am therefore looking out for any working example >>> configurations of such a driver. >>> >>> Every time I restart ntpd, it tries to dial out but fails and says >>> "no answer", but when I use cu with the very same phone number, it >>> works flawlessy. >>> >>> Any hints? >>> >>> Regards, >>> Heiko _______________________________________________ questions mailing list [email protected] https://lists.ntp.isc.org/mailman/listinfo/questions
