Signaling Network Management in MTP3: Transfer Prohibited and Allowed
Transfer Prohibited and Transfer Allowed shape MTP3 route management. Signalling Network Management (SNM) exposes the route state behind ISUP and other user-part traffic between switching centres. A prohibition can stop call setup even when the bearer path remains healthy.
A prohibition means that a signalling point cannot accept messages for a named destination, so upstream peers should avoid that path. An allowed indication reports that the route is usable again. Neither signal is a complete outage report: destination scope, cause values, timers and implementation details determine the effect.
Australian operators are managing this as legacy PSTN and ISDN interconnects give way to SIP and IP-based services. SS7 interconnect remains relevant to wholesale call routing, number portability and the 000 emergency service. A bad route state can spread across Telstra, Optus, TPG Telecom and wholesale carriers rather than remain local.
Sparse geography makes resilience harder, particularly on long-hauld paths between Perth and the eastern states. Redundant routes and round-the-clock operations remain essential. Australian engineers call a route “up” or “down” and may ask for “a squiz” when checking recent alarms and counters.
Route Sets and the Meaning of Availability
MTP3 selects a route from an ordered route set for each destination. If the preferred path is unavailable, alternate-route rules may redirect signalling, although continuity or congestion policy can inhibit that rerouting. Route-set state, not physical connectivity alone, is the key operational view.
Transfer Prohibited is not a synonym for a failed link or unavailable signalling point. It identifies an affected destination and a reason for prohibition. Transfer Allowed withdraws or reverses that condition for the same scope. Trace displays may label the messages as TP/TA or TFP/TFA.
For engineers working from packet captures, SS7 training courses can reinforce how MTP3 route sets, timers and procedures fit together before live trace fields are interpreted.
Recognising Transfer Prohibited Conditions
A Transfer Prohibited message commonly follows downstream route loss, congestion controls, administrative blocking or an unreachable destination point. Because MTP3 sits below ISUP, the symptom may be failed call setup, release handling or another user-part transaction rather than loss of speech.
SNM should record each event by adjacent signalling point, route, destination and cause. Correlate it with link alarms, the Signalling Route Set Congestion Test, queue depth and ISUP outcomes. Sustained counts indicate a persistent condition; repeated TP/TA pairs without lasting clearance can reveal a flapping route.
Recovering with Transfer Allowed
Transfer Allowed should be evaluated in sequence. It normally means the formerly prohibited path passed its availability checks and may return to normal selection. Confirm that its scope matches the earlier prohibition, then watch for stable routing rather than trusting the message alone.
Stale route state is a common operational risk. An allowed indication may be lost, delayed or processed after a newer prohibition, while timers and databases temporarily disagree. Reconciliation between the MTP3 state machine, alarm records and controlled test traffic is more dependable.
SNM Visibility Across Australian Interconnects
Australian dashboards should separate TP/TA activity by carrier boundary and geography. Long routes between Perth, Adelaide and the eastern capitals can have different spare capacity and restoration paths, so national averages may hide a problem in one direction. Handover teams should compare state with the route actually selected.
Useful measures include time since the last Transfer Allowed, prohibition duration, route flapping, repeat causes and destinations affected by one adjacent point. The wider SMB research collection provides additional context for cross-checking signalling events against transport and interworking records.
Separating Failure from Congestion
Transfer Prohibited caused by congestion needs a different diagnosis from one caused by failure. Congestion evidence usually includes rising occupancy, queueing, retransmissions or congestion-test activity; route failure normally produces clearer link and route alarms. Cause fields and surrounding events should settle the classification.
The guide on MTP3 congestion diagnostics separates capacity pressure from other route problems. In Australia, operators can also check whether busy-period traffic from wholesale, mobile and fixed-line services concentrates on limited interconnect paths, especially where alternate routing is constrained by policy.
Comparing Prohibited and Allowed States
The key operational differences are:
| Aspect | Transfer Prohibited | Transfer Allowed |
|---|---|---|
| Meaning | Destination path cannot accept traffic | Destination path may carry traffic |
| Routing | Upstream nodes avoid the affected route | Route can return to normal selection |
| Evidence | Cause, route and destination | Clearance and recovery sequence |
| Risk | Call setup failure or misrouting | Stale or premature restoration |
Incident records should capture both messages in sequence. A later allowed indication does not repair an unrelated route, destination or cause, and it should not close an alarm until routing and user-part traffic agree.
Practical indicators and verification checks
Symptoms to correlate
- State: The route entry matches the affected destination and adjacent point.
- Cause: Trace data identifies congestion, failure or administration.
- Evidence: Link alarms and user-part outcomes support the diagnosis.
Checks before closure
- Scope: Any TP and later TA cover the same route and destination.
- Timers: Expiry and retransmission values have settled.
- Service: Controlled ISUP traffic succeeds through the intended path.
Operational Takeaway for Service Continuity
Operationally, a route is not recovered because a console turns green. It is recovered when the prohibition is withdrawn for the correct destination, cause indicators are cleared, and user-part transactions follow the intended path across the carrier interconnect.
The practical takeaway is a scoped, time-bound approach: every Transfer Prohibited is validated against its cause, the matching Transfer Allowed is monitored, and route state, alarms and traffic agree before closure.
