*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.
What about using the timing stuff in zap? could this be done?
_______________________________________________ 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
