[OPEN-ILS-DEV] Asterisk scheduling controls

[Joe Atzberger]

>
> Options seem to be:
>>>
>>>   1. shutdown asterisk (instance)
>>>   2. maybe unload just the spool module part of asterisk (pbx_spool iirc)
>>>   3. mv callfiles outside spool directory, mv back at "open" time
>>>   4. update date modified to next "open" time
>>>   5. never queue more than one round of calls per channel, so there
>>>      *shouldn't* be much backlog
>>>
>>> The first is dead certain, but also overkill.  If we wanted to go that
>>> route, I would push for a proxy layer that EG can treat like one Asterisk
>>> instance, rather than needing a bunch of different instance configs.
>>>
>> Is a couple couple cron calls overkill compared to a proxy layer?  IMO a
> shutdown of Asterisk is just proper insurance against any untimely calls,
> and I would want a separate Asterisk box/instance for EG calls vs my main
> phone system.



No, I mean shutting down asterisk is overkill when it also handles other
mission-critical non-EG telephony.  I like the idea of a dedicated system,
but I don't get to dictate what hardware will be in use, or that our clients
buy another box, so that leaves running multiple instances on the same box.
 I'm curious how that would work in practice, since I would expect blocking
if different asterisks tried to use the same card/channel, resulting in an
increased rate of failure.  Probably would be OK w/ SIP though.

You don't need to unschedule calls if you use a temp dir and have a program
> feed the call files to the spool dir, you simply stop that program.  Any
> left over call files are left in the temp dir.


Yeah, that seems reasonable.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://libmail.georgialibraries.org/pipermail/open-ils-dev/attachments/20091216/01bcb627/attachment.htm