Jay Phillips

Wow, okay, I see the problem now. This is an anomaly to the AMI protocol that I didn't foresee. At the moment only "Response: Follows" messages have bodies that...

The best way for my to debug issues like this with the AMI parser is to see a telnet exchange reproducing the exact text which the parser fails to parse.

Could ...

If you're using this in a standalone Ruby process and want only to capture events in order, I'd probably recommend subclassing ManagerInterface and overriding e...

Doh, sorry, I misread your original post about the buffer size. I wrote that in a coffee shop earlier today and clearly wasn't paying much attention. :)

I'm sti...

Does increasing the buffer size help the problem? Attached is a patch file that will do that. Give that a try. 8kb does seem kinda small...

Try adding this to startup.rb:

Adhearsion::VoIP::Asterisk::ManagerInterface::CAUSAL_EVENT_NAMES << "dbget"

Does that fix the error?

Opening this ticket but I don't think I'm going to be able to get to this soon.

Fixed URL in master.

Are you sure that UserEvent is a valid AMI action? I don't see it after a cursory internet search. Everything I can find suggests it's just a dialplan applicati...