cami: Handle async OriginateResponse.

When issuing an async Originate action, we immediately get an eventless
Success response (with the corresponding ActionID), but then later
get back an OriginateResponse with the same ActionID. This confused
the current parsing, as the "ActionID" bit would lead us to set
middle_of_response = 1 and then get stuck, thinking we were in
the middle of a response, leading to further events getting lost.

To mitigate this, if we get an event with an Action ID but a response
was not already pending, don't set middle_of_response = 1.

Author: InterLinked1

cami.c

@@ -358,8 +358,11 @@ static void *ami_loop(void *varg)
 							end_of_response = 1;
 						}
 						/* Whether this event is the Response bit or a plain Event, some line (NOT necessarily the 2nd)
-						 * will have an ActionID, if it belongs to a response. */
-						if (strstr(nextevent, "ActionID:")) {
+						 * will have an ActionID, if it belongs to a response.
+						 *
+						 * An edge case here is async Originate actions, which result in an async OriginateResponse later
+						 * with the same action ID. We don't want to get confused and think a response is pending at this point. */
+						if (strstr(nextevent, "ActionID:") && response_pending) {
 							middle_of_response = 1;
 						}
 					}