[asterisk-bugs] [JIRA] (ASTERISK-19533) Script run from #exec can't connect to the manager on initial start or restart of Asterisk

[Corey Farrell (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-19533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Corey Farrell updated ASTERISK-19533:
-------------------------------------

    Assignee: Philippe Lindheimer
      Status: Waiting for Feedback  (was: Open)

Is this still an issue in currently supported branches?  If so can you provide the DEBUG logs [~mjordan] requested?  Also please provide your {{modules.conf}}

Based on what I see in the code, the AMI listening socket is opened from the main thread, meaning that AMI is listening for clients before init_manager() returns.

The possible explanation I see for this is if you have pbx_config set to preload in {{modules.conf}}.  This will not work as preload modules are started before AMI.  If this is the case you will need to either remove the preload setting from pbx_config, or not use AMI during its load.

> Script run from #exec can't connect to the manager on initial start or restart of Asterisk
> ------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-19533
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19533
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Codecs/General
>    Affects Versions: 1.8.8.2, 10.2.0
>         Environment: Detected on FreePBX but general issue
>            Reporter: Philippe Lindheimer
>            Assignee: Philippe Lindheimer
>            Severity: Minor
>
> Trying to open up an AMI connection from a #exec script in the dialplan fails upon Asterisk starting or restarting. It works other times. This mechanism is used to generate hints in the dialplan based on dynamic information that is only available in the AstDB and on all releases at least 1.8 and prior going into the manager is the only way to get such information.
> I have tested that this fails on 1.4.22-ish (and SVN build about that time), 1.4.32, 1.8.8.0, 10.2.0. As such I have said "No" to it being a regression though I believe at some point probably prior to 1.4.22 this may have worked. It may have been in 1.2?



--
This message was sent by Atlassian JIRA
(v6.2#6252)