Attention is currently required from: daniel, laforge, neels.

Hello Jenkins Builder, daniel, laforge,

I'd like you to reexamine a change. Please visit

https://gerrit.osmocom.org/c/osmo-iuh/+/37393?usp=email

to look at the new patch set (#3).

The following approvals got outdated and were removed: Code-Review+1 by daniel, Code-Review+1 by laforge, Verified+1 by Jenkins Builder

Change subject: support RAB Assignment Response 'unsuccessfulOutcome' ......................................................................

support RAB Assignment Response 'unsuccessfulOutcome'

Already present before this patch: - decoding 'successfulOutcome' in cn_ranap_rx_successful_msg_co() - decoding 'outcome' in cn_ranap_rx_outcome_msg_co()

In this patch, add: - decoding 'unsuccessfulOutcome' in cn_ranap_rx_unsuccessful_msg_co()

Context:

A RAB Assignment response is indicated as 'successfulOutcome' or 'unsuccessfulOutcome' or 'outcome'. 3GPP TS 25.413 specifies RAB Assignment as a "Class 3 Elementary Procedure", but doesn't seem to specify which of these three 'outcome' types to use for Class 3. In the field we've seen 'successfulOutcome' and 'outcome'.

A RAB Assignment response may actually contain responses for multiple RABs, and each of them can have a separate success or failure status. It seems that 'outcome' might be intended for such mixed responses.

Either one is fine, because the included RAB Assignment Response IEs are always in the same format, regardless of the outcome type.

Change-Id: Ifec566a98cb6141d27b9e5e33d5a78f8b1530658 --- M src/ranap_common_cn.c 1 file changed, 6 insertions(+), 0 deletions(-)

git pull ssh://gerrit.osmocom.org:29418/osmo-iuh refs/changes/93/37393/3