tree f863f04fae781b20565b2af09c89a629edc07039
parent 8cedded88c9a0c4c486f987b818ccba57e96421e
author Holger Hans Peter Freyther <holger@moiji-mobile.com> 1429804241 -0400
committer Holger Hans Peter Freyther <holger@moiji-mobile.com> 1430853320 +0200

sgsn: Handle different levels of QoS

If QoS is only three bytes it does not include the allocation/
retention policy. Otherwise it does. Copy it depending on that.
We should have a macro for the clamping to reduce code duplication.

The insanity does come from the MAP data and this seems to be
the easiest in terms of complexity. It is an array of bytes that
is transported from MAPProxy to the SGSN and then simply forwarded.

The case of more than three bytes is neither unit nor manually
tested so far.