Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 11582-04: Inter-Exchange Signalling Protocol for Call Transfer in Private Integrated Services Networks
A Comprehensive Technical Guide to the ISO/IEC Standard for Call Transfer Supplementary Service in PISN
The IEC 11582-04 standard (also adopted as CAN/CSA-ISO/IEC 11582-04) defines the inter-exchange signalling protocol for the call transfer supplementary service within Private Integrated Services Networks (PISN). This joint ISO/IEC standard is essential for ensuring seamless communication and interoperability among different PISN nodes when transferring active calls. It specifies the protocol procedures, message formats, state transitions, and error handling required to support call transfer operations in a multi-vendor environment.
Scope of IEC 11582-04
The scope of IEC 11582-04 is limited to the inter-exchange signalling aspects of the call transfer supplementary service within PISN. It applies to exchanges (i.e., private signalling nodes) interconnected by a private signalling network using the QSIG (Q-signalling) protocol suite. The standard addresses two variants of call transfer:
- Explicit Call Transfer (ECT) – where a user explicitly initiates the transfer by invoking a supplementary service request.
- Single Step Call Transfer – where the transfer is performed automatically as part of a call building or clearing procedure.
The standard does not cover the terminal equipment or network internal implementations; it focuses strictly on the signalling messages exchanged between PISN exchanges to coordinate the transfer of a call from one party to another.
Technical Requirements
Service Description
The call transfer supplementary service allows a served user to transfer an established call (active or held) to a third user. The served user may also be the transferring user or the user being transferred. The standard defines the phases and operations for initiating, performing, and clearing the transfer. The key states involve the transferring user (TP), the transferred user (TD), and the new target user (TU).
Signalling Protocol and Message Flow
The protocol is based on the Generic Functional Protocol for the support of supplementary services (ISO/IEC 11582 is built upon that framework). It uses the Remote Operations Service Element (ROSE) over the signalling transport. The call transfer operation is modeled as a series of operations invoked by the transferring exchange toward the remote exchange.
| Operation (Message) | Direction | Purpose |
|---|---|---|
| CallTransferRequest | TP → Destination | Initiate the transfer of the active call |
| CallTransferSetup | Destination → New Target | Request to set up a new call to the target user |
| CallTransferActivate | Destination → TP | Acknowledge transfer start; optionally modify call path |
| CallTransferComplete | Destination → TP | Indicate successful transfer and release of original connections |
| CallTransferReject | Any → Requestor | Return error or failure cause (e.g., busy, invalid state) |
Protocol Data Units (PDUs) and Encoding
All PDUs are encoded using ASN.1 (Abstract Syntax Notation One) with the basic encoding rules. The standard specifies the exact information elements (e.g., calling party number, connected number, transfer cause) that shall be included in each message. Mandatory fields ensure call state integrity, while optional elements allow for vendor-specific enhancements without breaking interoperability.
Tip: When implementing the protocol, pay close attention to the state machine definitions for the transferring and transfer recipient exchanges. The standard includes detailed state transition diagrams that are essential for avoiding race conditions and protocol deadlocks.
Implementation Highlights
Integration with Existing PISN Infrastructures
IEC 11582-04 is designed to work seamlessly with other QSIG supplementary services (e.g., call diversion, conference calling) and with basic call control (ISO/IEC 11571). In practice, an exchange that supports call transfer must coordinate the release of the original call segment and the establishment of a new path between the transferred and target parties. This requires careful resource management and signalling synchronization.
Interoperability Considerations
Interoperability testing between different manufacturers’ equipment is critical. The standard defines conformance criteria, but variations in timer settings (e.g., T–TransferRequest, T–CallTransferSetup) can lead to failures. It is recommended to implement the optional Compatibility Information Element to diagnose mismatches in capabilities.
Warning: In networks with mixed TDM and IP infrastructure, the protocol must be carried over the underlying bearer channel. Ensure that your QSIG over IP implementation (RFC 4492 or similar) correctly maps the call transfer operations and does not drop critical information elements during encapsulation.
Compliance and Certification
Testing and Conformance
Conformance testing according to ISO/IEC 11582-04 requires validation of the protocol state machine, PDU encoding, and correct handling of error conditions. Test laboratories often use test suites developed by ETSI (European Telecommunications Standards Institute) or TTCN-3 (Testing and Test Control Notation version 3) to simulate both user and network roles. Certification programs (e.g., the CSTA certification platform) may also include this standard as part of PISN interoperability testing.
Regulatory Acceptance
While IEC 11582-04 is primarily a voluntary international standard, regulatory bodies in many jurisdictions require compliance with relevant PISN signalling standards to validate network interoperability for emergency services and lawful interception. In regions that adopt the CAN/CSA-ISO/IEC 11582-04 version (e.g., Canada), compliance is often mandatory for public safety-grade private networks.
Success: Standardizing on IEC 11582-04 ensures that call transfer services operate reliably across multi-vendor PISN environments, reducing integration costs and improving end-user service continuity.
Danger: Non-compliance with the standard’s state machine and timer requirements can result in call transfer failures, dropped calls, or resource leakage. In critical sectors such as airport operations or emergency dispatch, such failures may have severe operational consequences.
Frequently Asked Questions
Q: What is the difference between IEC 11582-04 and the original ISO/IEC 11582:2004?
A: IEC 11582-04 is the Canadian adoption (CAN/CSA) of ISO/IEC 11582:2004. While the technical content is identical, the Canadian version may include a national foreword and minor editorial changes to align with regional standards practices. The signalling protocol itself remains fully equivalent.
A: IEC 11582-04 is the Canadian adoption (CAN/CSA) of ISO/IEC 11582:2004. While the technical content is identical, the Canadian version may include a national foreword and minor editorial changes to align with regional standards practices. The signalling protocol itself remains fully equivalent.
Q: Does IEC 11582-04 support call transfer over IP networks?
A: The standard is transport independent; it specifies the signalling operations and encoding at the application layer. For IP-based PISN, the QSIG messages are typically carried over TCP/IP using the QSIG over IP framework (e.g., RFC 4492 or T.234). The protocol operates identically whether the underlying transport is TDM or IP, as long as the reliability and sequence integrity guarantees are met.
A: The standard is transport independent; it specifies the signalling operations and encoding at the application layer. For IP-based PISN, the QSIG messages are typically carried over TCP/IP using the QSIG over IP framework (e.g., RFC 4492 or T.234). The protocol operates identically whether the underlying transport is TDM or IP, as long as the reliability and sequence integrity guarantees are met.
Q: What are the typical implementation challenges?
A: Common challenges include maintaining exact state synchronization between the two exchanges, particularly during network failures or timeouts. Implementing the optional timer variations correctly and handling simultaneous transfer requests (conflicting transfers) require careful design. Rigorous conformance testing and mutual agreements on optional features greatly reduce interoperability issues.
A: Common challenges include maintaining exact state synchronization between the two exchanges, particularly during network failures or timeouts. Implementing the optional timer variations correctly and handling simultaneous transfer requests (conflicting transfers) require careful design. Rigorous conformance testing and mutual agreements on optional features greatly reduce interoperability issues.
Q: How does this standard relate to other PISN supplementary services?
A: IEC 11582-04 is part of the QSIG supplementary service suite and interacts closely with basic call control (ISO/IEC 11571) and services such as call diversion (ISO/IEC 13863) and conference calling (ISO/IEC 11572). It is designed to allow multiple supplementary services to be active on the same call, provided the protocol operations are properly sequenced.
A: IEC 11582-04 is part of the QSIG supplementary service suite and interacts closely with basic call control (ISO/IEC 11571) and services such as call diversion (ISO/IEC 13863) and conference calling (ISO/IEC 11572). It is designed to allow multiple supplementary services to be active on the same call, provided the protocol operations are properly sequenced.
Last reviewed: 2026