Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Optimizing PISN Call Transfer with IEC 13871-97: Protocol Requirements and Compliance
An in-depth technical analysis of the inter-exchange signalling protocol for call transfer supplementary service in Private Integrated Services Networks
1. Scope of IEC 13871-97
IEC 13871-97, adopted as CAN/CSA-ISO/IEC 13871-97, defines the inter-exchange signalling protocol for the Call Transfer supplementary service within Private Integrated Services Networks (PISN). This standard is part of the ISO/IEC 13870-series and builds on the signalling framework defined by ISO/IEC 11582 (QSIG). It specifies the protocol between two Private Integrated Services Network Exchanges (PINX) over the Q reference point to support call transfer operations.
Scope Emphasis: The standard applies exclusively to the signalling layer—not to end-user station features or terminal equipment. It ensures consistent interworking between multi-vendor PISN nodes for transferring established calls from one party to another.
Call transfer allows a user (the transferor) to transfer an existing call (the held call) to another user (the transferee), then release from the call. The protocol covers both the initiation of transfer using the Call Transfer Initiate and Call Transfer Complete procedures, as well as error handling and exceptional sequences (e.g., network congestion, invalid states).
IEC 13871-97 is fully aligned with the stage 1 and stage 2 descriptions for Call Transfer (ISO/IEC 13870 and ISO/IEC 13872) and conforms to the generic functional procedures of ISO/IEC 11582. It is applicable to PISN environments supporting basic circuit-switched calls and may be extended for IP-based PISN emulation (as later refined in subsequent revisions).
2. Technical Requirements
2.1 Protocol Stack & Reference Model
The protocol operates at the Q reference point between PINXs. It uses the QSIG signalling system at layer 3 (network layer) of the OSI model, with underlying layer 2 (Q.921) and layer 1 (ISDN S/T interfaces). The call transfer supplementary service messages are carried within D-channel LAPD frames using the standard message and information element structures defined in ISO/IEC 11582.
Implementation Tip: Always ensure that the embedded QSIG stack correctly encodes the supplementary service control (CT) protocol discriminator and that the redirectingNumber and connectedNumber information elements are formatted per ISO/IEC 11801 and applicable national variants.
2.2 Message Types and Functional Definitions
The standard defines several new QSIG messages, grouped by functional capability:
| Message Name | Abbreviation | Direction | Purpose |
|---|---|---|---|
| Call Transfer Initiate | CTI | Transferor PINX → Transferee PINX | Request transfer of an existing call to a third party |
| Call Transfer Complete | CTCP | Transferee PINX → Transferor PINX | Indicate successful transfer and release of transferor |
| Call Transfer Reject | CTRJ | Transferee PINX → Transferor PINX | Reject transfer (e.g., invalid state, resource unavailable) |
| Call Transfer Failure | CTFL | Transferor PINX → Transferee PINX | Notify failure to complete transfer after successful initiation |
2.3 Information Elements and Parameters
Each message carries mandatory and optional information elements defined in the standard. The most critical include:
- Transfer Identification – index linking the original call with the transfer request.
- Calling/Called Party Numbers – used for routing the transferred leg.
- Redirection Number – address of the transferee.
- Hold/Retrieve Indicators – manage the state of the held call before and after transfer.
- Location Information – optionally conveys the transferor’s identity for billing/logging.
Common Implementation Pitfall: Many vendors misinterpret the Hold Timer parameter. IEC 13871-97 requires that the transferring PINX must not release the bridge connection until the CTCP message is received; premature release may cause calls to be dropped.
2.4 Call Transfer Procedures (Normative)
The standard defines three primary use cases:
- Blind Transfer – Transferor connects the new party without waiting for answer; the transferor releases immediately.
- Assured Transfer – Transferor stays on line until the transferee answers, then completes the transfer and releases.
- Supervised Transfer – Transferor remains engaged (if allowed) or releases after the transfer, depending on supplementary features.
Each case defines specific sequences of CTI, CTCP, or CTRI messages along with timeout constraints (e.g., CTI response timer default 30 s).
3. Implementation Highlights
Effective deployment of IEC 13871-97 requires careful attention to:
- Interoperability – Conformance with the base QSIG core (ISO/IEC 11582) is mandatory; otherwise, basic call handling fails.
- Timer Management – Implement all timers (CT response, hold recapture timer) as specified in annexes; deviations may cause premature call clearing.
- Table 2: Key Timer Defaults
| Timer | Default Value (seconds) | Trigger |
|---|---|---|
| T_CT_RESP | 30 | After sending CTI message |
| T_HOLD_RECAPTURE | 60 | After held call begins waiting for transfer |
| T_BLIND_TIMEOUT | 6 | Blind transfer alert indication |
Best Practice: For multi-vendor environments, perform conformance testing using a standardized PICS proforma (Protocol Implementation Conformance Statement) as defined in ISO/IEC 13871-97 annex A. This helps identify mismatches in information element coding and message sequencing.
Software Updates: Many legacy PISN switches can be upgraded to support this standard through firmware patches that add the supplementary service message handlers and state machines. Care must be taken to update all PINXs in the network before enabling the service.
4. Compliance and Testing Considerations
To claim compliance with IEC 13871-97, a system must:
- Implement all mandatory messages (CTI, CTCP, CTRI) and optional messages (CTFL) as specified.
- Support both blind and assured transfer procedures.
- Include the full set of mandatory information elements for each message.
- Conform to the QSIG overview standard (ISO/IEC 11582) and the PISN call control protocol (ISO/IEC 11572).
- Pass the abstract test suite defined in ISO/IEC 13871-97 annex B (or later revisions) for static and dynamic conformance.
Warning – Non-Compliance Risk: Failing to correctly implement the ‘Transferor release’ procedure can lead to unwanted billing charges or call abandonment. In networks with revenue assurance systems, such issues can result in significant penalty fees from regulators.
Testing can be performed with dedicated PISN conformance testers (e.g., protocol analyzers supporting QSIG CT) or through emulation of a PINX pair. Special attention should be given to fault scenarios such as simultaneous transfer requests, resource overload, and interoperability with older PINXs that implement proprietary early-version transfer protocols.
Certification Programs: Some national bodies (e.g., CSA in Canada) offer certification marks for products that successfully pass a recognized conformance test. For global deployment, manufacturers often submit to third-party laboratories recognized by the PISN Forum or similar organisations.
Frequently Asked Questions
Q: What is the difference between IEC 13871-97 and the earlier ISO/IEC 13871:1995?
A: IEC 13871-97 is the identical adoption; the 1997 version includes minor corrections to message formats and clarifications on the blind transfer procedure. No functional changes were introduced – it remains compatible with the 1995 edition.
A: IEC 13871-97 is the identical adoption; the 1997 version includes minor corrections to message formats and clarifications on the blind transfer procedure. No functional changes were introduced – it remains compatible with the 1995 edition.
Q: Can IEC 13871-97 be used in an IP-based PISN (VoIP)?
A: The standard was designed for circuit-switched ISDN at the Q reference point. However, its message semantics are often mapped to SIP or H.323 in modern IP-PBX environments via gateways that translate QSIG CT to SIP REFER messages. The core call transfer logic remains identical.
A: The standard was designed for circuit-switched ISDN at the Q reference point. However, its message semantics are often mapped to SIP or H.323 in modern IP-PBX environments via gateways that translate QSIG CT to SIP REFER messages. The core call transfer logic remains identical.
Q: Is there a withdrawal date for this standard?
A: As of 2026, IEC 13871-97 is still current but has been stabilized. Many later revisions (2005, 2010) exist that add enhancements like trunking optimization. For new deployments, the latest edition is recommended, but existing networks may continue relying on the 1997 version if no new features are required.
A: As of 2026, IEC 13871-97 is still current but has been stabilized. Many later revisions (2005, 2010) exist that add enhancements like trunking optimization. For new deployments, the latest edition is recommended, but existing networks may continue relying on the 1997 version if no new features are required.
Q: What testing tools support IEC 13871-97 conformance?
A: Several commercial protocol analyzers (e.g., Tektronix, Spirent, and JDSU) include dedicated QSIG CT test packages. Additionally, open-source libraries like QSIGTrace can decode the message flows. Always verify that the test suite implements the exact PICS defined in the standard.
A: Several commercial protocol analyzers (e.g., Tektronix, Spirent, and JDSU) include dedicated QSIG CT test packages. Additionally, open-source libraries like QSIGTrace can decode the message flows. Always verify that the test suite implements the exact PICS defined in the standard.
– Technical Standards Review, 2026