[asterisk-bugs] [JIRA] (ASTERISK-28433) More than 1 AMI connection ends up dying

[Luke Escude (JIRA)]

Luke Escude created ASTERISK-28433:
--------------------------------------

             Summary: More than 1 AMI connection ends up dying
                 Key: ASTERISK-28433
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28433
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Core/ManagerInterface
    Affects Versions: 16.3.0
         Environment: CentOS 7 x64
            Reporter: Luke Escude
            Severity: Minor


I'll need some help figuring out a proper diagnostic approach to help you guys out, since I don't have any ideas on how to recreate the issue consistently with valuable results. Anyways...

With a single AMI connection, the connection lasts forever - Ping, various commands, etc. the pipe never dies.

As soon as a second AMI connection forms to asterisk, it doesn't seem to survive - Meaning a Ping command (and all other commands) will suddenly stop returning any data. But, the socket doesn't seem to die.

A secondary issue is that some Originate commands will cause the AMI socket pipe to completely lock up for 10 seconds+ but I'd rather solve this issue first.

Any ideas on how to learn more details? The second AMI connection can typically last about a day, then drops off.

Interestingly, running 'manager show connected' after the second connection drops causes ALL further asterisk CLI output to not exist - The CLI will no longer push any information to the screen until you exit then re-enter the CLI again.



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