Configuring a Point Code Table in a Signaling Gateway
A point code table is the routing reference that allows a signaling gateway to identify where SS7 messages should go. It connects destination point codes with linksets, SCTP associations, M3UA application servers, or other transport paths. A correct configuration helps the gateway process MTP3, ISUP, SCCP, and related signaling traffic without ambiguity.
Configuring a point code table in a signaling gateway requires more than entering numeric values. The administrator must match the signaling plan, point code standard, network indicator, routing context, and operational state of every connected node. A small mismatch can cause unavailable routes, rejected messages, or incorrect call handling.
The work is especially important in hybrid networks. A gateway may translate between TDM-based SS7 links and SIGTRAN transport over IP while supporting mobile switching centers, signal transfer points, media gateways, and application servers.
Understand The Point Code Role
A point code uniquely identifies a signaling node within a signaling network. In an SS7 message, the originating point code identifies the sender, while the destination point code identifies the intended recipient. The gateway uses these values to select a signaling link, linkset, route, or IP-based association.
Point code formats vary by national or regional standard. ITU-T networks commonly use 14-bit codes, ANSI networks use 24-bit codes, and other variants may be present in specialized deployments. The table must use the format expected by the connected network rather than relying on a generic decimal representation.
The network indicator also matters. It distinguishes international, national, spare, or other signaling domains. A destination point code that is numerically correct can still fail if the network indicator or point code type does not match the incoming message.
Collect The Signaling Parameters
Before editing the gateway, document the local point code, adjacent signaling points, remote destinations, linkset names, and permitted traffic types. Include the originating point code and destination point code values used by each peer. For SIGTRAN, record the SCTP address pair, port, association name, and M3UA routing context where applicable.
The gateway should also reflect the actual network topology. A signal transfer point may be reachable through two linksets, while a service control point may be available through only one. If a destination is reached through an STP, configure the STP as the adjacent signaling point and define the final destination in the route set when the platform supports layered routing.
Modern IP networks introduce additional dependencies. A gateway carrying signaling toward an IMS core may need coordination with M3UA application servers and routing keys. The wider shift from circuit-switched signaling is outlined in this guide to LTE signaling evolution, which provides useful context for such mixed architectures.
Build The Point Code Entries
Create the local signaling point definition first. Assign the gateway’s own point code, point code variant, network indicator, and signaling mode. If the platform separates an SS7 local point code from an M3UA server identity, configure both and confirm how the vendor maps them.
Next, create remote entries for each destination. A typical record includes the destination point code, peer type, linkset or association, route priority, availability state, and optional subsystem information. Avoid assigning the same point code to two unrelated remote nodes unless the design explicitly uses replicated or load-sharing signaling points.
The following fields illustrate a vendor-neutral structure:
| Field | Purpose | Typical Value |
|---|---|---|
| Local point code | Identifies the gateway | 2-145-3 |
| Destination point code | Identifies a remote node | 2-210-4 |
| Network indicator | Selects the signaling domain | National |
| Transport path | Selects linkset or SIGTRAN peer | LS-MSC-01 |
| Route priority | Determines preferred path | Primary |
| Backup path | Provides failover | LS-MSC-02 |
| Status | Controls operational use | Enabled |
Point code notation must be entered exactly as the vendor expects. Some systems accept decimal values, while others require dashed components or hexadecimal notation. Confirm that the displayed value corresponds to the same binary point code used by neighboring STPs and signaling nodes.
Associate Routes With Transport
A point code entry is useful only when it is bound to an operational transport path. For traditional SS7, associate the destination with a signaling link or linkset and verify that MTP2 links reach the in-service state. For SIGTRAN, associate it with the correct SCTP association, M3UA application server process, or routing context.
Routing keys may include destination point code, originating point code, service indicator, and network appearance. When multiple application servers share traffic, confirm whether the gateway uses load sharing, active-standby operation, or broadcast distribution. An incorrect routing key can make the association appear healthy while messages are discarded at the application layer.
MTP3 route selection should also account for linkset priority and congestion. Define alternate paths only when they lead to a valid signaling peer. A backup route pointing to the wrong STP can create loops, duplicate delivery, or a misleading appearance of redundancy.
Validate Routing And Timers
Test the configuration with controlled signaling traffic. Send an ISUP message toward a known destination and inspect the routing label, originating point code, destination point code, service indicator, and selected link or association. For SCCP traffic, verify that global title translation and subsystem routing do not conflict with the point code route.
Review MTP3 management messages such as transfer prohibited, transfer allowed, transfer controlled, and signaling point unavailable. These messages reveal whether the gateway and adjacent nodes agree about route status. Also inspect SCTP and M3UA events, including association establishment, ASP activation, routing-context acceptance, and peer state changes.
Timers should be checked after the route is functional. T7, T1, and other protocol timers influence call setup and recovery behavior, but changing them will not repair an incorrect point code. Capture traces during both normal delivery and failover so that route selection and restoration can be verified.
Apply Security And Operational Controls
Signaling gateways should accept traffic only from authorized peers. Use firewall rules, restricted SCTP addresses, secure management access, and signaling screening policies where supported. Validate originating point codes and reject unexpected combinations of point code, service indicator, or network indicator.
Maintain change records for every point code and route update. Record the previous value, new value, reason, implementation time, and rollback procedure. A staged activation is safer than enabling many destinations simultaneously, particularly in a live PSTN, mobile, or IMS interconnection.
Use these practices when preparing the configuration:
- Keep a single approved inventory of local and remote point codes.
- Match every route to a documented linkset or SIGTRAN association.
- Test primary and backup paths independently before production use.
- Monitor MTP3, SCCP, M3UA, and SCTP alarms after each change.
- Preserve configuration backups and a tested rollback file.
Move From Configuration To Verification
A point code table should be treated as part of the signaling design, not as an isolated gateway setting. Its values must agree with STPs, service platforms, mobile core nodes, and IP transport peers. Regular audits can identify duplicate codes, inactive routes, obsolete associations, and inconsistent network indicators before they affect subscribers.
Start with one controlled destination, verify message traces and management states, then expand the route set according to the approved topology. Apply the same discipline to failover testing and configuration backups so that the gateway remains predictable during maintenance or network faults.
Use these principles to review your signaling gateway, correct mismatched entries, and validate SS7 or SIGTRAN routing in a controlled test window.
