Calling Line Identity Presentation in ISUP: Provider Choices
Calling Line Identity Presentation (CLIP) allows the destination network and subscriber equipment to display the originating number for an incoming call. In an ISDN User Part (ISUP) call, the relevant identity is carried through signalling messages, then interpreted by switches, gateways, mobile systems, and customer devices.
For Australian operators, CLIP is shaped by more than a single ISUP parameter. Privacy requests, numbering rules, interconnect agreements, fraud controls, emergency services, and IP migration all influence whether the calling line identity is passed, restricted, altered, or withheld.
How CLIP travels through an ISUP call
The originating exchange normally places the caller’s number in the Initial Address Message (IAM). The Calling Party Number parameter includes fields such as the nature of address, numbering plan, address presentation restriction indicator, and screening indicator. These values tell the next network how the number should be interpreted and whether it may be shown to the called party.
Transit exchanges usually relay the information in the IAM or map it into an equivalent SIP identity when traffic crosses a SIGTRAN or softswitch environment. A provider must preserve the number’s meaning during conversion. A formatting error, such as losing the national or international nature-of-address value, can produce an invalid display or cause downstream rejection.
Provider options at the interconnect
A network provider can pass the received CLI transparently when it has confidence in the source and the interconnect contract permits presentation. This is the simplest option, but it still requires checks for valid numbering ranges, correct digit length, and consistency between the identity and the access service.
The provider can also screen, normalise, replace, or suppress the identity. A business may present an approved switchboard number rather than an individual extension, while a private caller may request restriction. For technical readers building a strong foundation in SS7 training, the important distinction is between transporting a value and authorising its presentation.
Restriction, screening and substitution
The Address Presentation Restriction Indicator is central to privacy handling. When the originating subscriber requests CLIR, the destination should generally receive an indication that the number is restricted rather than an exposed CLI. Depending on national rules and service design, the network may display “private number”, “withheld”, or no usable identity.
The Screening Indicator provides a related but different signal. It can indicate whether the number was provided by the user, verified by the network, or inserted by another source. A provider may accept a customer-provided CLI for legitimate enterprise use, yet mark it as screened or replace it with a network-assigned number where caller ID spoofing risk is high.
| Provider decision | Typical use | Main control required |
|---|---|---|
| Pass the CLI | Verified subscriber and trusted interconnect | Validate numbering and format |
| Present a restricted result | Customer requests privacy | Preserve restriction indicators |
| Substitute a service number | Contact centres and hosted PBX systems | Authorise the presented number |
| Suppress the identity | Invalid, unauthorised, or risky CLI | Apply policy consistently |
| Translate between ISUP and SIP | IP interconnect or softswitch routing | Map identity and privacy semantics |
Australian numbering and routing realities
In Australia, a domestic geographic number normally uses the familiar eight-digit format with an area code beginning in 02, 03, 07, or 08. A caller from Sydney, Melbourne, Brisbane, or Perth may therefore appear differently after national, international, or mobile translation. Telstra, Optus, and other carriers must ensure that the displayed number remains meaningful across their respective routing domains.
The NBN has increased the use of hosted voice, SIP trunks, and cloud contact centres, so a call may cross several IP and legacy signalling boundaries before reaching a handset. Providers also need a carefully controlled exception process for Triple Zero traffic, where reliable calling identity and location-related information can be operationally significant.
CLIP security and trust boundaries
Caller ID is useful evidence, not absolute proof of identity. Spoofed numbers can support scams, impersonation, and misleading callback requests. Screening at the ingress edge, trusted-number databases, anomaly detection, and restrictions on customer-supplied CLI values help reduce this exposure.
A sensible design treats every interconnect as a trust boundary. An unexpected identity crossing that boundary should be checked rather than accepted automatically; the same boundary principle appears in practical fence-jumping guidance, even though the operational subject is different. The useful idea is containment: define what may cross, verify it, and record exceptions.
Interworking with SIGTRAN and SIP
MTP3 and SCCP provide the signalling transport framework around SS7, while SIGTRAN carries SS7 user parts over IP. In an M3UA deployment, the ISUP Calling Party Number still needs to survive application-server and signalling-gateway processing. Failure can occur when a gateway rewrites digits, discards restriction status, or maps a national number to the wrong global form.
SIP interworking adds another layer. P-Asserted-Identity, Privacy headers, and From values do not always have identical trust or privacy meanings. An Australian provider should document which identity is authoritative, how restricted calls are mapped, and what happens when a SIP peer supplies a number outside its allocated range.
Operational policy and testing
A provider policy should define accepted number ranges, permitted enterprise presentation numbers, privacy treatment, screening results, and behaviour for malformed IAMs. It should also specify whether transit traffic is passed unchanged or subjected to validation. These rules belong in signalling gateways, softswitches, service logic, and monitoring platforms rather than in informal operational notes.
Testing should cover domestic fixed-line calls, mobile calls, international traffic, private callers, hosted PBX numbers, diverted calls, and emergency-service scenarios. Useful training and reference material can sit alongside practical telecom products when engineers need to connect protocol theory with deployed equipment.
What operators should remember
CLIP in ISUP is a provider-controlled presentation decision built on signalling data. Passing a calling number is appropriate only when its format, source, authorisation, and privacy status are understood. Restriction and screening indicators must retain their meaning across SS7, SIGTRAN, and SIP boundaries.
The key lesson for Australian networks is simple: validate the identity, preserve privacy, document substitutions, and treat every interconnect as a controlled trust boundary. A displayed number should be useful to the recipient without becoming an unverified claim about who is calling.
