Hi,
-Original Message-
But the thought is correct, use a database to store the data
and one context that does a lookup into the database and
populates your callerid. It is a better way of doing things.
You could even host it in the ast_db and then it shouldn't be
too slow as you
Hi Sim :)
you seem to be one of the top candidates as a ast_data power tester :)
On Sat, 2004-06-19 at 12:14, Florian Overkamp wrote:
Hi,
-Original Message-
But the thought is correct, use a database to store the data
and one context that does a lookup into the database and
Hi Michael,
-Original Message-
Hi Sim :)
you seem to be one of the top candidates as a ast_data power tester :)
I'm game, tell me more :-)
Here's another scenario I'm working with: I am using
contexts per user
to 'include' the numberranges they are allowed to dial. Any
check #sboost and open your eyes :)
all that does not work as promised yet is:
I can't seem to get context includes right
MWI is tricky
and
I don't know how to specify odecs correctly
Besides that it works fantasticly, even in chaos DB setup where the
extension from he table triggers a ODBCget app
PROTECTED]
Subject: RE: [Asterisk-Users] Thousands of contexts?
Hi,
-Original Message-
But the thought is correct, use a database to store the data
and one context that does a lookup into the database and
populates your callerid. It is a better way of doing things.
You could
Michael Bielicki wrote:
Hi Sim :)
you seem to be one of the top candidates as a ast_data power tester :)
ast_data has gotten bloated beyond belief.
All one needs is a proper understanding of the power of Asterisk's dial
plan and you won't EVER have a need for thousands of contexts.
Use what Mark
Jeremy McNamara wrote:
Michael Bielicki wrote:
Hi Sim :)
you seem to be one of the top candidates as a ast_data power tester
:)
ast_data has gotten bloated beyond belief.
All one needs is a proper understanding of the power of Asterisk's
dial
plan and you won't EVER have a need
By reading the Wiki's I found out that an Asterisk server with many (1)
extensions and/or SIP users can become slow when reloading. But what happens when you
also have many contexts in extensions.conf? More precisely, one context for each SIP
user?
I need this because I will have users
Why not use mysql as it should be faster I'd suspect
-Original Message-
From: Manuel Wenger [mailto:[EMAIL PROTECTED]
Sent: 18 June 2004 5:43 PM
To: [EMAIL PROTECTED]
Subject: [Asterisk-Users] Thousands of contexts?
By reading the Wiki's I found out that an Asterisk server with many
Manuel Wenger wrote:
By reading the Wiki's I found out that an Asterisk server with many (1)
extensions and/or SIP users can become slow when reloading. But what happens when you
also have many contexts in extensions.conf? More precisely, one context for each SIP user?
I need this because I
Manuel Wenger [EMAIL PROTECTED] wrote:
By reading the Wiki's I found out that an Asterisk server with many
(1) extensions and/or SIP users can become slow when reloading. But
what happens when you also have many contexts in extensions.conf? More
precisely, one context for each SIP user?
-Users] Thousands of contexts?
Why not use mysql as it should be faster I'd suspect
-Original Message-
From: Manuel Wenger [mailto:[EMAIL PROTECTED]
Sent: 18 June 2004 5:43 PM
To: [EMAIL PROTECTED]
Subject: [Asterisk-Users] Thousands of contexts?
By reading the Wiki's I found out
To: [EMAIL PROTECTED]
Subject: [Asterisk-Users] Thousands of contexts?
By reading the Wiki's I found out that an Asterisk server with many (1)
extensions and/or SIP users can become slow when reloading. But what happens
when you also have many contexts in extensions.conf? More precisely
-Messaggio originale-
Da: Kevin Walsh [mailto:[EMAIL PROTECTED]
I don't quite understand your Caller*ID dilemma.
In your sip.conf, you'd have a block for each user, say [abc123].
That's your random username, yes? The same block would also
define the password and other directives.
14 matches
Mail list logo