Full Description

The present document specifies functions for using an H.323 packet network in order to interconnect two PrivateIntegrated services Network eXchanges (PINXs) forming part of a Private Integrated Services Network (PISN).Interconnection is achieved by carrying the inter-PINX signalling protocol over the H.323 call signalling channel,making use of the protocol tunnelling facilities of H.323, and inter-PINX user information (e.g. voice) over logicalchannels established through H.323. Each logical channel usually represents a unidirectional media stream conveyed bymeans of the Real-time Tranport Protocol (RTP). The inter-PINX signalling protocol is assumed to be QSIG, asspecified in ECMA-143 [2], ECMA-165 [3] and other standards.

The present document provides for an on-demand type of interconnection, where a separate H.323 call is established atthe start of each PISN call and cleared down at the end of that call. A semi-permanent scenario where a single H.323call with an indefinite lifetime carries QSIG on behalf of many PISN calls is described as an additional option.

In the scenarios covered in the present document, the PINXs participating in a call are not necessarily aware of theH.323 network providing the interconnection, and the features available are those of the QSIG network. This is differentfrom a scenario where true interworking between QSIG and H.323 (i.e. QSIG-H.323-QSIG) is used to connect twoPISNs or two parts of the same PISN. In this latter case all networks participate in a call on equal terms, and features arelimited to those available in all networks and supported by the gateways. This latter scenario is outside the scope of thepresent document.

The present document is applicable to PINXs that can be interconnected to form a PISN using QSIG as the inter-PINXsignalling protocol.

Product Details

Edition: 1.2.1 Published: 03/01/2004 Number of Pages: 26 File Size: 1 file , 140 KB