INAP and the Architecture Behind Modern Call Control Services
The Intelligent Network Application Part, widely known as INAP, sits at the core of legacy and hybrid telephone infrastructures worldwide. It defines how service logic and switching equipment converse across the SS7 signalling stack, allowing operators to deploy advanced call features without rewriting switch code. For engineers in Sydney, Melbourne, and other Australian hubs, understanding INAP remains essential even as the National Broadband Network reshapes local access.
INAP works through TCAP messages riding on SCCP, which means it inherits the reliability and addressing strengths of the signalling backbone it shares with MAP and ISUP. Studying it reveals how a single call from a handset in Brisbane can trigger a remote SCP in another state, returning routing decisions and tones in milliseconds.
Origins and standardised role of INAP
INAP emerged from the ITU-T Q.12xx series of recommendations during the 1990s, paralleling similar work from ETSI and ANSI. The goal was to separate service logic from switching hardware, so providers could roll out features like freephone, premium rate, and personal numbering without touching every exchange. The Australian carrier market, historically dominated by Telstra and Optus, adopted these standards to power services on the PSTN before the NBN rollout.
In practical terms, INAP packages operations that a Service Switching Point sends to a Service Control Point and the responses coming back. Each operation corresponds to a stage in call setup, supervision, or release, which gives the network a level of programmability that plain ISUP cannot offer.
INAP in the SS7 protocol stack
The protocol hierarchy places INAP on top of TCAP, which in turn runs over SCCP, MTP3, and MTP2. This positioning gives it transactional, connectionless messaging with global title addressing, so a call originating in Perth can reach a service node in Adelaide without dedicated circuits. Australian inter-capital signalling relies heavily on this global title translation.
Compared with ISUP, which mostly handles trunk and bearer setup, INAP focuses on service invocation. Where ISUP messages direct circuits between exchanges, INAP queries ask policy questions such as whether to allow a call, how to bill it, or which number to translate a dialled string into.
Core components of an Intelligent Network
The Intelligent Network architecture rests on three building blocks. Service Switching Points detect trigger conditions and suspend normal call processing while they consult the SCP. Service Control Points hold service logic and return instructions. Intelligent Peripherals provide tones, prompts, and speech resources for services that need them.
In Australia, Telstra historically embedded SCPs in its major switching centres across Sydney and Melbourne, while smaller operators often relied on shared platforms. This division made INAP traffic patterns visible across inter-capital routes during peak hours, particularly around business districts where service volumes spiked.
Trigger Detection Points and call flows
Call processing in an IN-equipped exchange proceeds through Trigger Detection Points, or TDPs, which are pre-defined checkpoints in the call state machine. When a TDP fires, the SSP launches an INAP dialogue, sending an InitialDP message to the SCP. The SCP responds with operations such as Connect, Continue, or ReleaseCall, which steer the call toward its destination.
A simple example illustrates the logic: a caller in Hobart dials a 13 number for a national service centre. The TDP for the 13 prefix fires, the SSP sends InitialDP to the SCP, and the SCP returns a Connect with a geographic number in Sydney. The call completes without the caller noticing any complexity.
| Protocol | Standardised by | Primary domain | Message transport |
|---|---|---|---|
| INAP | ITU-T (Q.12xx) | Fixed PSTN call control | TCAP over SCCP |
| CAP | ETSI (TS 29.078) | GSM and 3G mobile | TCAP over SCCP or M3UA |
| WIN | ANSI/TIA | CDMA networks | TCAP over SCCP |
| CS-1 and CS-2 | ITU-T | Multi-domain IN | TCAP over SCCP |
INAP and CAP share the same TCAP foundation, while WIN targets North American CDMA carriers. CS-1 and CS-2 extend the same principles to broadband and multi-domain scenarios.
INAP amid Australia's NBN migration
Australia's shift toward the NBN has reduced the reliance on legacy PSTN switches, but INAP still runs in many access gateways. VoIP interconnects between NBN providers and the legacy SS7 core use SIGTRAN, which transports TCAP and INAP over SCTP. Engineers in Adelaide and Perth who maintain these gateways must still read INAP traces when troubleshooting.
The ACMA framework, anchored in the Telecommunications Act 1997 and the Telecommunications (Consumer Protection) Code, requires providers to preserve service quality during migration. INAP-based features such as number translation and conditional forwarding have to remain functional as copper is retired, which keeps the protocol relevant in operational runbooks. For a comparative view on signalling systems in other regions, the global telecom reference provides useful background reading.
Practical recommendations for working with INAP
- Capture full bidirectional traces including SCCP and TCAP layers to confirm global title resolution.
- Map every Trigger Detection Point in your switch configuration to the corresponding service before any code change.
- Test INAP dialogues against a lab SCP before touching production traffic on busy Sydney to Melbourne routes.
- Keep a record of vendor-specific extensions, since some Australian operators have added private operations.
- Cross-check billing records against INAP operations with TCAP transaction identifiers when investigating disputes.
- Validate continuity across SIGTRAN transitions, especially when M3UA replaces MTP3 during NBN upgrades.
- Document dialogue lifetimes, because unclosed TCAP transactions can cause memory pressure on older SCPs.
If you maintain SS7 infrastructure today, the most concrete step is to schedule a one-day audit of your SIGTRAN gateways before the next scheduled NBN cutover. Detailed guides for tracing TCAP, INAP, and M3UA traffic are available through SS7 training solutions.
