tree 9ab21b516abb5c77d4b6cde9ed77b772baa54c2b
parent 21c423353cd99c63e9abf3d77df811bd745349cd
author Vadim Yanitskiy <axilirator@gmail.com> 1543432657 +0700
committer Vadim Yanitskiy <axilirator@gmail.com> 1543502569 +0700

library/GSUP_Types.ttcn: fix IE order in PROC_SS_ERROR templates

In general, the order of IEs in a GSUP message doesn't matter.
Despite libosmocore's GSUP API encodes IEs in a fixed order,
it is capable to decode them in any arbitary order.

Meanwhile, in the current TTCN-3 definitions (i.e. templates)
the order makes a difference, because the 'GSUP_IEs' type is
a record, that according to the TTCN-3 documentation represents
an *ordered* sequence of elements.

Let's reorder the IEs of both t{r|s}_GSUP_PROC_SS_ERR templates
in a way that is used by the libosmocore's GSUP encoder.

This correction doesn't affect successful test case executions,
because we don't test possible problematic situations yet. But
if something went wrong on the HLR side (i.e. SUT), the matching
statements wouldn't match the PROC_SS_ERR message correctly
and continue to wait until the guard timer is expired.

Change-Id: I5eb2314f6a9ab0e9fc5e836390414cec6e1a12db