diff options
author | Neels Hofmeyr <neels@hofmeyr.de> | 2019-04-01 22:24:33 +0200 |
---|---|---|
committer | Harald Welte <laforge@gnumonks.org> | 2019-04-13 21:38:58 +0000 |
commit | 9838c9070fb8147418e65348e71147a52f64320b (patch) | |
tree | f1d9c54235f01cb5a47f73a3eb3ca082a729f3b9 /include/osmocom/crypt | |
parent | 0ee798a0172a009cec4fb27c427b8f1d66fca749 (diff) |
GSUP: add Message Class IE
osmo-msc and osmo-hlr have distinct subsystems handling incoming GSUP messages.
So far we decide entirely by message type which code path should handle a GSUP
message. Thus no GSUP message type may be re-used across subsystems.
If we add a GSUP message to indicate a routing error, it would have to be a
distinct message type for subscriber management, another one for SMS, another
one for USSD...
To allow introducing common message types, introduce a GSUP Message Class IE.
In the presence of this IE, GSUP handlers can trivially direct a received
message to the right code path. If it is missing, handlers can fall back to the
previous switch(message_type) method.
Change-Id: Ic397a9f2c4a7224e47cab944c72e75ca5592efef
Diffstat (limited to 'include/osmocom/crypt')
0 files changed, 0 insertions, 0 deletions