Section: 5.2.3.2 CC-Establishment present
Content: In the "CC establishment present" state, the mobile station, upon receipt of the CC-ESTABLISHMENT message, shall stop timer T332. The CC-ESTABLISHMENT message contains information which the mobile station shall use for the subsequent SETUP message (if any) related to this CC-ESTABLISHMENT. The CC-ESTABLISHMENT message shall contain the Setup Container IE. If no CC-ESTABLISHMENT message is received by the call control entity of the mobile station before the expiry of timer T332, then the mobile station shall initiate clearing procedures towards the network using a RELEASE COMPLETE message with cause #102 "recovery on timer expiry" and proceed in accordance with subclause 5.4.2. Upon receipt of a CC-ESTABLISHMENT message the mobile station shall perform checks on the Setup Container IE in order to align the contained information with the mobile's present capabilities and configuration. The "recall alignment procedure" is defined later on in this subclause. If the recall alignment procedure has succeeded, the call control entity of the Mobile Station shall: - form and store the SETUP message for sending later in the "Recall present" state, - acknowledge the CC-ESTABLISHMENT message with a CC-ESTABLISHMENT CONFIRMED message, - start timer T335, and - enter the "CC-establishment confirmed" state. Exception: A busy mobile station which has successfully performed the recall alignment procedure shall respond with a CC-ESTABLISHMENT CONFIRMED message with cause #17 "user busy", and proceed as stated above. For speech calls the mobile station shall indicate all codecs that it supports for UTRAN in the Supported Codec List information element of the CC-ESTABLISHMENT CONFIRMED message. Codecs for GERAN shall be indicated in the Bearer Capability information element. Additionally, if the mobile station supports codecs for GERAN and UTRAN, it shall indicate the codecs for GERAN also in the Supported Codec List information element. A mobile station, for which the recall alignment procedure failed, shall respond with a RELEASE COMPLETE message in accordance with subclause 5.4.2 with the appropriate cause code as indicated in the description of the recall alignment procedure. The SETUP message is constructed from the Setup Container IE received in the CC ESTABLISHMENT MESSAGE. The mobile station shall assume that the Setup Container IE contains an entire SETUP message with the exception of the Protocol Discriminator, Transaction ID and Message Type elements. The mobile station may assume that the contents of the Setup Container IE are the same as were sent from the subscriber in a previous SETUP message of the mobile originating call establishment attempt. The mobile station shall copy the Setup Container to the SETUP message and not modify the contents except as defined in the recall alignment procedure and as defined in exceptions below. The mobile station shall not add other Information Elements to the end of the SETUP message. Exceptions: Bearer Capability IE(s), HLC IE(s) and LLC IE(s) (including Repeat Indicator(s), if there are 2 bearer capabilities), and the Supported Codec List IE require handling as described in the recall alignment procedure below. If the CC Capabilities in the Setup Container IE is different to that supported by the mobile station, the mobile station shall modify the CC Capabilities in the SETUP message to indicate the true capabilities of the mobile station. Facility IE(s) and SS Version IE(s) require handling as described in the recall alignment procedure. Stream Identifier IE requires handling as described in the recall alignment procedure. If no response to the CC-ESTABLISHMENT message is received by the call control entity of the network before the expiry of timer T333, then the network shall initiate clearing procedures towards the called mobile station using a RELEASE COMPLETE message with cause #102 "recovery on timer expiry" and inform all appropriate entities within the network, proceeding in accordance with subclause 5.4.2. Figure 5.7a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ]  Call initiation and possible subsequent responses.