Well I cat /proc/drivers/rtc and get
rtc_time : 15:48:35
rtc_date : 2007-11-02
rtc_epoch : 1900
alarm : 16:30:31
DST_enable : no
BCD : yes
24hr : yes
square_wave : no
alarm_IRQ : no
update_IRQ : no
periodic_IRQ : no
periodic_freq : 1024
batt_status : okay
I am wondering if the periodic_IRQ is needed and a freq of 1000 based on what I read about zaptel. Not sure. > Yes, but if you didn't need MeetMe it would be silly to try to
> diagnose it.
>
> I suspect ztdummy is loading correctly, but the system is not
> generating interrupts for ztdummy sync to. Traditionally ztdummy
> used a USB interface to get timing, but at some point I think it
> switched to using the kernel RTC if available.
>
> I don't use ztdummy -- I'm just recalling what I've seen on the
> mailing lists and IRC over the years.
>
> Tony Plack wrote:
>> We are going to implement MeetMe, but this should still work
>> right?
>>
>>> Tony Plack wrote:
>>>
>>>> I have an interesting issue. I am running Asterisk 1.4 (SVN
>>>>
>>>> branch latest) and same with Zaptel.
>>>>
>>>>
>>>> If I load ztdummy, my audio in BackGround (or Playback)
>>>> cannot be
>>>>
>>>> heard. If I rmmod ztdummy and restart Asterisk, Background
>>>>
>>>> works. What am I missing?
>>>
>>>
>>> What things are you using that requires zaptel timing (ztdummy)?
>>>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
|
_______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
