A.4.4.4 Spare and Private Point Code Subtype Prefixes
The Spare Point Code Support feature and the Internal Point Code Support feature provide optional point code subtype prefixes. The Spare Point Code feature must be enabled before a point code subtype prefix can be specified for a point code.
Note:
The SEAS interface does not support point code subtype prefixes.The values p-, s-, and ps- are valid point code subtype prefixes. The dash- separates the point code subtype prefix from the remainder of the point code. The prefixes are displayed in lower case. The syntax for the remainder of the point code remains the same.
The Spare Point Code prefix (s-) applies only to ITU-I and ITU-N point code domains (ITU-N24 point codes do not support the Spare Point Code prefix), to allows the EAGLE to fully support ITU National and International Spare Point Codes. Table A-2 lists the commands that support the Spare Point Code subtype prefix.
The Private (Internal) Point Code prefix (p-) applies to all point code domain types (including ITU-N24 point codes), to allow messages destined to the End Office Node to be routed from the inbound LIM to the outbound IPGWx. Table A-3 lists the commands that support the Private Point Code subtype prefix.
The subtype prefix ps- can be specified when the point code parameter supports both the spare and private point code prefixes.
Table A-2 Commands that support the Spare Point Code Prefix
Command | Description | Applicable Point Code Parameters |
---|---|---|
|
Alarm |
dpci and dpcn |
|
Application Route Key |
dpci and dpcn; opci and opcn |
|
Concerned Signaling Point Code |
pci and pcn |
|
Destination |
spci and spcn; dpci and dpcn; and Alias combinations. |
|
Enter Trace |
dpci and dpcn; opci and opcn |
|
GSM MAP Screening |
npci and npcn |
|
GSM Options |
ppsmspci1, ppsmspci2, ppsmspcn1, ppsmspcn2 |
|
GSM Short Message Services OP-Code |
pci and pcn |
|
Global Title Translation/Global Title Address |
pci and pcn |
|
Linkset |
apci and apcn |
|
Mated Application |
pci and pcn; mpci and mpcn |
|
Mated Relay Node |
pci and pcn; pci1 and pcn1; pci2 and pcn2; pci3 and pcn3; pci4 and pcn4 |
|
Network Appearance |
type=ituis, type=ituns |
|
Pass Commands |
Syntax for routing keys |
|
Remote Application |
ipci and ipcn |
|
Route |
dpci and dpcn |
|
Gateway Screening Allowed Affected Point Code |
pcst and pctype |
|
Gateway Screening Blocked Destination Point Code |
pcst and pctype |
|
Gateway Screening Blocked Origination Point Code |
pcst and pctype |
|
Gateway Screening Called Party (CDPA PC Destination) Point Code |
pcst and pctype |
|
Gateway Screening Calling Party (Origination) Point Code |
pcst and pctype |
|
Gateway Screening Affected Destination (Concerned) Point Code |
pcst and pctype |
|
Gateway Screening Destination Point Code |
pcst and pctype |
|
Gateway Screening Origination Point Code |
pcst and pctype |
|
Site ID |
True pci and pcn; cpci and cpcn; ncpci and ncpcn. |
|
Secondary Point Code |
spci and spcn |
Table A-3 Commands that support the Private Point Code Prefix
Command | Description | Applicable Point Code Parameters |
---|---|---|
|
Destination |
spci and spcn; dpc, dpca, dpci,, and dpcn Does not apply to Aliases |
|
Linkset |
If ipgwapc=yes, apc, apcn, apci, and apcn |
|
Global Title Translation |
pc, pca, pci, and pcn |
|
Destination alarm inhibit |
dpc, dpca, dpci, and dpcn |
|
Report Cluster Status |
dpc and dpca |
|
Report Destination Status |
dpc, dpca, dpci, and dpcn |
|
Remote Application |
ipc, ipca, ipci, and ipcn |
|
Restore Destination |
dpc and dpca |
|
Route |
dpc, dpca, dpci, and dpcn |