On Mon, Jul 27, 2009 at 12:34:35AM +0200, Philipp Kempgen wrote:
> Well, the AEL compiler adds lots of calls to NoOp(). These priorities
> serve as jump addresses for control structures like if, switch etc.
> ... NoOp("Console/dsp", "Finish if-if-if-from-pstn-604-606-607") in new stack
> IMHO thes
I think if someone knows well how to make dialplans in regular
extensions.conf file, then there is nothing much to learn about AEL. There
is a page on voip-info.org on AEL (
http://www.voip-info.org/wiki/view/Asterisk+AEL) and to me it proved to be
more than enough to switch to AEL. I used only tha
When using call files I see Dial command when on the CLI
however when using the AMI I dont see the originate Dial.
Is there a logging level that will show the originate dial on the CLI?
If there isnt currently a log state for that shouldnt it do that just
like the
call files do?
My logger.conf h
Steve Edwards schrieb:
> On Sun, 26 Jul 2009, Philipp Kempgen wrote:
>
>> Does anybody else have the feeling that custom messages (Verbose(1,...))
>> do not stand out enough on the CLI?
>
> Yes.
>
>> We're sending messages like "Extension 123 is unknown" to the output and
>> that should tell t
On Sun, 26 Jul 2009, Philipp Kempgen wrote:
> Does anybody else have the feeling that custom messages (Verbose(1,...))
> do not stand out enough on the CLI?
Yes.
> We're sending messages like "Extension 123 is unknown" to the output and
> that should tell the user why a call to 123 fails but u
We have an inbound PRI connected to our Cisco 3825 router which is then
passing the calls to Asterisk as SIP calls. We're getting the CallerID
number but not the CallerID name. We are seeing the name in the RPID field
with a SIP trace on the Asterisk box but don't understand why it's not
register
The pem file should contain both the private key and the certificate.
On Jul 24, 2009, at 4:08 PM, John A. Sullivan III wrote:
> Hello, all. After many pages of googling and testing in the lab, I'm
> still a bit perplexed about how to implement tls protection for the
> asterisk manager. manage
Hi,
After upgrading a debian/lenny server to 1.4.26 I get this error:
== Manager 'munin' logged off from 127.0.0.1
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'munin' logged on from 127.0.0.1
[Jul 26 17:45:12] ERROR[12354]: utils.c:966 ast_caref
Does anybody else have the feeling that custom messages
(Verbose(1,...)) do not stand out enough on the CLI?
We're sending messages like "Extension 123 is unknown" to the output
and that should tell the user why a call to 123 fails but users fre-
quently crank up the verbosity to 3 or 10 so our mes
harry R wrote:
> In advance sorry for my bad english and if my problem was already
> exposed (I didn't find any tips in the mailing list archive. Bad luck)
> I have some questions about asterisk 1.6 release :
> 1) how can I do a n+101 priority jumping if a SIP canal is busy ?
> I read that the gen
Miguel Molina wrote:
> Well some colleagues at work who went to the 2008 Astricon told me that
> all skilled asterisk programmers used AEL and not plain extensions.conf.
I would disagree with that, as I consider myself a skilled Asterisk user, and I
don't use AEL :)
While I like the concept of
11 matches
Mail list logo
