Adding An End Node Internal Point Code - Tekelec IP7 Secure Gateway Administration Manual

Database Administration Manual - IP7 Secure
Gateway
Adding an Existing Association to an Existing Application Server
SUA Configuration Procedures
Routing key matching the user part specified in the
and with the DPC of the routing key equal to the true point code of the EAGLE 5 ISS (shown in
the rtrv-sid output) - See the
IETF M3UA and SUA Configuration Procedures
For IPSG entities, these entities must be configured in the database.
The internal point code must be in the destination point code table - perform the "Adding a
Destination Point Code" procedure in the Database Administration Manual - SS7 .
An SS7 route to the internal point code - perform the "Adding a Route containing an SS7 DPC"
procedure in the Database Administration Manual - SS7 .
M3UA Linksets -
Procedures
M3UA associations -
Configuration Procedures
Signaling links assigned to the IPSG cards -
IPSG M2PA and M3UA Configuration Procedures

Adding an End Node Internal Point Code

This procedure is used to assign user parts to an internal point code (IPC), and thereby to an end office
node using the ent-rmt-appl command. An internal point code is assigned to remote applications.
Only one IPC value for each network type can be configured. If you are adding an IPC value of the
same network type as an existing IPC (for example, adding an ANSI IPC when the rtrv-rmt-appl
output contains an ANSI IPC), the IPC value must be the same as the existing IPC value.
The ent-rmt-appl command uses these parameters:
:ipc/ipca/ipci/ipcn/ipcn24 – The end node's internal point code can be an ANSI (ipc/ipca),
ITU-I or ITU-I spare (ipci), 14-bit ITU-N or 14-bit ITU-N spare (ipcn), or 24-bit ITU-N (ipcn24)
point code.
Note: The point code value can also be either a private (p- ) or a private spare (ps- ) point code, but
does not have to be a private or private spare point code. Any point code can be a private point code.
Only ITU-I or 14-bit ITU-N point codes can be private spare point codes. The point code value must
be shown in the rtrv-dstn command output.
Note: The EAGLE 5 ISS can contain 14-bit ITU-N point codes or 24-bit ITU-N point codes, but not
both at the same time.
:si – The service indicator value designates which MSU user part is being assigned to a remote
application. Valid values range from 3 to 15.
:ssn – The SCCP subsystem number parameter. This parameter is required if the si=3 parameter is
specified and is not valid for any other si value. If the ssne parameter is also specified, then the ssn
parameter serves as the starting value of a range. Valid values range from 0 to 255.
:ssne – The SCCP subsystem number range end parameter. The ssne value can be specified only if
the si=3 parameter is specified and is not valid for any other si value. This parameter serves as an
910-6278-001 Revision A, January 2012
Adding a Routing Key Containing an Application Server
Adding an IPSG M3UA Linkset
Adding an IPSG M3UA Association
procedure in
Adding an End Node Internal Point Code
.
procedure in IPSG M2PA and M3UA Configuration
procedure in
Adding an IPSG M3UA Signaling Link
End Office Support
IETF M3UA and
procedure
procedure in
IPSG M2PA and M3UA
procedure in
634