A New Timing API for Asterisk, Silencing Digium Critics

Russell Bryant has post details of a new timing API for Asterisk:

Starting with Asterisk 1.6.1, you will no longer need DAHDI installed at all to get proper timing in Asterisk. There is a new timing API, and there are already two implementations. There is a DAHDI timing interface (res_timing_dahdi) and another (res_timing_pthread) that has no special kernel requirements.

I hope this will shine some much needed light on the folks that are clamoring that Digium is keeping Asterisk proprietary by requiring a DAHDI timing source. One particularly annoying blog post states that the Asterisk fork(s) and other related VoIP/PBX software are gaining speed, because they are not tied to ‘proprietary timers needed for the Digium version of Asterisk.’

Need I inform you (usken.no) that:

  • The DAHDI interface has never been proprietary, the code is open and licensed under the GPL.
  • Timing is only utilized for MeetMe, the IAX2 Trunking feature and optionally during file playback.
  • app_conference is an alternative to MeetMe.
  • IAX2 Trunking feature is an optional feature that is not friendly to voice quality in high packet loss situations, so the loss of a timing device does not cripple or otherwise hinder Asterisk whatsoever.
  • File playback has a ’software timing’ method, if no DAHDI timing is available. This software timing method very well may also be available to IAX2 Trunking, but I am unsure if that functions or not.

I do not see any proprietary timers that are hindering Asterisk.

I see this post from usken.no as yet another attempt to slant the reasoning why people positioned themselves against Digium’s efforts.

Granted I have not agreed with every decision Digium has made (who does?) however I do see that Digium’s interest is very much with keeping Asterisk open source, along with developing a viable business model and an ever evolving ecosystem around its open source creation.

Additional Related Articles

Comments are closed.