Section: 5.2.3.4 Recall present
Content: In the "recall present" state, the call control entity in the mobile station waits for acceptance of the Recall by the user. Once confirmation is received, the mobile station indicates acceptance of a recall by - sending a SETUP message to its peer entity in the network; - starting Timer T303; and - entering the "call initiated" state and proceeding as described in subclause 5.2.1.1. The MS shall ensure that the contents of the Bearer Capability IE(s) and Supported Codec List IE sent in the SETUP message are the same as the Bearer Capability IE(s) and Supported Codec List IE in the previous CC-ESTABLISHMENT CONFIRMED message related to this Network Initiated MO Call. In the "recall-present" state, if the user of a mobile station is User Determined User Busy then a RELEASE COMPLETE message shall be sent with cause #17 "user busy" In the "recall-present" state. If the user of a mobile station wishes to reject the recall then a RELEASE COMPLETE message shall be sent with cause #21 "call rejected". In either case, the mobile shall release the connection in accordance with subclause 5.4.2 On receipt of the SETUP message in the "recall present" state, the network shall stop timer T334 and proceed as specified in subclause 5.2.1.2. If the call control entity of the network does not receive a SETUP message before the expiry of timer T334, then the network shall send a RELEASE COMPLETE message to the mobile using cause #102 "recovery on timer expiry", release the MM connection, enter the "null" state and shall inform all appropriate entities within the network. Figure 5.7b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ]  Recall acceptance or rejection by user