diff options
| author | Harald Welte <laforge@gnumonks.org> | 2012-07-16 13:20:53 +0200 |
|---|---|---|
| committer | Harald Welte <laforge@gnumonks.org> | 2012-07-16 13:20:53 +0200 |
| commit | ae1d0102202ddd3ca58744e5b5ec00f46cc22282 (patch) | |
| tree | d6f184c68a799ecbe7fc27e7a182a0b4536d14d9 | |
| parent | fdf453c0a97841cf238191eef63382b650ffe07f (diff) | |
BSC API: Don't treat a RRLP message as NOTICE event
While generally we should log troly unknown RR messages, we can simply
pass along RRLP messages (which aren't unknown!)
In real networks, the RRLP would probably not end up at the MSC, but
well, sometimes we don't care what real/classic networks do.
| -rw-r--r-- | openbsc/src/libbsc/bsc_api.c | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/openbsc/src/libbsc/bsc_api.c b/openbsc/src/libbsc/bsc_api.c index 361cb3b0c..c00dc579c 100644 --- a/openbsc/src/libbsc/bsc_api.c +++ b/openbsc/src/libbsc/bsc_api.c @@ -577,6 +577,12 @@ static void dispatch_dtap(struct gsm_subscriber_connection *conn, case GSM48_MT_RR_CLSM_CHG: handle_classmark_chg(conn, msg); break; + case GSM48_MT_RR_APP_INFO: + /* Passing RR APP INFO to MSC, not quite + * according to spec */ + if (api->dtap) + api->dtap(conn, link_id, msg); + break; default: /* Normally, a MSC should never receive RR * messages, but we'd rather forward what we |