Maybe I'm not familiar enough with the internals of Asterisk to understand what kind of timing you're after. I assumed you were just after a reference clock.
On Oct 12, 2004, at 10:12 AM, Christopher L. Wade wrote:
Darren Sessions wrote:Why not use an NTP timing source - go stratum 2 or 3. That should be plenty for a stable clock source.
*Timing* is what is needed, not _time_. Two different things. Besides the obvious problems with using a remote network resource as a timing device, I don't think many NTP server admins would enjoy you requesting a _time_ update on the order of 1000+ times a second? RTP not relying on incoming RTP stream is going to require ?hardware? on the machine. My $0.02.
-- Christopher L. Wade Unistar-Sparco Computers, Inc. Senior Systems Administrator dba Sparco.com Email: [EMAIL PROTECTED] 7089 Ryburn Drive Phone: (901) 872 2272 / (800) 840 8400 Millington, TN 38053 Fax: (901) 872 8482 USA
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
