ttcn3
/
titan.ProtocolModules.BSSMAP
10
0
Fork 1
Code Issues Pull Requests Projects Releases Wiki Activity

Fix message type of UPLINK SEIZED COMMAND 

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.

Related: OS#6087
Change-Id: I61ff2532a4d6eb3aa1ed96cdeb1f2c848ef4447e
This commit is contained in:
Andreas Eversberg 2023-07-12 11:09:29 +02:00
parent e03923ec75
commit 814c5d786a
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/BSSAP_Types.ttcn
View File

@ -2612,12 +2612,12 @@ type record PDU_BSSMAP_UplinkReleaseCommand
// UPLINK SEIZED COMMAND- 48.008 subclause 3.2.1.63
type record PDU_BSSMAP_UplinkSeizedCommand
{
OCT1 messageType, // H'4E
OCT1 messageType, // H'4D
BSSMAP_IE_Cause cause,
BSSMAP_IE_TalkerPriority talkerPriority optional,
BSSMAP_IE_EmergencySetIndication emergencySetIndication optional,
BSSMAP_IE_TalkerIdentity talkerIdentity optional
} with { variant "PRESENCE (messageType = '4E'O)" }
} with { variant "PRESENCE (messageType = '4D'O)" }