On 20/03/2009 7:05 a.m., Klaus Darilion wrote:
Until yet I tried to avoid storing permanent data in the astDB. Did you
ever had any issues with astDB - e.g. that data gets lost, DB is corrupt
... when Asterisk crashes?
Not so far on any machines - in fact, the one I developed this on had
Matt Riddell schrieb:
On 17/03/2009 9:10 a.m., Doug wrote:
So to make extension 201 in pickup group 1 just do:
asterisk -rx 'database put pickupgroup 201 1'
So this is a command line argument. Can this
be automated? Whenever we do a reload, can
this be stored?
The
On 17/03/2009 9:10 a.m., Doug wrote:
This looks great! A few questions...
in the standard extension macro we add a line:
Is this in extensions.conf?
Yeah, we have a macro (which is in the default extensions.conf) which we
add that line to.
exten =
At 22:22 3/13/2009, Matt Riddell wrote:
On 14/03/2009 10:29 a.m., Doug wrote:
At 16:10 3/10/2009, Matt Riddell wrote:
On 7/03/2009 4:58 a.m., Klaus Darilion wrote:
Hi!
What are the typical ways to work around the 64 groups limit?
What we actually do is store a
At 16:10 3/10/2009, Matt Riddell wrote:
On 7/03/2009 4:58 a.m., Klaus Darilion wrote:
Hi!
What are the typical ways to work around the 64 groups limit?
What we actually do is store a pickup group with a caller id.
So the AsteriskDB has ${DB/pickup/${CALLERID(num)}} and we set
On 14/03/2009 10:29 a.m., Doug wrote:
At 16:10 3/10/2009, Matt Riddell wrote:
On 7/03/2009 4:58 a.m., Klaus Darilion wrote:
Hi!
What are the typical ways to work around the 64 groups limit?
What we actually do is store a pickup group with a caller id.
So the
Benny Amorsen schrieb:
Klaus Darilion klaus.mailingli...@pernau.at writes:
What are the typical ways to work around the 64 groups limit?
a) Split into different Asterisks
b) Use directed pickup instead, not *8
Maybe we should change the groups from a bitmask to an AST_LIST
regards
Benny Amorsen schrieb:
Klaus Darilion klaus.mailingli...@pernau.at writes:
What are the typical ways to work around the 64 groups limit?
b) Use directed pickup instead, not *8
So I would have to implement privileges (who is allowed to pick up whose
calls) manually - not easy
klaus
Klaus Darilion klaus.mailingli...@pernau.at writes:
Maybe we should change the groups from a bitmask to an AST_LIST
That would be a serious pessimization, but I guess it would work if
every phone is in just a few groups. The optimal implementation would
probably be a bit vector.
/Benny
On Tue, Mar 10, 2009 at 05:00:38PM +0100, Benny Amorsen wrote:
Klaus Darilion klaus.mailingli...@pernau.at writes:
Maybe we should change the groups from a bitmask to an AST_LIST
That would be a serious pessimization,
Also space-wise
but I guess it would work if
every phone is in just
On 7/03/2009 4:58 a.m., Klaus Darilion wrote:
Hi!
What are the typical ways to work around the 64 groups limit?
What we actually do is store a pickup group with a caller id.
So the AsteriskDB has ${DB/pickup/${CALLERID(num)}} and we set
pickupmark to the same.
That way when someone dials 29
Hi!
What are the typical ways to work around the 64 groups limit?
thanks
klaus
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
Klaus Darilion klaus.mailingli...@pernau.at writes:
What are the typical ways to work around the 64 groups limit?
a) Split into different Asterisks
b) Use directed pickup instead, not *8
/Benny
___
-- Bandwidth and Colocation Provided by
13 matches
Mail list logo
