1. Database Administration - IP7 User's Guide
  2. IPSG M2PA and M3UA Configuration Procedures
  3. Adding IPSG Components

Adding IPSG Components

This section describes how to configure the components necessary to establish connections using IPSG M2PA associations on IPSG signaling links, and IPSG M3UA associations on IPSG signaling links.

The configuration of these connections consists of these items.

  1. Configure the IPSG card with the Adding an IPSG Card procedure.
  2. Configure the required destination point codes - see Chapter 2, “Configuring Destination Tables,” in Database Administration - SS7 User's Guide.
  3. Configure the required IPSG linksets - perform the Adding an IPSG M2PA Linkset or the Adding an IPSG M3UA Linkset procedures.
  4. IP addresses must be assigned to the IPSG card configured in step 1 by performing the Configuring an IP Link procedure. There are other IP link parameters that are assigned to the IPSG card when the IPSG card is configured. Default values are assigned to these parameters when the IPSG card is configured. These values can be displayed by the rtrv-ip-lnk command. These values can be changed by performing the Configuring an IP Link procedure.
  5. Local IP hosts, assigned to the IP addresses assigned to step 4, must be configured in the database by performing the Adding an IP Host procedure. Verify the hosts with the rtrv-ip-host command. This establishes a relationship between the IPSG card related information and the association related information.
  6. When the IPSG cards are added to the database in step 1, there are IP parameters that control the IP stack that are assigned default values. These parameter values can be displayed by the rtrv-ip-card command. These values can be changed by performing the Configuring an IP Card procedure.
  7. Static IP routes provide more flexibility in selecting the path to the remote destination and reduces the dependence on default routers. Static IP routes are provisioned by performing the Adding an IP Route procedure.
  8. IPSG Associations specify a connection between a local host/TCP port and a remote host/TCP port. Two types of IPSG associations can be provisioned: M2PA and M3UA. Associations that are assigned to IPSG M2PA signaling links must be IPSG M2PA associations. Associations that are assigned to IPSG M3UA signaling links must be IPSG M3UA associations. The IPSG M2PA association is configured by performing the Adding an IPSG M2PA Association procedure. The IPSG M3UA association is configured by performing the Adding an IPSG M3UA Association procedure. Associations can be assigned to IPLIMx or IPGWx signaling links also. These associations are configured by performing the Adding an M2PA Association or Adding an M3UA or SUA Associationprocedures. A number of fields in the association cannot be configured with the Adding an IPSG M2PA Association or Adding an IPSG M3UA Association procedures and are set to default values. The values of these fields can be displayed using the rtrv-assoc command after the Adding an IPSG M2PA Association or Adding an IPSG M3UA Association procedures are performed. These values can be changed by performing the Changing the Attributes of an IPSG Association procedure.
  9. There are two versions of IPSG M2PA associations, RFC and Draft 6, that can be configured in the database. When an IPSG M2PA association is added to the database with the Adding an IPSG M2PA Association procedure, the association is configured as an RFCM2PA association. The RFC version of M2PA timer set 1 is also assigned to the association when the IPSG M2PA association is added to the database.

    There are two different versions, RFC and Draft 6, of M2PA timer sets that can be assigned to IPSG M2PA associations. Each version of the M2PA timer sets contains 20 timer sets. The values of these timer sets can be changed with the Changing an M2PA Timer Set procedure.

    The version of the IPSG M2PA association and the M2PA timer set assigned to the association can be changed with Changing the Attributes of an IPSG Association procedure. The M2PA version of the association determines the version of the M2PA timer set that is assigned to the association. For example, if M2PA timer set 3 is assigned to the IPSG M2PA association, and the association is an RFC M2PA association, the RFC version of M2PA timer set 3 is used with the association. If M2PA timer set 7 is assigned to the IPSG M2PA association, and the association is a Draft 6 M2PA association, the Draft 6 version of M2PA timer set 7 is used with the association.

  10. When an IPSG M3UA association is added to the database, UA parameter set 10 is assigned to the association. There are 10 UA parameter sets that can be assigned to an association, but the UA parameter set assignment can be changed, using the Changing the Attributes of an IPSG Association procedure. The values assigned to each UA parameter set can be changed, except for UA parameter set 10, using the Changing a UA Parameter Set procedure.
  11. Configure the IPSG signaling links with either the Adding an IPSG M2PA Linkset or Adding an IPSG M3UA Signaling Link procedures. If the addition of these signaling links will exceed the current number of signaling links the EAGLE is allowed to have, the Enabling the Large System # Links Controlled Feature procedure will have to be performed to increase the quantity of signaling links.
  12. Configure the required routes - see Chapter 3, “SS7 Configuration,” in Database Administration - SS7 User's Guide.
  13. An internal point code can be provisioned to provide routing to an IP end office node. Configure the internal point codes by performing the Adding an End Node Internal Point Codeprocedure.
  14. The network appearance field identifies the SS7 network context for the message, for the purpose of logically separating the signaling traffic between the SGP (signaling gateway process) and the application server over a common SCTP (stream control transmission protocol) association. This field is contained in the DATA, DUNA, DAVA, DRST, DAUD, SCON, and DUPU messages. Network appearances are configured by performing the Adding a Network Appearance procedure.
  15. The EAGLE processes messages with a service information field (SIF) that is 272 bytes or smaller. The Large MSU Support for IP Signaling feature allows the EAGLE to process messages with a service indicator value of 6 to 15 and with a SIF that is larger than 272 bytes. Perform the Activating the Large MSU Support for IP Signaling Feature procedure to enable and turn on the Large MSU Support for IP Signaling feature.