Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Comprehensive Guide to IEC 15991-04: Call Interception and Connected Party Services in Private Integrated Networks
Technical insights into the inter-exchange signalling protocol for call interception supplementary services under CAN/CSA-ISO/IEC 15991-04
The standard IEC 15991-04 (adopted as CAN/CSA-ISO/IEC 15991-04) is a crucial component of the Private Integrated Services Network (PISN) standards suite. It defines the inter-exchange signalling protocol for the Call Interception and Interception of Connected Party supplementary services. These services allow authorized users to intercept calls directed to another user or to take over an established connection, respectively. This article provides a technical overview of the standard’s scope, core requirements, implementation considerations, and compliance pathways.
Scope of IEC 15991-04
The standard completes the Stage 3 specification for the Call Interception (CI) and Interception of Connected Party (ICCP) services within a PISN environment operating at the Q reference point (QSIG). It is applicable to private integrated networks in which exchanges (PINXs) interconnect via a signalling protocol based on the generic functional protocol (ISO/IEC 11582). IEC 15991-04 defines the signalling requirements to support these services across both public and private network domains, including interworking with circuit-switched and IP-based bearers.
Note: IEC 15991-04 is identical to the international standard ISO/IEC 15991:2004 and has been adopted by the Standards Council of Canada as CAN/CSA-ISO/IEC 15991-04. It is part of the QSIG family, which enables supplementary service interoperability across multi-vendor PISN networks.
Core Technical Requirements
The protocol is specified using the formal description techniques of ASN.1 and SDL, building on the Remote Operations Service Element (ROSE) and the generic functional protocol (GFP). Key technical elements include defined operations, information element coding, state machines, and timer values.
Protocol Operations
Each supplementary service is realized by a set of operations exchanged between the served PINX and the remote PINX. For Call Interception, the primary operations are CallInterception, CallInterceptionResult, and associated error returns. For Interception of Connected Party, the operations InterceptionOfConnectedParty, IOCPResult, and error procedures are defined. All operations are mapped onto QSIG messages using the framework provided in ISO/IEC 11582.
Implementation Tip: Ensure that the timing parameters (e.g., T-CI for call interception wait) are correctly configured according to Annex A of the standard. Incorrect timer values can lead to premature release or blocking of the service.
| Operation | Direction | Usage |
|---|---|---|
| CallInterception | Originating PINX → Destination PINX | Request interception of a call still in alerting phase |
| CallInterceptionResult | Destination PINX → Originating PINX | Accept or reject the interception request |
| InterceptionOfConnectedParty | Originating PINX → Destination PINX | Request interception of an already connected call |
| IOCPResult | Destination PINX → Originating PINX | Result (success/failure) for connected party interception |
| Error (return) | Both directions | Standard error codes (e.g., invalid service state, not available) |
Messages and Information Elements
The standard extends the basic QSIG message set with service‑specific information elements (IEs), such as the InterceptionInformation IE, which conveys the interception type (CI or ICCP) and the intercepting user’s identity. Coding and semantics for all IEs are provided in Clause 7 and Annex C of the document.
Common Pitfall: The InterceptionInformation IE must be included in the SETUP message for call interception and in the FACILITY message for connected party interception. Omission can cause immediate rejection of the service request.
Implementation and Integration Considerations
Integrating IEC 15991-04 into a PISN environment requires careful attention to interworking with existing supplementary services (e.g., call forwarding, call transfer) and to end‑to‑end compatibility over multimedia bearers. The standard defines interaction rules for coexisting services; for example, when both Call Interception and Call Forwarding Unconditional are active, the interception request shall take precedence if the intercepting user is authorized.
Interworking with External Networks
For calls traversing public ISDN or VoIP gateways, the QSIG signalling may need to be mapped to ISUP- or SIP-based protocols. IEC 15991-04 does not itself define this mapping, but equipment designers should refer to the relevant interworking recommendations (e.g., ITU-T Q.1912.5). The “C” option in the PISN profile field of the calling party number should be set to indicate that call interception information is present.
Benefit: Proper implementation of IEC 15991-04 allows enterprises to centralise call interception services such as interception of calls to generic numbers or supervised transfer of active calls – thereby improving operational efficiency and user productivity.
Compliance and Testing Requirements
Compliance verification for IEC 15991-04 follows the conformance testing methodology defined in ISO/IEC 9646. The standard includes a Protocol Implementation Conformance Statement (PICS) proforma (Annex D) and a set of abstract test cases (Annex E) for both Call Interception and Interception of Connected Party. Equipment suppliers must demonstrate that their QSIG stack correctly implements the mandatory operations and that the service state machines behave as specified.
Conformance Testing Checklist
- Mandatory operations: The PINX must support all required operations for at least one of the two services.
- Timer accuracy: All timers (e.g., T‑CI, T‑IOCP) must be within the tolerances given in Annex A.
- Error handling: The implementation must correctly respond to service‑related errors and must reject unsolicited operations.
- Interoperability: Field trials against at least two reference PINX implementations are recommended before deployment.
Critical: Failing to support the InterceptionNotAllowed error procedure may cause a silent resource leak on the destination PINX. This must be thoroughly tested in all conformance suites.
In addition, Canadian regulatory bodies may require proof of compliance with CAN/CSA‑ISO/IEC 15991‑04 for equipment to be installed in public‑switched or licensed private networks. Manufacturers should include the PICS statement in their technical documentation and conduct periodic regression testing as the QSIG protocols evolve.
Frequently Asked Questions
Q: Is IEC 15991‑04 a Canadian-only standard?
A: No. The base standard is the international ISO/IEC 15991:2004 published jointly by ISO and IEC. Canada has adopted it without modifications as CAN/CSA‑ISO/IEC 15991‑04. Many other countries also use the identical ISO/IEC version.
A: No. The base standard is the international ISO/IEC 15991:2004 published jointly by ISO and IEC. Canada has adopted it without modifications as CAN/CSA‑ISO/IEC 15991‑04. Many other countries also use the identical ISO/IEC version.
Q: What is the difference between Call Interception and Interception of Connected Party?
A: Call Interception (CI) allows a user to intercept a ringing call before it is answered. Interception of Connected Party (ICCP) enables a user to take over an active (already established) call. Each service has its own separate operation set and state machines.
A: Call Interception (CI) allows a user to intercept a ringing call before it is answered. Interception of Connected Party (ICCP) enables a user to take over an active (already established) call. Each service has its own separate operation set and state machines.
Q: Can IEC 15991‑04 be implemented over SIP‑based PISNs?
A: The standard specifies the QSIG protocol, which is typically carried over ISDN D‑channels (Q.931). For SIP networks, the corresponding SIP‑PISN interworking mechanisms (e.g., SIP‑QSIG mapping per RFC 4497) must be used to transport the call interception information elements. The standard does not define a native SIP solution.
A: The standard specifies the QSIG protocol, which is typically carried over ISDN D‑channels (Q.931). For SIP networks, the corresponding SIP‑PISN interworking mechanisms (e.g., SIP‑QSIG mapping per RFC 4497) must be used to transport the call interception information elements. The standard does not define a native SIP solution.
Q: Are there any security implications with call interception services?
A: Yes. Authorization mechanisms are essential. The standard does not specify authentication or encryption; it assumes the network operator implements appropriate access controls to prevent unauthorized use of the interception features. It is recommended to combine the protocol implementation with PINX‑level restrictions.
A: Yes. Authorization mechanisms are essential. The standard does not specify authentication or encryption; it assumes the network operator implements appropriate access controls to prevent unauthorized use of the interception features. It is recommended to combine the protocol implementation with PINX‑level restrictions.
Published: 2026