ISUP Address Complete Message Delays: Causes and Common Fixes
When an Australian caller dials a mobile number from Sydney and hears ringing two seconds later, the experience feels seamless. Behind that ring tone is a chain of ISUP messages, and one of the most timing-sensitive is the Address Complete Message. ACM is the signal a destination exchange sends back to the originating switch once it has all the digits it needs. If it arrives late, callers perceive post-dial delay, IVR systems time out, and operators chase phantom faults in interconnect routes.
Across networks run by Telstra, Optus and TPG, ACM timing is monitored against benchmarks of 1.5 to 4 seconds depending on jurisdiction and call type. Engineers troubleshooting complaints from Melbourne or Brisbane look at MTP3 routing, number portability dips, and ISUP variant mismatches between carriers, since most ACM delays originate well before ringing current flows.
The good news is that ACM delays are usually the result of a small set of recurring issues. A structured approach that isolates where the message stalls - in transit, at the destination, or in a database lookup - resolves the bulk of cases without major hardware changes.
ACM in the ISUP Call Flow
ISUP uses a sequence of messages to set up, supervise and clear a voice call between switches. After the IAM (Initial Address Message) leaves the originating exchange, it travels through the SS7 network toward the destination. The destination performs digit analysis, often consults an LNP or HLR database, and finally decides that enough digits have been received to begin alerting. At that point, the destination returns an Address Complete Message, which is the call's green light to provide ringback to the caller.
ACM is therefore a milestone, not the answer signal. It tells the originating side that the called line is being rung, but it does not indicate off-hook. If ACM is delayed, the caller hears nothing - just dead air or carrier announcements - even though the call is progressing normally somewhere downstream.
Common Causes of Address Complete Message Delays
Several distinct problems tend to surface repeatedly in trace captures from Australian carriers. The first is post-dial delay created by overlapping signalling, where the originating switch sends digits in IAM and the destination has to wait for additional information before it can produce ACM. The second is number portability lookup latency, particularly when an LNP dip must cross between networks operated by different LRN providers.
A third category is signalling link congestion. If an MTP3 link set between two exchanges is running above 40 percent utilisation during peak hours, ACM messages queue behind lower-priority traffic. ISUP variant mismatches, where ANSI and ITU-T flavours meet at a gateway without proper conversion, can also stretch ACM timing by forcing extra translation steps.
Finally, misconfigured timers at the destination switch can produce ACM even when digit collection is incomplete, leading to subsequent cut-through delays. Engineers working under the ACCC's regulated interconnection framework often see this where new entrants meet legacy Telstra equipment.
Diagnostic Snapshot of Common ACM Causes
A short table helps narrow the field before launching into trace analysis. Each row maps a typical cause to a recognisable symptom and a representative delay window observed in Australian interconnects. Use it as a first filter, then move into detailed signalling captures once a likely cause has been identified.
| Cause | Observable Symptom | Typical ACM Delay |
|---|---|---|
| Overlap signalling with no overlap receiving | Silence until digit timer expires | 4-7 seconds |
| LNP database dip across networks | Variable silence, then ringback | 2-5 seconds |
| MTP3 link congestion (>40% load) | Delay rises during peak hours | 1-3 seconds |
| ISUP variant mismatch at gateway | Inconsistent behaviour across routes | 2-6 seconds |
| Misconfigured T7 timer | Premature or absent ACM | 1-4 seconds |
Switch-Level Fixes Worth Trying First
Most ACM delay issues can be addressed without redesigning routes. Start by verifying the ISUP variant configuration on both ends of the affected circuit group - Australia largely runs ITU-T variants, but legacy gateways sometimes default to ANSI. Next, check whether overlap sending is enabled at the destination; if not, the originating switch waits for a digit timeout before the call can proceed.
Timer tuning is the next lever. T7 controls the interval between IAM and the receipt of address-complete signalling, while T9 governs how long the destination waits for additional digits. Lowering T7 slightly can reduce perceived delay, and aligning T9 with the actual digit collection profile prevents premature ACM. Engineers should also confirm that the LNP service provider is configured for the shortest available dip, ideally under 800 milliseconds.
Long-Term Network Optimisation
Once immediate fixes are in place, attention shifts to the underlying signalling fabric. Diversifying MTP3 routes between busy exchanges, particularly across the Sydney-Melbourne corridor, smooths out peak-hour congestion. Monitoring tools that capture per-call signalling traces make it easier to spot when ACM latency creeps upward over weeks rather than minutes. Rolling these traces into a regular audit cycle, with thresholds matched to ACMA reporting expectations, keeps the network honest.
A useful habit is to share trace samples between interconnect partners, since a sanitised ACM trace passed from Optus to a smaller provider can resolve disputes that would otherwise take months of back-and-forth.
Engineers in Brisbane who want to broaden their protocol knowledge often pair technical reading with the site's broader catalogue, where resources sit alongside unrelated material such as the Queensland casino guide for those exploring the full range of pages on the domain. The most reliable single step an operations team can take this week is to capture ACM timing on every interconnect trunk for one full business day, then compare the worst-case values against the diagnostic table to identify which of the common causes is in play.
