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

[Andrew Nagy (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-19533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226052#comment-226052 ] 

Andrew Nagy commented on ASTERISK-19533:
----------------------------------------

Previously. In some initial alpha build of Asterisk 12 preloading pbx_config would crash Asterisk. [~mjordan] fixed this and said that pbx_config no longer needed to be preloaded. Possibly as far back as 1.8... however I am not sure. In FreePBX we still preload pbx_config on first install. 

> 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: Rusty Newton
>            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)