Actions
Bug #2994
closedOsmoBTS wrong PAGING TYPE 3 REST OCTETS
Start date:
02/24/2018
Due date:
% Done:
100%
Spec Reference:
Description
When OsmoBTS builds RR PAGING TYPE 3 messages, it messes up generating the P3 rest octets IE, see the below decode:
GSM CCCH - Paging Request Type 3 L2 Pseudo Length .... 0110 = Protocol discriminator: Radio Resources Management messages (0x6) Message Type: Paging Request Type 3 Page Mode .... 0000 = Page Mode: Normal paging (0) Channel Needed ..00 .... = Channel 1: Any channel (0) 00.. .... = Channel 2: Any channel (0) TMSI/P-TMSI - Mobile Identity 1 TMSI/P-TMSI TMSI/P-TMSI - Mobile Identity 2 TMSI/P-TMSI TMSI/P-TMSI - Mobile Identity 3 TMSI/P-TMSI TMSI/P-TMSI - Mobile Identity 4 TMSI/P-TMSI TMSI/P-TMSI Value: 0x60cd1178 P3 Rest Octets L... .... = Channel Needed 3 & 4: Not Present .L.. .... = NLN(PCH): Not Present ..H. .... = Priority 1: Present ...0 00.. = Call priority: no priority applied (0) for Mobile Identity 1 .... ..H. = Priority 2: Present .... ...0 00.. .... = Call priority: no priority applied (0) for Mobile Identity 2 ..L. .... = Priority 3: Not Present ...L .... = Priority 4: Not Present Padding Bits: default padding
Related issues
Actions