…o return channel info to fs_cli. In this feature I just exposed the structure of event and event.content, and their keys, added checks that we are in fact getting json objects as we're supposed to, and stated in channel output that channel keys are specific for _that_ event. If a different one of a different type comes in, those keys will change but you can always see what. This is your internals 'control' feature. You got this passing, you have reusable statements for capturing shifting channel data structure cleanly printed.
…ng some of the reports kicked off.
…ture completed. I wrote *this* feature also for the specific purpose of it being _a_ feature where you are also shown internal specifics. Should help to write tests. Just rerun 'cucumber features/003_can_retrieve_channel_information.feature'
…vent-json', otherwise fail miserably. Now on to playing with event.content more
…9192 does is return channel information. Exposed event info, and content hash keys. content contains the channel data. event is a wrap around content in order to provide headers hash. hash contains length and type. event.content hash keys are exposed. Looks to caller_id_unique_id, unique_id, caller_channel_name, caller_dialplan, variable_current_application, variable_current_application_data, channel_state, channel_state_number, channel_name.
…s, and step matchers for isolating channel vs event over that channel
… the merge
…to change the wav files hunted, and tweak the connect
…ly, and failures to *always* be displayed.
…place with the listeners. Also did a bit of cleanup and attributation for Travis-CI
… Logged in.
…at the same place, as expected.
…m, should we need to.