ISUP Bearer Capability Negotiation Across Voice And Data Calls
Bearer capability negotiation determines what kind of service a circuit-switched call can support. In an SS7 network, the originating exchange signals the requested bearer and teleservice characteristics, while downstream switches assess whether those requirements can be preserved across the route.
For voice calls, the process usually concerns speech, 3.1 kHz audio, or unrestricted digital transmission. Data calls can require a transparent 64 kbit/s path, rate adaptation, or compatibility with an interworking device. The result depends on ISUP parameters, trunk configuration, national variants, and the capabilities of connected networks.
Understanding this exchange is essential when troubleshooting call setup, modem failures, fax compatibility, codec conversions, or rejected international traffic. It also provides a useful bridge between traditional PSTN architecture and IP-based signaling environments.
Why Bearer Capability Matters
Bearer capability describes the transport service requested for the call rather than the application alone. A speech call needs suitable voice handling, while a data service may require bit transparency and protection from voice compression or echo processing.
The idea developed alongside ISDN and the wider evolution of SS7. Engineers studying SS7 history can see how signaling moved from basic call control toward richer service descriptions and interworking functions.
If a network treats a data call as ordinary speech, it may activate echo cancellers, voice activity detection, or compression. Those processes can corrupt modem tones and fax signals. Conversely, carrying every call as unrestricted digital traffic may waste resources or conflict with tariff, routing, or regulatory rules.
Information Carried In ISUP
The Initial Address Message is the main vehicle for originating call characteristics. Its User Service Information can describe the requested user service, while the Transmission Medium Requirement indicates the desired transmission medium, such as speech, 3.1 kHz audio, or unrestricted digital information.
Other fields help switches make a consistent decision. The Nature of Connection Indicators can signal satellite use or continuity-check requirements, and the Forward Call Indicators carry information about ISDN access, end-to-end methods, and interworking conditions. Bearer details may also be influenced by access-side Q.931 information before they are mapped into ISUP.
The exact parameter set depends on the ISUP variant, such as ITU-T, ANSI, or a national profile. A trace should therefore be read against the applicable specification rather than interpreted from a generic message decoder alone.
How Exchanges Reach Agreement
ISUP does not normally perform negotiation in the same offer-and-answer style associated with SIP. The originating side sends a capability request in the IAM, and the terminating exchange either accepts the call, applies a compatible treatment, invokes interworking, or rejects the setup.
Address complete and answer messages confirm progress through call establishment, but they do not always restate every bearer attribute. The selected path is shaped by trunk capabilities, translation data, and the terminating subscriber or service platform. A mismatch may result in a cause value such as bearer capability not implemented or service unavailable.
| Call requirement | Typical ISUP indication | Network treatment | Common failure |
|---|---|---|---|
| Speech | Speech bearer or speech-related TMR | Voice switching and echo control | No speech path or incorrect interworking |
| 3.1 kHz audio | 3.1 kHz audio indication | Audio-band path for modem or fax tones | Compression or incompatible gateway |
| Transparent data | Unrestricted digital information | Bit-transparent circuit | Rejection by voice-only trunk |
| Rate-adapted data | User service and rate information | Adaptation equipment or digital access | Wrong rate or framing |
| Mixed or converted service | Interworking indicators | Media conversion or gateway processing | Capability lost across a boundary |
A successful call setup therefore does not prove that the end-to-end bearer is suitable. Verification should continue through answer supervision, media testing, and, where relevant, data-layer validation.
Voice Call Behavior
Speech calls are generally the most broadly supported bearer type. Switches can apply echo suppression, comfort-noise generation, gain control, and other voice treatments without affecting ordinary conversation. However, these functions still need to match the bearer indication and the network’s media policy.
The 3.1 kHz audio category is distinct from a narrow speech service. It is commonly associated with fax, modem, and older data applications that use the voice frequency band. A gateway that sees this indication should avoid processing designed specifically for compressed speech.
Interworking can change the practical result. An ISUP call crossing an ISUP-to-SIP gateway may be mapped to a media type and codec policy, while a gateway connected to an analog line may have limited control over what happens after call completion.
Data And Interworking Cases
Unrestricted digital information is intended for a transparent digital connection. It is useful for circuit-switched data, leased-style services, and certain ISDN applications, but it requires every relevant segment to support the requested transmission mode.
Rate adaptation introduces additional dependencies. The access network, exchange, signaling gateway, and terminal adapter must agree on speed, framing, and synchronization. If one switch downgrades the service to speech or 3.1 kHz audio, the call may connect while the application fails.
Modern networks often convert these services into SIP, RTP, or specialized media sessions. During that conversion, ISUP bearer indicators should be mapped deliberately. A generic voice profile can produce a completed call with unusable data, making packet captures and ISUP traces important parts of fault isolation.
Engineering Checks For Reliable Negotiation
Operational teams should correlate signaling, trunk configuration, and media behavior instead of relying on a single cause code. Useful checks include:
- Compare IAM User Service Information and Transmission Medium Requirement values with the originating access request.
- Confirm that every trunk group and signaling gateway supports the requested bearer category.
- Check whether echo cancellers, codecs, tone detectors, or transcoding are enabled on data-capable paths.
- Review interworking indicators and release causes at each network boundary.
- Correlate call setup with timer expiry, continuity checks, and delayed responses using resources on SS7 timers.
Timer analysis matters because a capability problem can be masked by a separate signaling failure. An IAM may be correct while an ACM or ANM is delayed, causing the originator to release the call before media testing begins.
A disciplined test plan should include speech, fax, modem, unrestricted digital, and gateway-to-gateway scenarios. Capture the signaling at both ends, record the negotiated or mapped media treatment, and compare the observed path with the service profile.
Build this capability analysis into SS7 training, trace review, and network acceptance testing so that voice and data services receive the bearer treatment they require. Clear parameter mapping and end-to-end verification can prevent silent degradation between legacy circuit networks and modern telecommunications platforms.
