summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAndreas Eversberg <jolly@eversberg.eu>2013-07-10 08:58:03 +0200
committerHolger Hans Peter Freyther <holger@moiji-mobile.com>2013-08-18 10:32:45 +0200
commita874b8d396a2c883716491ab5ae3a756e7e46e64 (patch)
tree79262a1dc5ff0475fe38fad5d6835ae69a548922
parent66b52c1df840d0b7700df1a641aa5f8f0bcfa253 (diff)
Fix: Handle CM service request on already secured channel correctly
Second part of the previous patch. Log an error message in case we receive a location updating request on an already authenticated channel.
-rw-r--r--openbsc/src/libmsc/gsm_04_08.c5
1 files changed, 5 insertions, 0 deletions
diff --git a/openbsc/src/libmsc/gsm_04_08.c b/openbsc/src/libmsc/gsm_04_08.c
index eea0736..d81dab9 100644
--- a/openbsc/src/libmsc/gsm_04_08.c
+++ b/openbsc/src/libmsc/gsm_04_08.c
@@ -281,6 +281,11 @@ static int _gsm0408_authorize_sec_cb(unsigned int hooknum, unsigned int event,
release_loc_updating_req(conn);
break;
+ case GSM_SECURITY_ALREADY:
+ LOGP(DMM, LOGL_ERROR, "We don't expect LOCATION "
+ "UPDATING after CM SERVICE REQUEST\n");
+ /* fall through */
+
case GSM_SECURITY_NOAVAIL:
case GSM_SECURITY_SUCCEEDED:
/* We're all good */