Section: 5.5.3.2.2 STATUS message with compatible state
Content: A STATUS message may be received indicating a compatible call state but containing one of the following causes: # 95 "semantically incorrect message"; or # 96 "invalid mandatory information"; or # 97 "message type non-existent or not implemented"; or # 98 "message type not compatible with protocol state"; or # 99 "information element non-existent or not implemented"; or # 100 "conditional IE error". This indicates that the transmitter of the STATUS message was unable to accept some information sent by the recipient of the STATUS message. This allow the recipient to retransmit some or all of the information. Other actions are possible and are implementation dependent; they may include releasing the call. In the case the MS receives a STATUS message with the cause #100 due to the presence of a Repeat Indicator with the value "service change and fallback" in a SETUP message, it may then resend a new SETUP message with a single BC-IE (no Repeat Indicator is included). The actual behaviour is dependent on the implementation. In the case the network receives a STATUS message with the cause #100 due to the presence of a Repeat Indicator with the value "service change and fallback" in a SETUP message, it shall then resend a new SETUP message, with either the BC-IE of the preferred service or the speech BC-IE (fallback to speech) as the only BC (no Repeat Indicator is included). The preferred behaviour is decided by configuration.