If all request fragments are received, the server MUST reply with a WORKING packet. No further processing is required.
When a call is dispatched:
If the call is secure, ask the security provider to verify or decrypt the received packets, as appropriate, follow the processing information specified in section 126.96.36.199.1.1. If an error occurs, send a REJECT to the client, change the call state to STATE_COMPLETE, remove the call from the activity, and update the lowest-allowed-sequence of the activity. The call is finished.
Dispatch to the application stub.
After the application stub completes successfully, check whether a later call sequence has already been dispatched on this activity. If so, and Overlapped in the server call is false, skip further processing of this sequence.
If the [maybe] flag (as defined in [C706] sections 12.5.2 and 188.8.131.52) is set, no reply is needed. Change the Call State to STATE_COMPLETE, remove the call from the activity, and update the lowest-allowed-sequence of the activity. The call is finished.
Set the Call State to STATE_SEND_FRAGS, and send one or more response fragments to the client.