Bug #2903
closedOsmoBSC forwards unknown RR message to MSC, rather than sending RR STATUS
100%
Description
According to TS 44.018 Section 8.4, has a clear rule as to how the network side should behave in case of unknown RR message type.
... if the network receives an RR message with message type not defined for the PD or not implemented by the receiver, it shall ignore the message except that it should return a status message (RR STATUS) with cause #97 "message type non-existent or not implemented".
In any case, it's quite clear that RR terminates at the BSC, and the MSC never deals with it. Forwarding it might be a nice hack for OsmoMSC, but I'm not sure we want to test how other MSCs behave if sent such messages.
So we should send RR STATUS with cause #97 and not forward to MSC.
There's BSC_Tests.TC_err_84_unknown_msg for this.
Updated by laforge about 6 years ago
- Status changed from New to Resolved
- Assignee changed from 4368 to laforge
- % Done changed from 0 to 100
Change-Id I0a4d311f6939a4fcee59129daa18da4a2ab510ae by pmaier stopped the forwarding via SCCP to the MSC (but misses a reference to this ticket or any update to this ticket)
https://gerrit.osmocom.org/7358 sends the RR STATUS and fixes the TTCN test case.
