Warren Selby wrote 30.03.2012 18:37:
> A couple things - what
version of asterisk are you using? Are you actually using zaptel or do
you have DAHDI as your interface to your TDM cards?
Asterisk
SVN-branch-1.4-r359615
I have to work with wicked Tormenta cards with
weird chip which requires s
On Fri, Mar 30, 2012 at 8:43 AM, Mikhail Lischuk wrote:
> **
>
> Warren Selby wrote 29.03.2012 22:46:
>
>
>>
> To do this, you change your features.conf setting like so:
>
> parse => *9,peer/both,Macro,Parse
>
>
> The same result when I changed to Macro. I believe that it's true that
> callerid on
Warren Selby wrote 29.03.2012 22:46:
>>
>
> To do this, you
change your features.conf setting like so:
>
> parse =>
*9,peer/both,Macro,Parse
The same result when I changed to Macro. I
believe that it's true that callerid on outgoing call is "crap shoot".
Here is output:
-- Executing [044
On Thu, Mar 29, 2012 at 2:16 PM, Mikhail Lischuk wrote:
> **
>
> Warren Selby писал 29.03.2012 20:20:
>
> I'd be really curious to see the entire CLI log of the call, with
> verbose set to 6 and AGI debug enabled, from when the call first comes in
> to when it's hung up, including the execution
, March 29, 2012 2:17 PM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] AGI variables being wrong
Warren Selby писал 29.03.2012 20:20:
I'd be really curious to see the entire CLI log of the call, with verbose set
to 6 and AGI debug enabled, from whe
Warren Selby писал 29.03.2012 20:20:
> I'd be really curious
to see the entire CLI log of the call, with verbose set to 6 and AGI
debug enabled, from when the call first comes in to when it's hung up,
including the execution of the *9 feature code. Also, knowing which
version of Asterisk and D
On Thu, Mar 29, 2012 at 10:10 AM, Steve Edwards
wrote:
> On Thu, 29 Mar 2012, Mikhail Lischuk wrote:
>
> I have the following line in features.conf:
>> parse => *9,peer/both,AGI,/etc/**asterisk/agi/map.pl
>>
>
> I've never invoked an AGI from 'features,' but I'll assume it's 'the same'
> as execu
On Thu, 29 Mar 2012, Mikhail Lischuk wrote:
I have the following line in features.conf:
parse => *9,peer/both,AGI,/etc/asterisk/agi/map.pl
I've never invoked an AGI from 'features,' but I'll assume it's 'the same'
as executing an AGI from the dialplan.
During outgoing call, those variables
Greetings!
I have the following line in features.conf:
parse =>
*9,peer/both,AGI,/etc/asterisk/agi/map.pl
What that script does is
parsing AGI variables and doing some things based on them, nothing
special.
During outgoing call, those variables get messed up. Let's
look at an example: numb
