Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
CAN/CSA-ISO/IEC TR 14475-04: Signalling Protocol for Call Independent Supplementary Services in Private Integrated Services Networks
A comprehensive technical review of the Canadian adoption of ISO/IEC TR 14475:2004 covering scope, protocol architecture, implementation, and compliance
1. Scope and Applicability
The CAN/CSA-ISO/IEC TR 14475-04 standard is the Canadian adoption of the International Technical Report ISO/IEC TR 14475:2004, entitled “Information technology — Telecommunications and information exchange between systems — Private Integrated Services Network — Inter-exchange signalling protocol — Call independent supplementary services.” It defines the signalling protocol required to support call independent supplementary services (CISS) within a Private Integrated Services Network (PISN).
Call independent supplementary services are those that can be invoked, operated, and terminated without being associated with a specific call. Examples include message waiting indication, call interception, and terminal location registration. The standard specifies how such services are signalled across the Q reference point between Private Integrated services Network eXchanges (PINX) using the QSIG protocol family.
Tip: CAN/CSA-ISO/IEC TR 14475-04 is identical to ISO/IEC TR 14475:2004. It serves as a Technical Report, providing informative guidance and recommended practices rather than normative requirements, though it is frequently referenced in procurement specifications for private telecommunications equipment.
2. Technical Requirements and Protocol Architecture
2.1 Protocol Stack Model
The standard follows the layered architecture of the Integrated Services Digital Network (ISDN) model. The CISS protocol operates at the network layer (Layer 3) of the signalling channel, utilizing the existing QSIG infrastructure. The key layers involved are:
- Physical Layer: Typically based on E1/T1 or ISDN basic/primary rate interfaces.
- Data Link Layer: Q.921 (LAPD) for reliable frame transfer.
- Network Layer: Q.931-based messages extended for private network signalling.
- Application Layer: Generic functional protocol (GFP) for supplementary service control.
2.2 Message Structure
All CISS messages use the standard QSIG message format with a protocol discriminator, call reference, message type, and information elements. The message types specific to call independent supplementary services are encapsulated within the QSIG FACILITY message when interworking with basic call services, or they may use dedicated message types for pure CISS transactions.
| Message Name | Direction | Function |
|---|---|---|
| CISS_SETUP | Requesting PINX → Remote PINX | Initiates a CISS transaction, identifies the supplementary service and parameters. |
| CISS_CONNECT | Remote PINX → Requesting PINX | Indicates successful acceptance of the requested service. |
| CISS_RELEASE | Bidirectional | Terminates the CISS transaction and releases associated resources. |
| CISS_PROCEEDING | Remote → Requesting | Acknowledges receipt and indicates that the request is being processed. |
| CISS_REJECT | Remote → Requesting | Rejects the service request with a cause code (e.g., service not subscribed). |
2.3 Information Elements
The standard mandates specific information elements (IEs) for carrying service identifiers, operation codes, and user data. The most critical IE is the Supplementary Service Identifier, which uniquely identifies the call independent service being invoked. Additional IEs provide parameters such as timeout values, facility information, and error diagnostics.
Warning: Incorrect encoding of the Supplementary Service Identifier IE can lead to misinterpretation of the service type by the remote PINX. Implementers must verify that all service codes follow the registration scheme defined in the companion standard ISO/IEC 11582.
3. Implementation Highlights
3.1 Integration with Existing QSIG Stacks
Because CISS builds upon the QSIG core protocol, many aspects of implementation involve extending the existing call control state machine to handle call independent states. The standard recommends a separate finite state machine (FSM) for each active CISS transaction, independent of any call state machine. This modularity simplifies integration and prevents accidental interference with normal circuit-switched calls.
3.2 Timer Management
The protocol defines several timers to manage transaction reliability:
- T-CISS-1: Waiting for CISS_CONNECT or CISS_REJECT after sending CISS_SETUP (default 30 s).
- T-CISS-2: Waiting for CISS_RELEASE after sending a release request (default 15 s).
- T-CISS-3: Request retransmission interval (5 s, 3 retries).
These values are aligned with timers defined in ITU-T Q.931 to ensure compatibility with ISDN networks.
3.3 Interworking with Legacy Systems
The Technical Report provides guidelines for interworking with older PINXs that may not support CISS natively. An optional gateway function can map CISS messages into FACILITY messages encapsulated in basic call control procedures. This allows gradual migration without requiring a complete network upgrade.
Success Story: Several enterprise networks have used CAN/CSA-ISO/IEC TR 14475-04 to deploy message‑waiting notification and remote terminal configuration services across multivendor PBX systems, achieving full interoperability where proprietary solutions previously existed.
4. Compliance Notes and Testing Considerations
4.1 Conformance Assessment
While TR 14475 is a Technical Report and thus not subject to mandatory conformity assessment in the traditional sense, many Canadian and international organizations require equipment to demonstrate adherence to its specifications.
- Static conformance: Ensure all mandatory message types and IEs are supported.
- Dynamic conformance: Validate correct state transitions and timer behaviour.
- Interoperability testing: Pair implementations from different vendors, including reference implementations.
4.2 Test Scenarios
Commonly used test cases include:
- Successful and unsuccessful CISS setup sequences.
- Transmission of user data within CISS messages.
- Handling of overlapped signalling (segmented messages).
- Error recovery mechanisms (e.g., lost CISS_CONNECT).
4.3 Certification in Canada
Although the CAN/CSA series is often granted through voluntary standards adoption, publicly procured PISN equipment may be required to comply with CAN/CSA-ISO/IEC TR 14475-04. Suppliers should consult with the Conseil de la radiodiffusion et des télécommunications canadiennes (CRTC) or the Standards Council of Canada (SCC) for specific regulatory references.
Tip: When performing compliance testing, refer to the companion standard CAN/CSA-ISO/IEC 11574-1 for the general requirements of signalling protocol for call independent supplementary services and the allocation of service identifiers.
Q: What is the difference between call independent supplementary services (CISS) and call dependent supplementary services (CDSS) in a PISN?
A: Call independent services operate without a connection-oriented association; they can be used to signal information or activate features even when no call is in progress. Call dependent services, such as call hold or call transfer, require an active call association. CAN/CSA-ISO/IEC TR 14475-04 exclusively covers the signalling for the former.
A: Call independent services operate without a connection-oriented association; they can be used to signal information or activate features even when no call is in progress. Call dependent services, such as call hold or call transfer, require an active call association. CAN/CSA-ISO/IEC TR 14475-04 exclusively covers the signalling for the former.
Q: Is CAN/CSA-ISO/IEC TR 14475-04 mandatory for all private networks in Canada?
A: No, it is a voluntary standard. However, government and large enterprise procurement contracts often mandate compliance to ensure multi-vendor interoperability and to align with international best practices. The standard is widely adopted as a de facto requirement for new PISN deployments.
A: No, it is a voluntary standard. However, government and large enterprise procurement contracts often mandate compliance to ensure multi-vendor interoperability and to align with international best practices. The standard is widely adopted as a de facto requirement for new PISN deployments.
Q: How does CAN/CSA-ISO/IEC TR 14475-04 relate to the more familiar QSIG standards?
A: QSIG is the fundamental signalling system for PISN (per ISO/IEC 11572/11582). This Technical Report extends QSIG by specifying the protocol messages and procedures for call independent supplementary services. It assumes that the underlying QSIG infrastructure (Layer 2 and Layer 3 basic call) is already in place.
A: QSIG is the fundamental signalling system for PISN (per ISO/IEC 11572/11582). This Technical Report extends QSIG by specifying the protocol messages and procedures for call independent supplementary services. It assumes that the underlying QSIG infrastructure (Layer 2 and Layer 3 basic call) is already in place.
Q: Are there any known interoperability issues when implementing this standard?
A: Interoperability can be affected by vendor-specific interpretations of the Supplementary Service Identifier registry. To mitigate this, implementers should participate in industry plugtest events and validate against the reference implementations described in Annex B of the Technical Report. The standard’s informative nature means that careful attention to the accompanying implementation guides is essential.
A: Interoperability can be affected by vendor-specific interpretations of the Supplementary Service Identifier registry. To mitigate this, implementers should participate in industry plugtest events and validate against the reference implementations described in Annex B of the Technical Report. The standard’s informative nature means that careful attention to the accompanying implementation guides is essential.
— This article is prepared for informational purposes and reflects the state of the standard as of 2026.