Project

General

Profile

Bug #2883

GSUP encoding of MSISDN is wrong

Added by laforge about 2 years ago. Updated about 1 month ago.

Status:
New
Priority:
Normal
Assignee:
sysmocom
Category:
-
Target version:
-
Start date:
01/26/2018
Due date:
% Done:

0%

Resolution:

Description

The GSUP documentation is quite clear on this: The element is encoded as in 09.02 and 04.08. This includes the TON (type of number) and NPI (numbering plan information). For some unknown reason, the current OsmoMSC implementation diverges from both our own specification as well as 3GPP. Instead, the coding currently implemented seems to be:
  • GSUP IE Tag + Length
  • another Length byte
  • Hex digits

Related issues

Related to OsmoMSC - Bug #4324: SMS-over-GSUP: inconsistent SM-RP DA/OA codingResolved12/13/2019

Related to Cellular Network Infrastructure - Support #4333: GSUP binary compatibility: add GSUP protocol version IE?Feedback12/16/2019

History

#1 Updated by laforge over 1 year ago

  • Priority changed from Urgent to Normal

#2 Updated by fixeria about 1 month ago

  • Related to Bug #4324: SMS-over-GSUP: inconsistent SM-RP DA/OA coding added

#3 Updated by fixeria about 1 month ago

From 3GPP TS 129.002, section 17.7.8 "Common data types":

AddressString ::= OCTET STRING (SIZE (1..maxAddressLength))
-- This type is used to represent a number for addressing
-- purposes. It is composed of
--   a) one octet for nature of address, and numbering plan
--      indicator.
--   b) digits of an address encoded as TBCD-String.

-- a) The first octet includes a one bit extension indicator, a
--    3 bits nature of address indicator and a 4 bits numbering
--    plan indicator, encoded as follows:

-- bit 8: 1  (no extension)

-- bits 765: nature of address indicator
--   000  unknown
--   001  international number
--   010  national significant number
--   011  network specific number
--   100  subscriber number
--   101  reserved
--   110  abbreviated number
--   111  reserved for extension

-- bits 4321: numbering plan indicator
--   0000  unknown
--   0001  ISDN/Telephony Numbering Plan (Rec ITU-T E.164)
--   0010  spare
--   0011  data numbering plan (ITU-T Rec X.121)
--   0100  telex numbering plan (ITU-T Rec F.69)
--   0101  spare
--   0110  land mobile numbering plan (ITU-T Rec E.212)
--   0111  spare
--   1000  national numbering plan
--   1001  private numbering plan
--   1111  reserved for extension
--   all other values are reserved.

#4 Updated by fixeria about 1 month ago

Here is an example of an alphanumeric address:

TP-Originating-Address - (Facebook)
   Length: 14 address digits
   1... .... = Extension: No extension
   .101 .... = Type of number: Alphanumeric (coded according to 3GPP TS 23.038 GSM 7-bit default alphabet) (5)
   .... 0000 = Numbering plan: Unknown (0)
   TP-OA Digits: Osmocom

#5 Updated by neels about 1 month ago

  • Related to Support #4333: GSUP binary compatibility: add GSUP protocol version IE? added

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)