Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Interconnecting PISN over IP Networks: A Technical Guide to CAN/CSA-ISO/IEC-15429-04
Mapping Functions, Protocol Interworking, and Compliance for Transparent QSIG Tunnelling
Scope and Field of Application
The international standard ISO/IEC 15429:2003, adopted in Canada as CAN/CSA-ISO/IEC-15429-04, specifies the mapping functions required to tunnel QSIG signalling over Internet Protocol (IP) networks. Its primary field of application is the interconnection of Private Integrated Services Networks (PISN) across enterprise IP backbones and wide-area networks.
The standard defines how QSIG—the signalling protocol at the Q reference point defined in ISO/IEC 11582—can be encapsulated and transported transparently through an IP network. This ensures that all supplementary services (e.g., Call Completion on No Reply, Name Identification, Call Diversion) remain fully operational across the IP segment without modifying the legacy PBX endpoints.
Target audiences for this standard include network architects designing converged voice-data infrastructure, telephony system integrators, and equipment manufacturers developing gateway or IP-PBX products that must maintain backward compatibility with traditional digital PISN systems.
Implementation Note: The standard does not define a new signalling protocol. Instead, it provides a structured mapping framework that allows existing QSIG implementations to communicate transparently over heterogeneous IP transport layers.
Technical Architecture and Mapping Functions
Core Mapping Model
ISO/IEC 15429 introduces the concept of a tunnelling association between PISN endpoints. This association is managed through a set of abstract service primitives, collectively known as the SS-Co (Signalling and Control) mapping functions. These functions are responsible for establishing, maintaining, and releasing a logical tunnel that carries QSIG protocol data units across the IP network.
| Function | SS-Co Primitive | Purpose | Associated Service |
|---|---|---|---|
| MAP-CONNECT | SS-Co-CONNECT request/indication | Establishes a tunnelling association between two PISN endpoints | Basic Call Control |
| MAP-DATA | SS-Co-DATA request/indication | Transports QSIG signalling messages in the tunnel | All Supplementary Services |
| MAP-RELEASE | SS-Co-RELEASE request/indication | Terminates the tunnelling association | Call Clearing |
| MAP-ERROR | SS-Co-ERROR indication | Notifies of protocol or transport errors | Exceptions / Diagnostics |
Protocol Interworking Requirements
To maintain transparency, the SCQ (Signalling, Control, QSIG) mapping function is responsible for converting between QSIG primitives and the underlying IP transport. The standard mandates a strict one-to-one mapping of QSIG information elements to IP payload fields. This prevents data loss during encapsulation.
| Traffic Class | IP DSCP Marking | Max Acceptable Delay | Transport Requirement |
|---|---|---|---|
| Signalling (SCQ) | CS6 / AF41 | < 100 ms | TCP or sequenced UDP |
| Voice Bearer | EF (DSCP 46) | < 150 ms | RTP/UDP |
| Tunnelling Control Data | AF31 | < 400 ms | Reliable transport |
Interoperability Warning: Mismatches in the maximum QSIG information element length field between the two endpoints of the tunnelling association can cause silent call failures. Implementers must validate that both gateways support the full message set defined in the PICS for 15429.
Protocol Implementation Highlights
Layering and Encapsulation
The QSIG tunnelling implementation follows a strict layering model on the IP side:
- Upper Layer (QSIG): The original QSIG message as generated by the PISN endpoint.
- SCQ Layer: Adds the tunnelling header (TUN-HDR), which includes protocol discriminator, tunnelling identifier, and message type.
- Transport Layer: Encapsulates the SCQ frame for transport over the IP network (typically TCP port assigned per profile or UDP with application-level sequencing).
Supplementary Service Transparency
A key achievement of this standard is the preservation of complex supplementary service interactions. Features such as Call Intrusion, Path Replacement, and Common Information (CNIP/CNIR) are tunnelled end-to-end. The gateway does not need to interpret the QSIG content; it only acts as a transparent relay.
Business Value: By adhering to CAN/CSA ISO IEC 15429-04, enterprises can migrate from TDM-based PBX trunks to cost-efficient IP backbones without replacing legacy PISN equipment or retraining staff on new telephony features.
Compliance and Certification Pathways
Compliance with the standard is verified through a Protocol Implementation Conformance Statement (PICS). Testing bodies evaluate the following critical aspects:
- Static Conformance: Does the implementation support all mandatory SS-Co functions?
- Dynamic Conformance: Does the implementation correctly sequence the MAP-CONNECT, MAP-DATA, and MAP-RELEASE primitives?
- SCQ Compatibility: Does the TUN-HDR formatting strictly match the ISO/IEC 15429 logical channel structure?
The Canadian adoption (CAN/CSA-ISO/IEC-15429-04) is fully identical to the international edition. Certification in Canada typically follows the SCC (Standards Council of Canada) accreditation framework, recognizing testing performed by ISO/IEC 17025 accredited laboratories.
Regulatory Penalty Warning: Network equipment marketed for PISN interconnection in Canada that claims compliance with ANSI/TIA or legacy T1 standards but fails to meet the QSIG tunnelling requirements of CAN/CSA-ISO/IEC-15429-04 may face restricted deployment by carriers and rejection in enterprise tenders.
Frequently Asked Questions
Q: Does ISO/IEC 15429 replace existing ETSI or TIA standards for QSIG?
A: No. ISO/IEC 15429 specifically addresses the transport of QSIG over IP networks. It does not replace QSIG signalling standards (e.g., ISO/IEC 11572, ISO/IEC 11582) or supplement ETSI QSIG profiles. Instead, it provides the encapsulation bridge needed when PISN interconnection spans an IP backbone.
A: No. ISO/IEC 15429 specifically addresses the transport of QSIG over IP networks. It does not replace QSIG signalling standards (e.g., ISO/IEC 11572, ISO/IEC 11582) or supplement ETSI QSIG profiles. Instead, it provides the encapsulation bridge needed when PISN interconnection spans an IP backbone.
Q: How does this standard differ from an H.323 or SIP trunk?
A: The fundamental difference is transparency. H.323 and SIP are conversion gateways that translate QSIG to another protocol. CAN/CSA-ISO-IEC-15429-04 mandates tunnelling, which means the native QSIG signalling is encapsulated and forwarded without translation. This fully preserves proprietary or private supplementary service behaviour.
A: The fundamental difference is transparency. H.323 and SIP are conversion gateways that translate QSIG to another protocol. CAN/CSA-ISO-IEC-15429-04 mandates tunnelling, which means the native QSIG signalling is encapsulated and forwarded without translation. This fully preserves proprietary or private supplementary service behaviour.
Q: Is the standard relevant for cloud-based or hosted PBX architectures?
A: Yes, the principles defined in ISO/IEC 15429 can be extended to virtualized PISN functions. The abstract mapping functions are independent of the physical topology. Cloud interconnects that expose a QSIG trunk interface often implement this tunnelling standard to maintain compatibility with on-premises PISN equipment.
A: Yes, the principles defined in ISO/IEC 15429 can be extended to virtualized PISN functions. The abstract mapping functions are independent of the physical topology. Cloud interconnects that expose a QSIG trunk interface often implement this tunnelling standard to maintain compatibility with on-premises PISN equipment.
Q: What are the main conformance documents required for certification?
A: The primary document is the PICS proforma. Testing also requires the Implementation Extra Information for Testing (IXIT) document, which provides details of the specific IP transport, maximum message sizes, and supported supplementary services list.
A: The primary document is the PICS proforma. Testing also requires the Implementation Extra Information for Testing (IXIT) document, which provides details of the specific IP transport, maximum message sizes, and supported supplementary services list.