| commit | 2cafc4b30910f244e610e4cf75f72ba360df6ace | [log] [tgz] |
|---|---|---|
| author | Harald Welte <laforge@gnumonks.org> | Fri Dec 24 13:06:11 2010 +0100 |
| committer | Harald Welte <laforge@gnumonks.org> | Fri Dec 24 15:42:22 2010 +0100 |
| tree | ebad59bc7665d956b617a0c9185a926649a35d05 | |
| parent | 3a3c277b70df3a09b20fa1f985b29445783959b1 [diff] |
BSC API: Make 'Got data in non active state' message as LOGL_INFO LOGL_ERROR will make this message shpw up in everey default log config. However, as it seems, this is commonly observed in case a MS still sends a MS STATUS (in respons to the MM INFO) at the end of a location area update. It might be best to actually change the channel release procedure to make sure we can still pass such 'late' data to the MSC until the time the Layer2 has been completely released.