Project

General

Profile

Actions

Bug #2868

closed

OsmoMSC doesn't interpret CM Service Type

Added by laforge about 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
01/24/2018
Due date:
% Done:

100%

Resolution:
Spec Reference:

Description

When we receive a CM Service Request, OsmoMSC should eventually verify what kind of service it is the phone requests, and whether we support that service.

TS 24.008 10.5.3.3 lists the following service types:

Service type (octet 1)
Bits
4 3 2 1
0 0 0 1 Mobile originating call establishment or packet mode connection establishment
0 0 1 0 Emergency call establishment
0 1 0 0 Short message service
1 0 0 0 Supplementary service activation
1 0 0 1 Voice group call establishment
1 0 1 0 Voice broadcast call establishment
1 0 1 1 Location Services
All other values are reserved.

We should reject anything that's not 0001, 0010, 0100, 1000, as we don't support those other services. An appropriate error cause as per Section 4.5.1.1 is "Service option not supported".

Actions #1

Updated by laforge about 6 years ago

  • Status changed from New to In Progress
  • Assignee changed from 4368 to laforge
  • % Done changed from 0 to 80

https://gerrit.osmocom.org/6011

TTCN-3 tests: MSC_Tests.TC_cm_serv_req_{vgcs,vbs,lcs}_reject

Actions #2

Updated by laforge almost 6 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 80 to 100

patch merged.

Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)