Bug #6087
closed
Wrong message type for UPLINK SEIZED COMMAND in BSSAP_Types.ttcn
Added by jolly 10 months ago.
Updated 7 months ago.
Description
The depositroy "https://gitea.osmocom.org/ttcn3/titan.ProtocolModules.BSSMAP" includes a file "src/branch/master/src/BSSAP_Types.ttcn" that defines the messages between MSC and BSS. The UPLINK SEIZED COMMAND, as defines in "type record PDU_BSSMAP_UplinkSeizedCommand" has wrong message type. It is '4E'O, but it must be '4D'O. I verified it against the TS 48.008. 4E'O is used for CHANGE CIRCUIT message.
Files
- Status changed from New to Feedback
- Assignee set to laforge
- Status changed from Feedback to New
- Assignee changed from laforge to jolly
for the osmocom.org repository (as interim fix until upstream fixes it), you can also log into gitea.osmocom.org, create a fork and submit your patch as PR.
- Status changed from New to In Progress
- % Done changed from 0 to 30
upstream patch was merged 2 months ago. Please update the issue status here, thanks.
- Status changed from In Progress to Resolved
- % Done changed from 30 to 100
- Status changed from Resolved to Closed
The fix is already merged at eclipse.org. Our TTCN3 tests depend on that fix already.
Also available in: Atom
PDF
