ECMA 326 : 1ED 2001

1 Scope
2 Conformance
3 References
4 Definitions
  4.1 External definitions
  4.2 Other definitions
      4.2.1 Entity A
      4.2.2 Entity B
      4.2.3 Gateway
      4.2.4 IP network
      4.2.5 Leg A
      4.2.6 Scenario A1
      4.2.7 Scenario A2
5 Acronyms
6 Service architecture
  6.1 Service architecture for invocation and operation
      6.1.1 ECMA-186 service architecture
      6.1.2 H.450.9 service architecture
      6.1.3 Scenarios for interworking
      6.1.4 Selection of the same gateway for all phases
  6.2 Options
7 Protocol interworking - General requirements
8 Protocol interworking - Messages and APDUs
  8.1 Signalling phase 1 - invocation of call completion
      8.1.1 Scenario A1
      8.1.2 Scenario A2
  8.2 Signalling phase 2 - user B available notification
      8.2.1 Scenario A1
      8.2.2 Scenario A2
  8.3 Signalling phase 3 - CC call establishment
      8.3.1 Scenario A1
      8.3.2 Scenario A2
  8.4 Signalling phase 4 - cancellation of SS-CC
      8.4.1 Scenario A1
      8.4.2 Scenario A2
9 Protocol interworking - content of APDUs
  9.1 APDU content mapping from QSIG to H.323
      9.1.1 ccbsRequest/ccnrRequest invoke APDU mapping
      9.1.2 ccbsRequest/ccnrRequest return result APDU
            mapping
      9.1.3 ccCancel/ccExecPossible invoke APDU mapping
  9.2 APDU content mapping from H.323 to QSIG
      9.2.1 ccbsRequest/ccnrRequest invoke APDU mapping
      9.2.2 ccbsRequest/ccnrRequest return result APDU
            mapping
      9.2.3 ccCancel/ccExecPossible invoke APDU mapping
Annex A - Implementation Conformance Statement (ICS)
          proforma
Annex B - Message flow examples

Gives the signalling interworking between "QSIG" and "H.323" in support of call completion supplementary services within a Corporate telecommunication Network (CN).