What are merged requests, looped-request, spiral requests?
A. Merged Requests: If the incoming requests does not contain the To tag and also it does not match any of the present transaction based on the transaction matching rules specified in section 17.2.3 in RFC 3261 (same as above flow chart) and if the From tag, Call ID and Cseq matches any of the present transaction then the request is assumed to be a merged request i.e. the same request has arrived at the UAS more than once, following different paths (most likely due to forking) and in this case the UAS should respond with a 482 Loop detected response.