home *** CD-ROM | disk | FTP | other *** search
- THE DRAWINGS CONTAINED IN THIS RECOMMENDATION HAVE BEEN DONE IN AUTOCAD
- Recommendation U.15
- INTERWORKING RULES FOR INTERNATIONAL SIGNALLING SYSTEMS
- ACCORDING TO RECOMMENDATIONS U.1, U.11 AND U.12
- (Malaga-Torremolinos, 1984)
- The CCITT,
- considering
- (a) that in international transit calls, a number of different signalling
- standards may be involved;
- (b) that interworking between signalling systems according to Recommendations U.1 and U.11 is
- already mostly covered by those Recommendations;
- (c) that it is necessary to define specifically the
- interworking rules between Recommendations U.1 or U.11 signalling
- and Recommendation U.12 signalling;
- (d) that it is also useful to cover in the same
- Recommendation any interworking problems between Recommendations
- U.1 and U.11 signalling standards;
- (e) that the originating Administration is responsible for
- international telex accounting;
- (f) that it is desirable for standard arrangements to apply
- for obtaining the called customer's answerback;
- (g) that it is essential to prevent alternative routing in
- transit centres if network identities cannot be conveyed to the
- originating centre;
- (h) that the use of type D signalling according to
- Recommendation U.12 should be considered in preference to type C
- (Recommendation U.11) signalling for transit working;
- (i) that types A and B (Recommendation U.1) signalling may
- only be used for transit working where no alternative routings are
- allowed;
- (j) that there may be cases where conversion of Network
- Identification Code (NIC) to a Transit Centre Identification Code
- (TCIC) or vice versa cannot be implemented. In such cases the TCICs
- and NICs shall be absorbed and alternative routing shall not be
- allowed within that transit centre. Onward selection shall indicate
- this condition by using the appropriate COT,
- unanimously declares the view that
- 1 General
- The rules for interworking should cover the following areas:
- - alternative routing,
- - conversion of TCIC (Recommendation U.11) and NIC (Recommendation U.12)
- signals,
- - service signal conversion,
- - exchange of line identifications,
- - call-connected signal conversion,
- - methods for obtaining the called subscriber's answerback.
- For the purposes of this Recommendation it shall be assumed that a typical
- type D interworking connection comprises a first and a last type D exchange and
- intermediate type D exchanges if any. These are defined below:
- A first type D exchange uses type D signalling on the outgoing side and
- any other trunk signalling standard or directly connected subscriber line
- standard on the incoming side.
- An intermediate type D exchange uses type D signalling on both the
- incoming and outgoing sides.
- A last type D exchange uses type D signalling on the incoming side and any
- other trunk signalling standard or directly connected subscriber line standard on
- the outgoing side.
- 2 Rules for alternative routing
- In general, alternative routing should not be allowed when the incoming
- circuit uses an A or B signalling standard. Table 1/U.15 gives details of each
- case.
- 3 Rules for conversion of TCICs and NICs (see Table 1/U.15 for
- details)
- Rule 1 - The last type D exchange should convert any TCIC received from
- outgoing type C circuits to the type D NIC format. Where a bilateral
-
-
-
- Fascicle VII.2 - Rec. U.15 PAGE1
-
- agreement exists between Administrations to use TCICs on a type A signalling
- route, then these may be converted by the last type D exchange to the NIC
- format at the discretion of the Administration of that exchange. This
- requires that the TCIC must always use the standard Administration's
- identification letter(s) as recommended in Recommendation U.11, S 4 and
- defined in the ITU publication List of Indicators for the Telegraph
- Retransmission System and Telex Network Identification Codes, Part A
- (Recommendation F.60, S 3.4.2.4 refers).
- Rule 2 - Non-standard information, e.g. type A register codes will be
- absorbed by the last type D exchange. Such codes may also be received on
- type C circuits. It is therefore recommended that Administrations should, in
- no circumstances, return from terminating or transit centres any
- International Telegraph Alphabet No. 2 (ITA2) sequences which could be
- incorrectly interpreted as TCICs.
- Rule 3 - In the case of calls from type A or C circuits routed to type D
- circuits, the network identification codes (NICs) received from the type D
- network may be converted into the type C transit centre identification code
- (TCIC format) by the first type D exchange, see Table 1/U.15.
- The NICs received from the type D network will be translated into the TCIC
- format of ITA2 Combination No. 29, followed by
- recommended in Recommendation F.60) followed by number of
- Combinations No. 30 to complete a sequence of seven
- combinations.
- Rule 4 - In the case of calls from type B circuit routing to a
- type D circuit, the first type D exchange shall absorb any
- NICs.
- poss
- possible call connected signal and answerback timing problems
- The conversion from 3 or 4 character NICs to 7 character TCICs can result
- firstly in the callVconnected signal arriving at the first type D centre before
- complete transmission of the last TCIC, and secondly, in some cases, the
- answerback arriving before complete transmission of the callVconnected signal to
- the incoming circuit. It is necessary to overcome this difficulty by delaying the
- forwarding of selection in relation to the activities on the backward path.
- The third COT character should be sent by the first type D exchange to
- indicate (by bit b1) to the following type D exchanges that a delay of forward
- selection is necessary, since the call has been received from a nonVtype D
- signalling standard for which conversion of NICs to TCICs is required.
- Figure 1/U.15 shows the timing diagram of this protocol.
- Note 1 V TCICs received from distant type C links would pass through the
- type D links with the appropriate conversion. Where the third COT indicates that
- conversion of NIC to TCIC is necessary, onward seizure should not occur before
- the complete transmission of CSC No. 12 of the locally generated NIC.
- Where the conversion of NIC to TCIC is not necessary, onward seizure of the
- outgoing circuit should not occur before the complete transmission of the
- receptionVconfirmation signal.
- Note 2 V A problem may exist where the same Recommendation F.69 code is
- allocated to more than one RPOA.
- 5 Rules for service signal conversion
- Rule 1 V The last type D exchange will convert all returned standard service
- signals into the appropriate type D numeric service codes. In the case of
- additional information included in the service text (i.e. a, d, g, d
- preceding a Recommendation U.1 type A or B service code (see Recommendation
- U.1, ' 10.1.2)), only the standard Recommendation U.1/U.11 service text will
- be translated by the type D transit centre.
- Table 7b/U.12 gives details of service signal conversion.
- 6 Rules for exchange of line identifications
- Rule 1 V If the incoming circuit is not a subscriber line then the first
- type D exchange shall not request a called line identification.
- Rule 2 V When the incoming circuit is not a subscriber line and a request
- for calling line identification is received, the first type D exchange shall
- send CSC No. 12 only, to indicate that no identification is available as per
- Table 1/U.12.
- Rule 3 V If the incoming circuit is a subscriber line and the called line
- identification is required, then the first type D exchange shall recognize
-
-
-
-
- PAGE6 Fascicle VII.2 - Rec. U.15
-
- receipt of the callVconnected signal not preceded by a STTC and a TTC signal
- as an indication that a called line identification is not available.
- Rule 4 V If the outgoing circuit is not a subscriber line, then the last
- type D exchange shall not request a calling line identification.
- Rule 5 V When the outgoing circuit is not a subscriber line and a request
- for called line identification is received, the last type D exchange shall
- indicate that the identification is not available, as described in
- Recommendation U.12, S 3.13.
- 7 Rules for call connected signal conversion
- Rule 1 - The last type D exchange shall convert all variations of received
- call connected signals as defined in Recommendations U.1 and U.11 to the
- type D call connected signal, indicating that call metering is required (CSC
- No. 13).
- Rule 2 - The first type D exchange shall convert CSC No. 13 to the call
- connected signal according to Recommendations U.1 or U.11.
- Rule 3 - CSC No. 14 (call connected without metering) received at the first
- type D exchange may or may not be converted to a call connected on type A, B
- or C circuits. The use of CSC No. 14 is left for further study.
- 8 Rules for obtaining the called subscriber's answerback when interworking
- type D with other signalling systems
- Rules 2 to 4 apply to the first type D exchange and Rules 5 to 7 to the last
- type D exchange.
- A compilation of the rules is shown in Tables 2/U.15 and 3/U.15.
- Rule 1 - As a general rule, the first and the last type D exchanges should
- behave independently of each other's interworking requirements with regard
- to controlling the answerback tripping, and intermediate exchanges will be
- transparent to this control.
- Rule 2 - For locally connected subscribers the first type D exchange will
- generate the WRU on receipt of the call connected signal as per
- Recommendation U.12, Appendix III.
- Rule 3 - If the incoming circuit uses an automatic return of answerback
- trunk signalling standard, then the first type D exchange will generate a
- WRU two seconds after receipt of the call connected signal.
- Rule 4 - If the incoming circuit uses a nonautomatic return of answerback
- trunk signalling standard, then the first type D exchange will
- through-connect on receipt of the call connected signal without generating a
- WRU.
- Rule 5 - For locally connected subscribers, the last type D exchange will
- through-connect after the call connected signal has been transmitted on the
- incoming type D trunk.
- Rule 6 - If the outgoing circuit uses an automatic return of answerback
- trunk signalling standard, then the last type D exchange will absorb any
- incoming characters on the forward path until two seconds from the
- commencement of the first backward path character. If no characters have
- been received on the backward path within 8-9 seconds following the start of
- the received call connected signal, then through-connection shall occur. The
- alternative of clearing the call is for further study.
- Rule 7 - If the outgoing circuit uses a nonautomatic return of answerback
- trunk signalling standard, then the last type D exchange shall delay any
- received WRU until two seconds from the start of the received call connected
- signal. Through-connection shall occur following the retransmission of the
- WRU or after two seconds from the start of the received call connected
- signal if no WRU has been received.
- TABLE 1/U.15
- Rules for conversion of network identification codes (NICs)
- and transit centre identification codes (TCICs) and alternative routing
- Incoming Outgoing Action to be taken by the transit exchange
- signalling signalling
- Type D The NIC shall be retransmitted as received.
- Alternative routing is allowed.
- Type C TCICs shall be converted into NICs. Any type
- A register codes shall be absorbed.
- Alternative routing is allowed.
- Type D Type B No register codes will be received.
- Alternative routing is not allowed (see
- Note).
- Type A with Absorb register codes. Alternative routing is
- register codes not allowed (see Note).
- Type A with TCICs may be absorbed or converted to NICs at
- TCICs the discretion of individual Administrations.
- Alternative routing is not allowed (see
- Note).
- Type D NICs shall be converted into TCICs.
- Alternative routing is allowed.
- Type C with TCICs shall be retransmitted as received.
- register codes The type A register codes may be
- or TCICs retransmitted as received at the discretion
- of individual Administrations. Alternative
- routing is allowed.
- Type C Type B No register codes will be received.
-
-
-
- Fascicle VII.2 - Rec. U.15 PAGE1
-
- Alternative routing is not allowed (see
- Note).
- Type A with The register codes may be absorbed or
- register codes retransmitted as received at the discretion
- of individual Administrations. Alternative
- routing is not allowed (see Note).
- Type A with The TCICs may be absorbed or retransmitted as
- TCICs received at the discretion of the individual
- Administration. Alternative routing is not
- allowed (see Note).
- Type D Any received NICs shall be absorbed.
- Alternative routing is not allowed (see
- Note).
- Type C with Any received register codes or TCICs shall be
- Type B register codes absorbed. Alternative routing is not allowed
- or TCICs (see Note).
- Type B No register codes will be received.
- Alternative routing is not allowed (see
- Note).
- Type A with Any received register codes or TCICs shall be
- register codes absorbed. Alternative routing is not allowed
- or TCICs (see Note).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PAGE6 Fascicle VII.2 - Rec. U.15
-
- TABLE 1/U.15 (continued)
- Incoming Outgoing Action to be taken by the transit exchange
- signalling signalling
- Type D Conversion of NICs to TCICs is at the
- discretion of individual Administrations.
- Alternative routing can be allowed only if
- conversion of NICs to TCICs occurs.
- Type A using a Type C with The received register codes or TCICs may be
- TCIC (trunk register codes absorbed or retransmitted at the discretion
- route dedicated or TCICs of individual Administrations. Alternative
- to originating routing is allowed only if retransmission of
- traffic only) TCICs occurs.
- Type B No register codes will be received.
- Alternative routing is not allowed (see
- Note).
- Type A with Any received register codes or TCICs may be
- register codes absorbed or retransmitted as received at the
- or TCICs discretion of individual Administrations.
- Alternative routing is not allowed (see
- Note).
- Type D NICs will be absorbed. Alternative routing is
- not allowed (see Note).
- Type B No register codes will be received.
- Alternative routing is not allowed (see
- Note).
- Type A using Type C with The received register codes or TCICs may be
- register codes register codes absorbed or retransmitted, at the discretion
- (trunk route or TCICs of the individual Administrations.
- dedicated to Alternative routing is not allowed (see
- originating Note).
- traffic only)
- Type A with The received register codes or TCICs may be
- register codes absorbed or retransmitted as received, at the
- or TCICs discretion of individual Administrations.
- Alternative routing is not allowed (see
- Note).
- Type D NICs may be absorbed or converted to TCICs,
- at the discretion of individual
- Administrations. Alternative routing is not
- allowed (see Note).
- Type A with Type C with
- register codes
- or TCICs
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Fascicle VII.2 - Rec. U.15 PAGE1
-
- register codes Register codes or TCICs may be absorbed or
- or TCICs retransmitted as received, at the discretion
- of individual Administrations. Alternative
- routing is not allowed (see Note).
- Type B No register codes will be received.
- Alternative routing is not allowed (see
- Note).
- Type A with Register codes or TCICs may be absorbed or
- register codes retransmitted as received at the discretion
- or TCICs of individual Administrations. Alternative
- routing is not allowed (see Note).
- Note - Where alternative routing is stated as "not allowed", it applies in this
- transit exchange and shall also be indicated in the COT signals on outgoing type C
- and D signalling to prevent alternative routing in distant centres. Alternative
- routing is not allowed when the outgoing or incoming trunks use type A or B
- signalling, with the one exception of the case where a type A incoming route accepts
- TCICs and is dedicated to originating traffic only and where the outgoing signalling
- is type C or D standard.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PAGE6 Fascicle VII.2 - Rec. U.15
-
- TABLE 2/U.15
- Rules for obtaining the called subscriber's answer-back (first type D exchange)
- Incoming Action to be taken by the first type D Outgoing
- signalling type exchange signalling type
- Type A, 1. Send WRU two seconds after receiving
- Type B call-connected signal.
- (automatic 2.Connect-through backward path after Type D
- return of sending the call-connected signal.
- answer-back), 3.Connect-through forward path after sending
- Type C WRU. (See S 8, Rule 3 and Note below)
- Type B, 1.No action on WRU.
- (non-automatic 2.Connect-through backward path after Type D
- return of sending call-connected signal.
- answer-back) 3.Connect-through forward path after
- receiving call-connected signal. (See S 8,
- Rule 4)
- 1. Send WRU 1-2 character periods after Type D
- Subscriber receiving call-connected signal.
- 2.Connect-through backward path after
- receiving call-connected signal.
- 3.Connect-through forward path after sending
- WRU. (See S 8, Rule 2 and Note below)
- Note - Where a call is recognised as originating from a service position (either as
- indicated by the COT received or derived from the use of dedicated service trunks or
- lines), then individual Administrations may at their discretion inhibit the
- generation of the WRU at the first type D exchange.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Fascicle VII.2 - Rec. U.15 PAGE1
-
- TABLE 3/U.15
- Rules for obtaining the called subscriber's answer-back (last type D exchange)
- Incoming Action to be taken by the first type D Outgoing
- signalling type exchange signalling type
- 1. Absorb WRU and any other characters
- on the forward path until
- through-connection of the forward path.
- Type D 2.Connect-through the backward path after
- sending the call connected signal and in Type A,
- the case of type C on completion of the Type B
- received call-connected signal. (automatic
- 3.Connect-through the forward path two return of
- seconds after reception of the first answer-back),
- backward path characters following the Type C
- received call-connected signal or in the
- absence of any characters, 8-9 seconds
- after the start of the received
- call-connected signal.
- (See S 8, Rule 6)
- 1. Delay any received WRU until two
- seconds after the start of the received
- Type D call-connected signal. Type B
- 2.Connect-through the backward path after (non-automatic
- sending the call- connected signal. return of
- 3.Connect-through the forward path after answer-back)
- retransmitting any received WRU, or in the
- absence of a received WRU, two seconds
- after the start of the received
- call-connected signal.
- (See S 8, Rule 7)
- 1.No action on WRU.
- 2.Connect-through backward path after
- Type D sending call-connected signal. Subscriber
- 3.Connect-through forward path after sending
- call-connected signal.
- (See S 8, Rule 5)
- Figure 1/U.15 - CCITT 67820
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PAGE6 Fascicle VII.2 - Rec. U.15
-
-