It's 2014 peoplez
Handle a corner case with recognition better

If we run a series of recognition requests and answer one correctly, and then hang up in the middle of the second (or otherwise cause the recognition to return in the 'INTERRUPTED' state) the complete method reads the old value for RECOG_COMPLETION_CAUSE and attempts to parse an empty string, throwing an exception. Handle a message coming back from a recognition request that is in the 'INTERRUPTED' state in a manner that doesn't cause an unchecked exception to be thrown (thus crashing the call and preventing any post-call actions from occurring)

Add changelog entry

Refactor for style guidelines
Merge pull request #230 from runningferret/feature/handle_interrupted_recog_take2

Handle a corner case with recognition better
Pin to Celluloid 0.15.x due to possible incompatibility with Celluloid 0.16

Pending investigation
[BUGFIX] Fix possible infinite blocking

Avoid cases where executing AGI commands (reported as sending SIP messages) might block indefinitely due to a race condition in fetching their response value.

Requires a fix to Celluloid: https://github.com/celluloid/celluloid/issues/456
Merge branch 'feature/reliable-agi-response-wait' into develop
Bump to 2.5.3
Merge branch 'release/2.5.3' into develop
allow runtime setting of Recognition-Timeout

Resolved conflicts:
	lib/punchblock/translator/asterisk/component/mrcp_recog_prompt.rb

send recognition timeout setting as UniMRCP option

allowing dynamic setting of Recognition-Timeout in the MRCP messaging
with speech recognition server

Resolved conflicts:
	lib/punchblock/translator/asterisk/component/mrcp_recog_prompt.rb

add test for setting recognition-timeout header

update changelog