Comment #10 on issue 3 by [email protected]: Allow mobicents SS7 stack
to be configurable to use 5 or 8 bit SLS
http://code.google.com/p/jss7/issues/detail?id=3
About enum for Mtp3UserPart: we chinese SPS coding has 24-bit pointcodes
but which are incompatible with both ANSI and other ITU-T networks. So we
really need an enum for it.
ANSI point codes use 24-bits (three octets); ITU-T point codes typically
use 14-bits. For this reason, signaling information exchanged between ANSI
and ITU-T
networks must be routed through a gateway STP, protocol converter, or other
signaling point that has both an ANSI and an ITU-T point code. (Note: China
uses 24-bit ITU-T point codes, which are incompatible with both ANSI and
other ITU-T networks). Interaction between ANSI and ITU-T networks is
further complicated by different implementations of higher-level protocols
and
procedures.
An ANSI point code consists of network, cluster, and member octets (e.g.,
245-16-0). An octet is an 8-bit byte that can contain any value between
zero and 255. Telcos with large networks have unique network identifiers
while smaller operators are assigned a unique cluster number within
networks 1 through 4 (e.g., 1-123-9). Network number 0 is not used; network
number 255 is reserved for future use.
ITU-T point codes are pure binary numbers, which may be stated in terms of
zone, area/network,and signaling point identification numbers. For example,
the point
code 5557 (decimal) may be stated as 2-182-5 (binary 010 10110110 101).
Possible Enum values
ANSI
ITU
Japan TTC/DDI
China
Japan NTT