[ATrpms-users] Asterisk dependencies

Philip Prindeville philipp_subx at redfish-solutions.com
Wed Jul 5 20:48:20 CEST 2006


Axel Thimm wrote:
> On Thu, Jun 29, 2006 at 03:42:50PM -0600, Philip Prindeville wrote:
>   
>> Mark Wormgoor wrote:
>>     
>>> Hi,
>>>
>>>   
>>>       
>>>> Would it make sense to remove the dependency of Asterisk on
>>>> zaptel and libtonezone?  Or even spandsp?
>>>>
>>>> Some of us are using the natively SIP handsets like the Zyxel
>>>> or Vtech...
>>>>     
>>>>         
>>> Asterisk always needs zaptel. You need to have a good timing module, and 
>>> only the zaptel kmdl provides them (ztdummy). The rc.d script for 
>>> loading the kmdl is in the zaptel module.  And zaptel depends on 
>>> libtonezone.
>>>
>>> As for spandsp, the app_rxfax and app_txfax are now part of asterisk, so 
>>>   rpm automatically requires spandsp. Unless these modules are split 
>>> into a separate package (asterisk-fax?), the dependency remains.
>>>
>>> Kind regards,
>>>
>>> Mark
>>>   
>>>       
>> There were some noises about further breaking Asterisk down into
>> finer granularity.  That would be a good thing, and would more fully
>> exploit the ability to tailor/configure Asterisk to a wide range of
>> applications.
>>     
>
> Do you have a pointer?
>   

I'm thinking back to your message of 5/31 (ref: <20060601000953.GJ2163 at neu.nirvana>).



>> Has there been any movement on this?
>>
>> And what is the strategy?
>>     
>
> Not sure whether you mean some discussion at upstream level or at
> package level.
>   

I didn't look to see if Asterisk came with packaging done upstream or
if ATrpms generates its own packaging (or heavily modifies upstream
packaging).


>> Could the timing module ztdummy (since it doesn't actually correspond
>> to real hardware, if I've understood correctly) be made part of a
>> stand-alone asterisk-kmdl rpm instead?
>>     
>
> Technically yes, but what would the gain be? A smaller kmdl package?
> Zaptel kmdls are about 250-350k, not really big (if compared for
> instance to the kernel rpm).
>   

Well, I'm thinking that most of the zaptel package should be support for
various physical cards.  If you're running pure VoIP with SIP peering
with other call-managers, then you don't need to support any sort of
trunking (FXS, FXO, PRI, T1/CCS, etc).

The ztdummy module, on the other hand, sounds like it doesn't
correspond to any particular hardware... it just provides a kernel
service required by Asterisk itself.

-Philip




More information about the atrpms-users mailing list