Hi,<br><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;" lang="EN-US"><br>I'm currently study the alternatives I can use to implement an alternative clock source for Asterisk. After some research I
found two options some developers are doing.</span></font>
<p class="MsoNormal"><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;" lang="EN-US">The first solution is described on
Digium's bug tracker (<a title="blocked::http://bugs.digium.com/view.php?id=8896" href="http://bugs.digium.com/view.php?id=8896">http://bugs.digium.com/view.php?id=8896</a>).
The idea is to use a patched ztdummy with a new module. This module will
register itself to ztdummy and it will implement the interrupt handler.
Since ztdummy is already registered to zaptel, my clock will be used. This
solution is being used with mISDN driver.</span></font></p>
<p class="MsoNormal"><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;" lang="EN-US">The second solution is to make a
ztdummy "clone" with my code controling the clock.... The idea is very similar to
the first one but the ztdummy-clone will register itself directly to
zaptel. I'll need to patch zaptel's Makefile to compile my "clone" and so
on….Ztxen uses this solution (XEN
virtualization).</span></font></p>
<p class="MsoNormal"><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;" lang="EN-US">Both options are very similar and they need to keep zaptel device driver running to do it.</span></font></p>
I'd like to know if there are another alternative which doesn't need zaptel.<br><br>Any information will be useful!<br><br>Thanks in advance!<br><font face="Arial" size="2"><span style="font-size: 10pt; font-family: Arial;" lang="EN-US">
</span></font><br>-- <br>--------------<br>Paulo Garcia<br><br>