Wireshark-bugs: [Wireshark-bugs] [Bug 7042] The MSISDN is not seen correctly in GTP packet
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7042
--- Comment #16 from Anders Broman <anders.broman@xxxxxxxxxxxx> 2012-04-10 22:38:06 PDT ---
(In reply to comment #14)
> So, in *other* protocols, such as GTP, how is the + indicated in a TBCD string?
>
> Or is an MSISDN in GTP *always* an international phone number?
3GPP TS 29.060 :
7.7.33 MS International PSTN/ISDN Number (MSISDN)
The MS international ISDN numbers are allocated from the ITU-T Recommendation
E.164 numbering plan, see
3GPP TS 23.003 [2]. The MSISDN is coded according to the contents of
ISDN-AddressString data type defined in
3GPP TS 29.002 [6]. The MSISDN shall be in international format and the "nature
of address indicator" shall indicate
"international number".
3GPP TS 23.003
3.3 Structure of MS international PSTN/ISDN number
(MSISDN)
MS international ISDN numbers are allocated from the ITU-T Recommendation E.164
numbering plan; see also ITU-T
Recommendation E.213.
For GSM/UMTS applications, a National Destination Code is allocated to each
PLMN. In some countries more than
one NDC may be required for each PLMN.
The composition of the MS international ISDN number should be such that it can
be used as a global title address in the
Signalling Connection Control Part (SCCP) for routeing messages to the home
location register of the MS. The country
code (CC) and the national destination code (NDC) will provide such routeing
information. If further routeing
information is required, it should be contained in the first few digits of the
subscriber number (SN).
A sub-address may be appended to an ISDN number for use in call setup and in
supplementary service operations where
an ISDN number is required (see ITU-T Recommendations E.164, clause 11.2 and
X.213 annex A). The sub-address is
transferred to the terminal equipment denoted by the ISDN number.
The maximum length of a sub-address is 20 octets, including one octet to
identify the coding scheme for the
sub-address (see ITU-T Recommendation X.213, annex A). All coding schemes
described in ITU-T Recommendation
X.213, annex A are supported in GSM and UMTS.
3GPP TS 29.002
ISDN-AddressString ::=
AddressString (SIZE (1..maxISDN-AddressLength))
-- This type is used to represent ISDN numbers.
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.
-- b) The following octets representing digits of an address
-- encoded as a TBCD-STRING.
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
