Hi We're still testing out asterisk 1.8 (using 1.8.2.2 from rpm package) before putting it into production and I'm observing an odd issue when using the AMI Every request I send to the AMI just results in a FullyBooted response rather than the expected response. Here are some examples from my logs -- Call started: 22/02/2011 11:34:03 -- action: command command: core show channels Event: FullyBooted Privilege: system,all SequenceNumber: 1706 File: manager.c Line: 2937 Func: action_login Status: Fully Booted -- Call started: 22/02/2011 10:28:15 -- action: command command: sip show peers Event: FullyBooted Privilege: system,all SequenceNumber: 1610 File: manager.c Line: 2937 Func: action_login Status: Fully Booted Has anyone else experienced anything like this? -- Ishfaq Malik Software Developer PackNet Ltd Office: 0161 660 3062
On 11-02-23 05:39 AM, Ishfaq Malik wrote:> Has anyone else experienced anything like this? >There is a patch on the issue tracker[1], please test it out and report your feedback. [1] https://issues.asterisk.org/view.php?id=18168 -- Paul Belanger Digium, Inc. | Software Developer twitter: pabelanger | IRC: pabelanger (Freenode) Check us out at: http://digium.com & http://asterisk.org
Hi, I have this same behaviour on version 1.8.2.3 build from source. We are using AMI to originate call from our CRM software, but we ignore that message. Regards, Marcin
On Feb 23, 2011, at 4:39 AM, Ishfaq Malik wrote:> Hi > > We're still testing out asterisk 1.8 (using 1.8.2.2 from rpm package) > before putting it into production and I'm observing an odd issue when > using the AMI > > Every request I send to the AMI just results in a FullyBooted response > rather than the expected response. Here are some examples from my logs > > -- Call started: 22/02/2011 11:34:03 -- > action: command > command: core show channels > > Event: FullyBooted > Privilege: system,all > SequenceNumber: 1706 > File: manager.c > Line: 2937 > Func: action_login > Status: Fully Booted > > > -- Call started: 22/02/2011 10:28:15 -- > action: command > command: sip show peers > > Event: FullyBooted > Privilege: system,all > SequenceNumber: 1610 > File: manager.c > Line: 2937 > Func: action_login > Status: Fully Booted > > > Has anyone else experienced anything like this?Is this a new AMI connection for each command? If so, that is the problem. Whenever a connection is made, Asterisk informs the connector that it is FullyBooted and it is safe to start sending commands. If it didn't do this, if multiple machines are making a new connection, only one of them would get notified. The proper thing to do would be to maintain an open connection for sending commands, or to expect the command upon connection and only send after that. You are probably getting the message you expect after the FullyBooted response, so this would be a parsing error on your part. Assign an ActionID to the event you send and the response you are looking for will have that ActionID in it as well.
> Hi, > > I have this same behaviour on version 1.8.2.3 build from source. We are using AMI to originate call from our CRM software, but we ignore that message.The patch for the bug at https://issues.asterisk.org/view.php?id=18168 has been committed (thanks FeyFre!). The FullyBooted event will no longer be broadcast to every connection each time someone connects. It will still be sent to the individual connections upon successful authentication. AMI applications should all really listen for the FullyBooted event before doing anything of consequence since it is possible to connect to AMI and send a command before the module that would normally handle the command is loaded. This would result in missed commands. Terry -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20110224/8fb2430e/attachment.htm>