[asterisk-dev] Methodologies for validating dialplan

[Joshua C. Colp]

On Tue, Jan 4, 2022 at 7:00 PM <asterisk at phreaknet.org> wrote:

> On 1/4/2022 5:49 PM, Joshua C. Colp wrote:
>
> On Tue, Jan 4, 2022 at 6:22 PM <asterisk at phreaknet.org> wrote:
>
>> That's a really fair point - maybe another potential source of
>> improvement?
>>
>> I do use AMI for some things, but I have no use for the "Newexten" and
>> "Varset" AMI events (if I run my "amidump.php" script, I'll see hundreds
>> of these constantly even for a single call).
>>
>> In addition, it makes using core set debug >= 3 a real pain, because
>> then every complete AMI event is dumped, the result of which is that 90%
>> of the debug suddenly becomes an AMI dump of new exten and new vars.
>>
>
> Stasis events can be disabled in stasis.conf, I don't know the
> ramifications of disabling new exten but varset is fine. Generating the
> stasis events is what can be expensive.
>
> Thanks, I'll play around with disabling both of them and see how much that
> helps.
>
> I see "ast_channel_varset_type" in stasis.conf - which one would be the
> right one for disabling Newexten? I poked around the code a bit but I'm not
> following the connection as much.
>
A quick look at the code in manager_channels.c that generates it shows it
as being done based on channel snapshots, so not possible to disable the
stasis side.

-- 
Joshua C. Colp
Asterisk Technical Lead
Sangoma Technologies
Check us out at www.sangoma.com and www.asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20220104/88f3f47f/attachment-0001.html>