[Home]

Summary:ASTERISK-21667: No AMI events output until Asterisk receives an AMI command
Reporter:Arkadiusz Malka (yarns)Labels:
Date Opened:2013-04-23 05:59:38Date Closed:2013-05-30 11:30:44
Priority:MajorRegression?
Status:Closed/CompleteComponents:Core/ManagerInterface
Versions:11.3.0 Frequency of
Occurrence
Constant
Related
Issues:
Environment:CentOS 6.3Attachments:( 0) myDebugLog.zip
Description:manager.conf

[general]
enabled = yes
webenabled = no
port = 5038
bindaddr = 192.168.1.215
timestampevents = yes


[test]
secret=test
read = all
write = all

After login i can get only this:
Asterisk Call Manager/1.3
Action: login
Username: test
Secret: test

Response: Success
Message: Authentication accepted

Event: FullyBooted
Privilege: system,all
Status: Fully Booted

Then there is no input until i send something. After sending \r\n it returns events and at the end response to sended data (error in this case):
Event: RTCPSent
Privilege: reporting,all
Timestamp: 1366714610.822301
To: xxxxxxxxxxxxxxx
OurSSRC: 1740974660
SentNTP: 1366714610.3368054784
SentRTP: 3114792
SentPackets: 19464
SentOctets: 3114240
ReportBlock:
FractionLost: 0
CumulativeLoss: 0
IAJitter: 0.0001
TheirLastSR: 3856155382
DLSR: 390.0890 (sec)

Event: RTCPSent
Privilege: reporting,all
Timestamp: 1366714611.621060
To: xxxxxxxxxxxxxxxxxxx
OurSSRC: 903999879
SentNTP: 1366714611.2543775744
SentRTP: 1218960640
SentPackets: 752
SentOctets: 120320
ReportBlock:
FractionLost: 0
CumulativeLoss: 0
IAJitter: 0.0006
TheirLastSR: 0
DLSR: 26867.6210 (sec)

Response: Error
Message: Missing action in request

Comments:By: Michael L. Young (elguero) 2013-04-23 10:06:18.644-0500

We require a complete debug log to help triage the issue. This document will provide instructions on how to collect debugging logs from an Asterisk machine for the purpose of helping bug marshals troubleshoot an issue: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information



By: Arkadiusz Malka (yarns) 2013-04-23 11:26:03.570-0500

Got debug log, but it contains some sensitive data. Can we make this private, before i post log file?

By: Michael L. Young (elguero) 2013-04-23 11:40:19.709-0500

You can either sanitize the data (remove sensitive data) or I can have someone mark this as a security issue which will make it private to developers, bug marshals and you.

By: Arkadiusz Malka (yarns) 2013-04-23 12:09:26.771-0500

Debug log

By: Michael L. Young (elguero) 2013-04-23 12:19:43.586-0500

What are you using to connect to the manager?  Telnet?

By: Arkadiusz Malka (yarns) 2013-04-23 13:36:11.808-0500

Mostly low level sockets, but the same behavior is when connected using putty (raw or telnet)

By: Michael L. Young (elguero) 2013-04-23 15:31:44.389-0500

I have done testing on 11 branch, 11.3 and on trunk.  I have tested on CentOS 5.9 and Fedora 18.  I have been unable to reproduce this issue.  I have used telnet and putty without any issues.  As soon as I login, events start coming through.

By: Arkadiusz Malka (yarns) 2013-04-24 04:32:04.346-0500

Found same issue here: http://stackoverflow.com/questions/12215028/not-receiving-events-on-asterisk-11-ami
Any idea what else i should check to find out why it happens?

By: Rusty Newton (rnewton) 2013-05-13 18:36:50.903-0500

@Arkadiusz, I recommend setting up a clean install of Asterisk with default configs and starting from that - see what the most minimal configuration you can use to reproduce the problem.

We can't reproduce the issue and unless you can show us how we won't be able to track it down.

I'm not sure what other debug you could get that would be helpful. You could compile with DEBUG_THREADS and try "core show locks" to see if anything is locking specifically before it starts spitting out events. Theres a small chance it could be useful.

https://wiki.asterisk.org/wiki/display/AST/CLI+commands+useful+for+debugging#CLIcommandsusefulfordebugging-%27coreshowlocks%27

If you can't find a way to reproduce it consistently then I'll close this out as "can't reproduce". At some point someone will find a way to reproduce it and then we can re-open the issue.


By: Rusty Newton (rnewton) 2013-05-30 11:33:04.816-0500

Closed. If anyone finds a way to reproduce (or at least narrow it down to a possible cause) and can describe how then please comment here or ping a bug marshal in #asterisk-bugs to re-open.