[asterisk-dev] BugID 014021, Zap/DAHDI timers, internal timing and packetization

Russell Bryant russell at digium.com
Thu Dec 11 07:24:14 CST 2008


Dan Austin wrote:
> If you've followed my poor description this far, my question
> is can the /dev/[zap|dahdi]/timer interface support different
> clockrate for each channel that opens it?  If it cannot, then
> bug 014021 cannot be solved in 1.4 or 1.6.0, at least not with
> trivial changes to the code.  It might be possible to resolve
> it in 1.6.1 using the new res_timing_* interfaces.

Yes, you can set a rate for each open DAHDI timer.

Take a look at res_timing_dahdi.c in Asterisk trunk or 1.6.1. 
Specifically, the function dahdi_timer_set_rate() is how you set it.

-- 
Russell Bryant
Senior Software Engineer
Open Source Team Lead
Digium, Inc.



More information about the asterisk-dev mailing list