All drawings contained in this Recommendation have been done in Autocad.
Recommendation Q.764
SIGNALLING PROCEDURES
1	General
1.1	Relationship with other Recommendations
	This Recommendation describes the signalling procedures for the set–up and cleardown of national and international ISDN connections. The messages and signals are defined in Recommendation Q.762 and their format and content are given in Recommendation Q.763. Recommendation Q.730 contains the procedures for supplementary services. (These were previously § 4 of Recommendation Q.764.)
1.2	Numbering (see Recommendations E.163, E.164)
	The procedures described assume that the ISDN uses the international numbering plan defined for the ISDN and thus provides a basic circuit switched service between ISDN terminals or between ISDN terminals and terminals being connected to the existing international telephony network.
1.3	Address signalling
	In general, the call set–up procedure described is standard for both speech and non–speech connections using en–bloc address signalling for calls between ISDN terminals. Overlap address signalling is also specified.
1.4	Basic procedures
	The basic call control procedure is divided into three phases; call set–up, the data/conversation phase and call cleardown. Messages on the signalling link are used to establish and terminate the different phases of a call. Standard inband supervisory tones and/or recorded announcements are returned to the caller onspeech and 3.1 kHz connections to provide information on call progress. Calls originating from ISDN terminals may be supplied with more detailed call progress information by means of additional messages in the access protocol supported by a range of messages in the network.
1.5	Signalling methods
	Two signalling methods are used in this Recommendation:
–	link–by–link;
–	end–to–end.
	The link–by–link method is primarily used for messages that need to be examined at each exchange (see § 2). The end–to–end methods are used for messages of end point significance (see Recommendation Q.730).
	The link–by–link method may be used for messages of end point significance. (However, the messages may be affected by processing delays.)
1.6	Layout of Recommendation Q.764
	The procedures specified in § 2 of this Recommendation relate to basic calls (i.e. calls not involving supplementary services). Section 3 of this Recommendation specifies the procedures relating to end–to–end signalling connections. The additional requirements to be met in the case of calls involving supplementary services and network utilities are specified in Recommendation Q.730. The timers used in this Recommendation are summarized in Annex A. The SDLs for the ISDN–UP are presented in Annex B.
1.7	Interworking with other signalling systems or user parts
	Only some examples are included in this Recommendation and these should not be used as a definitive interworking guide.
2	Basic call control and signalling procedures
	Figures 1/Q.764 to 10/Q.764 at the end of this section show the ISDN call set–up sequences which are described below.
2.1	Successful call set–up
2.1.1	Forward address signalling – en bloc operation
2.1.1.1	Actions required at originating exchange
a)	Circuit selection
	When the originating exchange has received the complete selection information from the calling party, and has determined that the call is to be routed to another exchange, selection of a suitable, free, inter–exchange circuit takes place and an initial address message is sent to the succeeding exchange.
	Appropriate routing information is either stored at the originating exchange or at a remote database to which a request may be made.
	The selection of the route will depend on the called party number, connection type required and the network signalling capability required. This selection process may be performed at the exchange or with the assistance of the remote database.
	In addition, in the case of a subscriber with digital access, the set–up message contains bearer capability information which is analyzed by the originating exchange to determine the correct connection type and network signalling capability. The bearer capability information will be mapped into the user service information parameter of the initial address message. The information received from the access interface is used to set the value of the transmission medium requirement parameter. The first value of bearer information received will be used to set the initial mode of the connection.
	The connection types allowed are:
–	speech;
–	3.1 kHz audio;
–	64 kbit/s unrestricted;
–	alternate speech/64 kbit/s unrestricted;
–	alternate 64 kbit/s unrestricted/speech.
The network signalling capabilities allowed are:
–	ISDN–UP preferred;
–	ISDN–UP required;
–	ISDN–UP not required (any signalling system).
	The information used to determine the routing of the call by the originating exchange will be included in the initial address message, (as transmission medium requirement and forward call indicators), to enable correct routing at intermediate exchanges. The initial address message conveys implicitly the meaning that the indicated circuit has been seized.
	In the case where N×64 kbit/s (N2) connections are required, the procedures for a single 64 kbit/s connection may be used if the N×64 kbit/s are contiguous 64 kbit/s channels and are pre–assigned for N×64 kbit/s use.
	If subaddress information is received from the calling access, this information is passed unchanged to the destination exchange in the access transport parameter of the initial address message.
b)	Address information sending sequence
	The sending sequence of address information on international calls will be the country code (not sent to an incoming international exchange) followed by the national (significant) number. On national connections, the address information may be the local number or the national (significant) number as required by the Administration concerned. For calls to international operator positions (Code 11 and Code 12) refer to Recommendation Q.107.
	The end of pulsing (ST) signal will be used whenever the originating exchange or the outgoing exchange is in a position to know by digit analysis that the final digit has been sent.

c)	Initial address message
	The initial address message (IAM) in principle contains all the information that is required to route the call to the destination exchange and connect the call to the called party.
	All initial address messages will include a protocol control indicator (in the forward call indicator parameter) and a transmission medium requirement parameter.
	The originating exchange will set the parameters in the protocol control indicator and in the ISDN–UP preference indicator to indicate:
i)	the type of end–to–end method that can be accommodated (§ 3);
ii)	the availability of Signalling System No. 7 signalling;
iii)	the use of the ISDN–UP;
iv)	whether further information is available (to be requested before the called party is alerted);
v)	network signalling capability required, e.g. ISDN–UP required all the way.
	The ISDN–UP preference indicator is set according to the bearer service, teleservice and supplementary service(s) requested. The exact setting depends on the service demand conditions and may be different depending on individual cases. In principle, if the service demand requires ISDN–UP to be essential then the indicator is set to “required”, if the service required is optional but preferred it is set to “preferred”, otherwise it is set to “not required”. The indicator is set to either “required” or “preferred”, or “not required”, according to the most stringent condition required by one or more of the parameters in the initial address message. In addition, if end–to–end signalling is essential to provide the requested service the indicator should always be set to “required” (see Recommendation E.172).
	The transmission medium requirement parameter contains the connection type required information, e.g. 3.1 kHz audio.
The originating exchange may also include in the initial address message:
i)	a call reference (including the point code of the originating exchange) to enable the destination exchange to establish an end–to–end connection (§ 3);
ii)	the calling party number if this is to be passed forward without being requested. The calling party number could contain Code 11 or 12 if the call is from an international operator;
iii)	an SCCP connection request parameter; and
iv)	other information related to supplementary services and network utilities.
The initial address message can contain an access transport parameter.
d)	Transfer of information not included in the initial address message
	As an alternative to the inclusion of call set–up user facility information in the initial address message, any call set–up user facility information that need not be examined at intermediate exchanges and which can be requested from by the destination exchange (see Recommendation Q.763, § 3.22), may be transported between the originating and destination exchange. The method of transportation for this information can be by the link–to–link method (see § 2.1.6) or via the end–to–end methods (see § 3).
e)	Completion of transmission path
	Through connection of the transmission path will be completed in the backward direction (the transmission path is completed in the forward direction on receipt of a connect or answer message) at the originating exchange immediately after the sending of the initial address message, except in those cases where conditions on the outgoing circuit prevent it (see § 2.1.9).
	It is also acceptable that on speech or 3.1 kHz audio calls, through–connection of the transmission path will be completed in both directions immediately after the initial address message has been sent, except in those cases where conditions on the outgoing circuit prevent it (see § 2.1.9).
f)	Network protection timer
	When the originating exchange or the controlling exchange has sent the initial address message the awaiting address complete timer (T7) is started. If timer (T7) expires the connection is released and an indication is returned to the calling subscriber.

2.1.1.2	Actions required at an intermediate exchange
a)	Circuit selection
	An intermediate exchange, on receipt of an initial address message will analyze the called party number and the other routing information (§ 2.1.1.1 a)) to determine the routing of the call. If the intermediate exchange can route the call using the connection type specified in the transmission medium requirement parameter, a free inter–exchange circuit is seized and an initial address message is sent to the succeeding exchange. Within a network if the intermediate exchange does not route the call using just the connection type specified in the transmission medium requirement parameter, the exchange may also examine the user service information containing the bearer capability information (if available) to determine if a suitable route can be selected. In this case if a new connection type is provided the transmission medium requirement parameter is modified to the new connection type.
	For calls between networks, the gateway exchange (e.g. outgoing ISC) must ensure that the transmission medium requirement parameter is set according to the service requested by the customer (see Recommendation E.172). More specifically this parameter is carried unchanged within the international network.
	When no echo suppressor or nature–of–circuit indication is received from a preceding exchange using a signalling system with fewer facilities, the indicators will be considered as received “no” unless positive knowledge is available.
b)	Parameters in the initial address message
	An intermediate exchange may modify signalling information received from the preceding exchange according to the capabilities used on the outgoing route. Signalling information that may be changed are nature of connection indicator, end–to–end method indicator; the most significant digits in the called party number may be amended or omitted (see § 2.1.1.1 b)). A change of the end–to–end method used may also alter parameters (see § 3). Other signalling information is passed on transparently, e.g. the access transport parameter, user service information, etc.
c)	Completion of transmission path
	Through–connection of the transmission path in both directions will be completed at an intermediate exchange immediately after the initial address message has been sent, except in those cases where conditions on the outgoing circuit prevent it (see § 2.1.9).
2.1.1.3	Actions required at the destination exchange
a)	Selection of called party
	Upon receipt of an initial address message the destination exchange will analyze the called party number to determine to which party the call should be connected. It will also check the called party's line condition and perform various checks to verify whether or not the connection is allowed. These checks will include correspondence of compatibility checks, e.g. checks associated with supplementary services.
	At this point, certain call set–up information may need to be obtained from an originating or controlling exchange (see § 2.1.6). Examination of the protocol control indicator will show whether end–to–end information is necessary to be obtained before further processing of the call, in this case the SCCP, pass along or information request and information messages can be used.
	In this case where the connection is allowed, the destination exchange will set up a connection to the called party. If a continuity check has to be performed on one or more of the circuits involved in a connection, setting up of the connection to the called party must be prevented until the continuity of such circuits has been verified.
2.1.2	Forward address signalling – Overlap operation
2.1.2.1	Actions required at originating exchange
a)	Circuit selection
	When the originating exchange has received sufficient information [see § 2.1.2.1 c)] from the calling party to determine that the call is to be routed to another exchange, selection of a suitable, free, inter–exchange circuit takes place and an initial address message is sent to the succeeding exchange.
	Appropriate routing information is either stored at the originating exchange or at a remote database to which a request may be made.
	The selection of the route will depend on the called party number, connection type required and the network signalling capability required. This selection process may be performed at the exchange or with the assistance of a remote database.
	In addition, in the case of a subscriber with digital access, the set–up message contains bearer capability information which is analyzed by the originating exchange to determine the correct connection type and network signalling capability. The bearer capability information will be mapped into the user service information parameter of the initial address message. The information received from the access interface is used to set the value of the transmission medium requirement parameter. The first value of bearer information received will be used to set the initial mode of the connection.
The connection types allowed are:
–	speech;
–	3.1 kHz audio;
–	64 kbit/s unrestricted;
–	alternate speech/64 kbit/s unrestricted;
–	alternate 64 kbit/s unrestricted/speech.
The network signalling capabilities allowed are:
–	ISDN–UP preferred;
–	ISDN–UP required;
–	ISDN–UP not required (any signalling system).
	The information used to determine the routing of the call by the originating exchange will be included in the IAM, (as transmission medium requirement and forward call indicators), to enable correct routing at intermediate exchanges. The IAM conveys implicitly the meaning that the indicated circuit has been seized.
	In the case where N × 64 kbit/s (N  2) connections are required, the procedures for a single 64 kbit/s connection may be used if the N × 64 kbit/s are contiguous 64 kbit/s channels and are pre–assigned for N × 64 kbit/s use.
	If subaddress information is received from the calling access, this information is passed unchanged to the destination exchange in the access transport parameter of the initial address message only.
b)	Address information sending sequence
	The sending sequence of address information on international calls will be the country code (not sent to an incoming international exchange) followed by the national (significant) number. On national connections, the address information may be the local number or the national (significant) number as required by the Administration concerned. For calls to international operator positions (Code 11 and Code 12) refer to Recommendation Q.107.
	The end of pulsing (ST) signal will be used whenever the originating exchange or the outgoing exchange is in a position to know by digit analysis that the final digit has been sent.
c)	Content of initial and subsequent address messages
	The initial and subsequent address messages in principle contain all of the information that is required to route the call to the destination exchange and connect the call to the called party. The contents of the initial address message is the same as described in § 2.1.1.1 c). The only purpose of the subsequent address message is to carry further digits.
	All digits required for routing the call through the international network will be sent in the IAM. On calls with a country code in the number (except in the case of calls to special operators), the IAM will contain a minimum of 4 digits and should contain as many digits as are available. Within national networks the address information contained within the IAM may vary depending on the routing requirement within the network.
	The remaining digits of the number may be sent in subsequent address messages containing one or several digits as they are received. Efficiency can be gained by grouping together as many digits as possible. However, to prevent an increase in postsending delay in those cases where overlap operation with subscribers' dialling is used, it may be desirable to send the last few digits individually.

The end–of–pulsing (ST) signal is always sent in the following situations:
i)	semi–automatic calls;
ii)	test calls; and
iii)	when the end–of–pulsing (ST) signal is received.
	In automatic working, the end–of–pulsing (ST) signal will be sent whenever the originating or outgoing exchange is in a position to know, by digit analysis, that the final digit has been sent. Digit analysis may consist of an examination of the country code and counting the maximum (or fixed) number of digits of the national number. In other cases, the end–of–pulsing signal is not sent and the end–of–address information is determined by the receipt of the address complete message or connect message from the incoming exchange.
d)	Transfer of information not included in the initial address message
	As an alternative to the inclusion of call set–up user facility information in the initial address message, any call set–up user facility information that need not be examined at intermediate exchanges and which can be requested by the destination exchange (see Recommendation Q.763, § 3.22), may be transported between the originating and destination exchange. The method of transportation for this information can be by the link–by–link method (see § 2.1.6) or via the end–to–end methods (see § 3).
e)	Completion of transmission path
	Through connection of the transmission path in the backward direction (the transmission path is completed in the forward direction on receipt of connect or answer message) at the originating exchange will be completed except in the cases where conditions on the outgoing circuit prevent it (see § 2.1.9):
i)	immediately after the sending of the initial address message, or
ii)	when digit analysis or timer (T10), or receipt of the address complete message indicates that all digits have been received.
	It is also acceptable that on speech or 3.1 kHz audio calls, through connection of the transmission path will be completed in both directions immediately after the initial address message has been sent, except in the cases where conditions on the outgoing circuit prevent it (see § 2.1.9).
f)	Network protection timer
	Each time when the originating exchange has sent an address message the awaiting address complete timer (T7) is started. If timer (T7) expires the connection is released and an indication is sent to the calling subscriber.
2.1.2.2	Actions required at an intermediate exchange
a)	Circuit selection
	An intermediate exchange, on receipt of an IAM, will analyze the digits available and the other routing information [see § 2.1.2.1 a)] to determine the routing of the call. If the intermediate exchange can route the call using the connection type specified in the transmission medium requirement parameter a suitable free inter–exchange circuit is seized and an IAM is sent to the succeeding exchange. If the number of digits in the called party number are not sufficient to route the call the routing will be carried out when the intermediate exchange has received additional digits in subsequent address message(s). Any address digits received in subsequent address messages during the circuit selection process may be included in this IAM. Any subsequent address messages received after the IAM has been sent, are forwarded to the succeeding exchange as subsequent address message(s).
	Within the network if the intermediate exchange does not route the call just using the connection type specified in the transmission medium requirement parameter, the exchange may also examine the user service information containing the bearer capability information (if available) to determine if a suitable route can be selected. In this case the transmission medium requirement parameter is modified to the new connection type.
	For calls between networks, the gateway exchange (e.g. outgoing ISC) must ensure that the transmission medium requirement parameter is set according to the service requested by the customer (see Recommendation E.172). More specifically this parameter is carried unchanged within the international network.
	When no echo suppressor or nature–of–circuit indication is received from a preceding exchange using a signalling system with fewer facilities the indicators will be considered as received “no” unless positive knowledge is available.
	Selection of the outgoing national circuit normally can start at an incoming international exchange on receipt of the IAM and signalling can proceed on the first national link.
b)	Parameters in the initial address message
	An intermediate exchange may modify signalling information received from the preceding exchange according to the capabilities used on the outgoing route. Signalling information that may be changed are nature of connection indicator, end–to–end method indicator; the most significant digits in the called party number may be amended or omitted [see § 2.1.1.1 b)]. A change of the end–to–end method used may also alter parameters (see § 3). Other signalling information is passed on transparently, e.g. the access transport parameter, user service information, etc.
c)	Completion of transmission path
	Through–connection of the transmission path in both directions will be completed at an intermediate exchange immediately after the initial address message has been sent, except in those cases where conditions on the outgoing circuit prevent it (see § 2.1.9).
2.1.2.3	Actions required at the destination exchange
a)	Selection of called party
	Upon the receipt of the sufficient called party number information the destination exchange will analyze the called party number to determine to which party the call should be connected. It will also check the called party's line condition and perform various checks, to verify whether or not the connection is allowed. These checks will include correspondence of compatibility checks, e.g. checks associated with supplementary services.
	At this point, certain call set–up information may need to be obtained from an originating or controlling exchange (see § 2.1.6). Examination of the protocol control indicator will show whether end–to–end information is necessary to be obtained before further processing of the call, in this case the SCCP, pass along or information request and information messages can be used.
	In the case where the connection is allowed, the destination exchange will set up a connection to the called party. If a continuity check has to be performed on one or more of the circuits involved in a connection, setting up of the connection to the called party must be prevented until the continuity of such circuits has been verified.
2.1.3	Calling party number
	The calling party number can either be included in the initial address message [§§ 2.1.1.1 c) and 2.1.2.1 c)] or requested by the destination exchange (see § 2.1.6). If the calling party number is required at the destination exchange but is not included in the initial address message, the destination exchange will analyze the protocol control indicator to determine if the request and response should be conducted by one of the procedures in § 3. The destination exchange will investigate the presence/absence or the calling party number parameter to determine whether a request is useful or not. Further it may be necessary to withhold the sending of the address complete message until the calling party number has been successfully delivered.
2.1.4	Address complete message, connect message and call progress message
2.1.4.1	Return of address complete message from destination exchange
	An address complete message will be sent from the destination exchange as soon as it has been determined that the complete called party number has been received, or an indication received from the called party that an inband tone is being connected (for this case see §§ 2.1.5 and 2.2.4). However there is no direct mapping from alerting, received from the access signalling system, to address complete in the network. In the case that the continuity check is performed the destination exchange will withhold sending the address complete message until a successful continuity indication has been received (see § 2.1.9).

	Address complete is sent from the destination exchange in the following conditions:
1)	In the case where the terminating access is non ISDN the following action takes place at the destination exchange:
a)	In all cases an address complete message is sent as soon as it has been determined that the complete called party number has been received, and the destination exchange established that the subscriber is free. Indicators in the address complete message will be set to indicate:
–	call line status: “Subscriber free”
–	ISDN access indicator: “Non ISDN”
b)	In the case of a PBX an address complete message is sent as soon as it has been determined that the called party number has been received. Indicators in the address complete message will be set to indicate:
–	called line status: “No indication”
–	ISDN access indicator: “Non ISDN”.
2)	In the case where the terminating access is ISDN, the following conditions can apply:
a)	If an indication that the address is complete or no status indication has been received from the ISDN access prior to the destination exchange determining that the complete called party number has been received, the indicators in the address complete message will be set as follows:
–	called line status: “No indication”
–	ISDN access indicator: “ISDN”.
	Note – In case a) the indication that the destination user is being alerted is transferred in a call progress message (see § 2.1.5).
b)	The destination exchange concludes from the receipt of an indication from the ISDN access that the complete called party number has been received. In this case the indicators in the address complete message will be set as follows:
–	called line status: “Subscriber free”
–	ISDN access indicator: “ISDN”.
2.1.4.2	Return of connect message from the destination exchange
	If a connect indication is received from the ISDN access under the following conditions:
–	no alerting indication received from the ISDN access and
–	an address complete message has not yet been sent by the destination exchange,
a connect message is sent by the destination exchange. This connect message signifies both address complete and answer conditions.
	Indicators in the connect message will indicate:
–	called line status: “Subscriber free”
–	ISDN access indicator: “ISDN”.
	The destination exchange will through–connect before the connect message is sent.
2.1.4.3	Receipt of address complete message or connect message at an intermediate exchange
	Upon receipt of an address complete message an intermediate exchange will send the corresponding address complete message to the preceding exchange. If a connect message is received at an intermediate exchange instead of an address complete message, a connect message will be sent to the preceding exchange.
2.1.4.4	Receipt of address complete message or the connect message at the originating exchange
a)	When the originating exchange receives an address complete message the appropriate exchange functions take place.
b)	On receipt of an address complete message with the called line status indicator set to “subscriber free” an alerting indication is passed to the calling party if possible.
c)	On receipt of the address complete message the awaiting address complete timer (T7) is stopped and the awaiting answer timer (T9) is started. If timer (T9) expires the connection is released and an indication is sent to the calling subscriber.
d)	If the connect message is received then the appropriate exchange functions take place. The awaiting address complete timer (T7) is stopped (see § 2.1.7.2).
2.1.4.5	Through–connection and awaiting answer indication at the destination exchange
	The sending of the awaiting answer indication (e.g. ring tone) at the destination exchange depends on the type of call. On speech and 3.1 kHz calls and call to an analogue called party the awaiting answer indication is applied to the transmission path to the calling party from the destination exchange on receipt of an alerting indication from the called party or from information contained within the destination exchange that the called party will not or is prohibited from providing inband tone.
	Regardless of whether tones are to be provided or not, the destination exchange will through–connect after the reception of the connection indication from the called party and before sending the answer/connect message to the preceding exchange.
	If the destination exchange does not send the awaiting answer indication because the destination user provides for the sending of tones, then the destination exchange will through–connect the transmission path in the backward direction on receipt of the progress indication.
	The complete through–connection of the transmission path at answer is covered in § 2.1.7.
2.1.4.6	Address complete message with charging information
	The address complete message carries a charge indicator.
2.1.4.7	Address complete message with other information
	Additional information can be included in the address complete messages (e.g. related to supplementary services, see Recommendation Q.730).
2.1.4.8	Return of address complete message in interworking situations
	An address complete message will not be sent until the cross–office check is made, if applicable (see § 2.1.10).
	If the succeeding network does not provide electrical called–party's–line–condition indications the last Signalling System No. 7 exchange shall originate and send an address complete message when the end of address signalling has been determined:
a)	by receipt of an end–of–pulsing (ST) signal; or
b)	by receipt of the maximum number of digits used in the national numbering plan; or
c)	by analysis of the national (significant) number to indicate that a sufficient number of digits has been received to route the call to the called party; or
d)	by receipt of an end–of–selection signal from the succeeding network (e.g. number received signal in Signalling System No. 5); or
e)	exceptionally, if the succeeding network uses overlap signalling and number analysis is not possible, by observing that timer (T10) has elapsed since the last digit was received, and that no fresh information has been received; in such circumstances, transmission to the national network of the last digit received must be prevented until the end of the waiting period which causes an address complete message to be sent backward. In this way, it is ensured that no national answer signal can arrive before an address complete message has been sent.
	If in normal operation, a delay in the receipt of an address complete signal from the succeeding network is expected, the last common channel signalling exchange will originate and send an address complete message 15 to 20 seconds (timer (T11)) after receiving the latest address message. The time–out condition is an upper limit considering the clauses of § 2.9.10.3 (20 to 30 seconds waiting for address complete message timer (T7) for outgoing international exchanges in abnormal release conditions).
2.1.4.9	Return of sub–address information in address complete message, connect message or call progress message
	If sub–address information is received from the called access this information is passed unchanged to the originating exchange in the access transport parameter of the address complete message, connect message or call progress message.
2.1.5	Call progress
	The call progress message is sent (either before or after the address complete message) from an exchange in the backward direction indicating that an event has occurred during call set–up which should be relayed to the calling party.
2.1.5.1	Return of call progress message from the destination exchange
	The call progress message is sent from the destination exchange if the address complete message has been sent and subsequently:
–	an indication is received that the called party is being alerted,
the call progress message contains an event indicator that is set to “alerting”
–	a progress indication is received from the called party,
the call progress message contains an event indicator that is set to “progress”.
	If the indication received from the called party contains a “progress indication”, this is carried by the call progress message in the access transport parameter (transported unchanged across the public network).
	The destination exchange may on receipt of the indication from the called party, that contains an appropriate progress indicator, through–connect the speech path, see § 2.1.4.5.
	In the case of call failure and the connection of a tone or announcement being returned before the address complete message has been returned, see § 2.2.4.
2.1.5.2	Action at an intermediate exchange
	On receipt of a call progress message an intermediate exchange will send the corresponding call progress message to the preceding exchange.
2.1.5.3	Actions at the originating exchange
	On receipt of a call progress message at the originating exchange, no state change occurs (i.e. the awaiting address complete or the awaiting answer timer are not stopped), and the appropriate indication is sent to the calling user. If the call progress message contained information carried in the access transport parameter it is transferred unaltered into the indication returned to the calling user.
2.1.6	Information messages
2.1.6.1	Requesting information
	An information request message may be sent to any exchange in the forward (backward) call establishment direction after sending (receiving) an IAM during call set–up.
2.1.6.2	Sending information
	On sending an information request message a timer (T33) is started. No second information request message may be sent in the same direction until a response information message is received. If the timer (T33) expires before the response message is received, see § 2.10.7. The value of this timer (T33) is 12–15 seconds to allow for a cascade of information request messages, as described in item ii). The response information message may be sent as follows:
i)	if all the information requested is available locally, then an information message containing all the required information is sent in response;
ii)	if all the information is not available locally, but may be available remotely, than an information request message may be sent to a subsequent exchange in the connection in an attempt to extract the information not locally available. (This information request message may be delayed if one has already been sent and the response not yet received.) On receipt of a response, all the information necessary to respond to the original information message is sent in an information message;
iii)	if all the information is not available locally or remotely, then an information message containing only the available information is sent and the requested but not delivered information is indicated as “not available”, using either the indication in the information indicator or an appropriate coding in the requested parameter.
2.1.6.3	Sending unsolicited information
	Information that is available at an exchange and that does not correspond to information which can be or has been requested by an information request message, can be sent in the information message with the solicited information indicator set to signify that the message has been sent unsolicited.
	The unsolicited information message can be used only if the ISDN user part has been used all the way. It can be sent in any direction in any call state (except in the awaiting release complete state).
	Solicited and unsolicited information must not be sent in the same information message; if unsolicited information is to be sent at the same time together with solicited information, this has to be done in a separate message with the solicited information indicator set to “unsolicited”.
2.1.6.4	Receiving an information message
	Upon receipt of an information message which does neither contain the requested information nor an indication that the requested information is not available, the actions taken will depend on whether the call can be progressed.
2.1.7	Answer message
2.1.7.1	Return of answer message from destination exchange
	When the called party answers, the destination exchange connects through the transmission path and the ringing tone is removed if applicable. An answer message to the preceding exchange is sent. If the destination exchange is the exchange controlling charging, then charging may begin.
2.1.7.2	Receipt of answer message at intermediate exchange
	Upon receipt of an answer message, an intermediate exchange sends the corresponding answer message to the preceding exchange and, if this is the exchange controlling charging, charging may begin, and timer (T9) is stopped.
2.1.7.3	Receipt of answer message at originating exchange
	When the originating exchange receives an answer message indicating the required connection has been completed, the transmission path is connected–through in the forward direction, if not already connected. The awaiting answer timer (T9) is stopped. If the originating exchange is the exchange controlling charging, charging may begin if applicable. The calling party is informed.
2.1.7.4	Return of answer from automatic terminals
	When connections are set–up to terminals having an automatic answer feature, the alerting indication may not be received from the called party. If a destination exchange receives an answer indication an answer message is sent provided that an address complete message has been sent, otherwise the connect message is sent.
2.1.7.5	Answer with charging information
	The answer message received from the destination exchange or from a succeeding network carries a charge indicator.
2.1.8	Continuity–check
	Because the signalling in Signalling System No. 7 does not pass over the circuit, facilities should be provided for making a continuity–check of the circuit in the circumstances described below.
	The application of the continuity–check depends on the type of the transmission system used for the circuit.

	For transmission systems having some inherent fault indication features giving an indication to the switching system in case of fault, a continuity–check is not required. However, a per call continuity–check may be needed on fully digital circuits when circuits or bundles of circuits in primary multiplex groups are dropped and inserted en route between switches, and alarm indications carried on bits of the primary multiplex frame structure are lost in passing through an intermediate transmission facility that does not relay them transparently. Typical, per call continuity–checks may be needed when the transmission link between switches contains a TDMA satellite system, a digital circuit multiplication system or a digital access and cross connection system, where fault indications are lost (see Recommendation Q.33).
	When an initial address message is received with a request for a continuity–check relating to a digital circuit having inherent fault indication, one of the following actions is taken:
either	a)	the continuity–check request is disregarded;
or	b)	a continuity–check loop is connected and the maintenance system is alerted. In this case the call may fail since no continuity signal may be received from the distant end.
	Note – The reception of such a request could only be caused by an abnormal condition such as administrative errors or the occurrence of signalling errors.
	When the circuit type is unknown to an SS No. 7 exchange, or in an application where both analogue and digital circuits may be served or when no inherent fault indication is available, a continuity–check loop should always be connected in the following case:
i)	when the exchange has the capability to process initial address messages with continuity–check request and such messages are received;
ii)	when continuity–check request messages are received.
	Means should be provided in SS No. 7 to detect circuit identification code misunderstandings between SS No. 7 exchanges.
	For exchanges having both analogue and digital circuits served by SS No. 7, the continuity–check initiated by a continuity–check request message could be used to test for proper alignment of circuit code identities. On those exchanges, reception of a continuity–check request message should always cause a loop to be attached to the circuit.
	Alternative methods for detection of circuit identity misunderstandings in exchanges with all digital circuits may be employed.
	The continuity–check is not intended to eliminate the need for routine testing of the transmission path.
	The continuity check of the circuit will be done, link–by–link, on a per call basis or by a statistical method prior to the commencement of conversation. Procedures and requirements are specified in Recommendation Q.724, § 7.
	The actions to be taken when pilot supervision is used are described in Recommendation Q.724, § 9.
2.1.9	Special procedures at an interworking point
2.1.9.1	Completion of transmission path at an interworking exchange
	In general, completion of the transmission path at an interworking point should occur as soon as possible during the call set–up phase. The actual point of switch–through will vary depending on the interworking signalling system, e.g. whether inband or outband signalling is used or whether a continuity–check procedure is applied.
	When interworking with other internationally specified signalling systems, the following rules on switch–through should be applied:

SS No. 7 ® SS No. 7	 When no continuity–check is to be made on the outgoing circuit, through–connection should occur after sending the initial address message. When continuity–check is to be made on the outgoing circuit, through–connection should occur after residual check tone has propagated through the return path of the circuit (see Recommendation Q.724, § 7.3).	
 SS No. 6 ® SS No. 7
SS No. 5 ® SS No. 7
R1 ® SS No. 7
SS No. 7 ® SS No. 6	When no continuity–check is to be made on the outgoing circuit, through–connection can occur after sending the initial address message. When a continuity–check is to be made on the outgoing circuit, through–connection can occur after residual check tone has propagated through the return path of the circuit (see Recommendation Q.724, § 7.3).	
 R2 ® SS No. 7	 Through–connection should occur after receipt of address complete.	
 SS No. 7 ® SS No. 5
SS No. 7 ® R1	 Through–connection can occur after sending ST (end of pulsing) signal and removal of a possible check loop.	
 SS No. 7 ® R2	 Through–connection should occur after sending of address complete.	

	When a continuity–check is made on the outgoing circuit, and early connection is made, there is a possibility that the calling party has its go and return paths temporarily looped (from the instant of through–connection to the instant of loop removal of the incoming end of the circuit). This problem can be prevented by using the optional single report continuity–check procedure given in Recommendation Q.724, § 7.3.
2.1.9.2	Alerting of called party
	If in an interworking situation a continuity–check has to be performed on one or more of the circuits involved in the connection preceding the interworking point, appropriate measures must be taken to prevent alerting of the called party until the continuity of such circuits has been verified. Interworking situations which could be discriminated are:
a)	SS No. 7 ® any non No. 7 signalling system.
b)	International SS No. 7 ® national SS No. 7 not performing continuity–check.
	For a) the last digit(s) of the national number have to be withheld in any (interworking) transit exchange or terminating exchange in case of DDI (direct dialling in) or the alerting of the called party is postponed in the terminating exchange in case of non DDI.
	For b) either the last digit(s) of the national number are withheld in the incoming international transit exchange, a transit exchange in the national network or the terminating exchange in case of DDI (direct dialling in) or the setting up of the connection to the called party is postponed in the terminating exchange in case of non DDI.
2.1.10	Cross office check
	For digital exchanges, the requirements mentioned in Recommendation Q.543 shall be met. For other exchanges, Administrations shall ensure the reliability of a connection through a switching machine (cross–office check) either on a per call basis or by a statistical method. With either method, the probability of the connection being established with an unacceptable transmission quality should not exceed 0.00001 as the long–term average.
2.1.11	Charging procedures
2.1.11.1	Basic call charging
	Charging will normally begin when the exchange(s) controlling charging receives the answer or connect message from the network. Optionally an Administration may wish to begin charging prior to the receipt of the answer or connect message for national and/or international calls.

2.1.11.2	Network charging messages (national option)
	When the charging exchange does not have the capability to determine the charge rate for a particular call, charge information may be received during the call set–up. Also, charge rate information may be returned during call set–up, followed subsequently by further charge information messages during the conversation/data phase, should the original rate require to be changed during the call.
2.1.12	Forward transfer message
	The forward transfer message may be sent in telephony semi–automatic working in either of the following two cases:
a)	following a call switched automatically to a subscriber, or following a call established via a special operator, the controlling operator wishes to call in an assistance operator. On receipt of the forward transfer message at the incoming international exchange, an assistance operator is called in;
b)	following a call via codes 11 and 12, the controlling operator wishes to recall the incoming international exchange. Receipt of the forward transfer message at the incoming international exchange recalls the incoming operator on calls completed via the operator positions at the exchange.
2.1.13	Transit network selection (national option)
	If transit network selection information is included in the set–up information from the calling party or is provided on a subscription basis, this information is carried in the transit network selection parameter, and is used for routing of the call, e.g. to a specific carrier.
	A sequence of transit networks may be specified by the calling party, in which case the transit network selection parameter is repeated in the order specified.
2.2	Unsuccessful call set–up
	If at any time in the call set–up the connection cannot be completed a release message is returned. This message contains the reason.
2.2.1	Actions at exchange initiating a release message
	The initiating exchange immediately starts the release of the switched path (if established). The exchange sends a release message to the preceding exchange and a timer (T1) is started to ensure that a release complete message is received from the preceding exchange within time T1 [expiration of timer (T1) is covered in § 2.10.6].
2.2.2	Actions at intermediate exchange
	On receipt of a release message from the succeeding exchange, an intermediate exchange:
i)	immediately start the release of the switched path; when the circuit is reselectable, a release complete message is returned to the succeeding exchange;
ii)	at the same time as the start of the release of the switched path, a release message is sent to the preceding exchange. A timer (T1) is started to ensure that a release complete message is received from the preceding exchange within time T1 (expiration of this time is covered in § 2.10.6).
2.2.3	Actions at the controlling exchange (i.e. the exchange controlling the call)
	On receipt of a release message from the succeeding exchange, the controlling exchange starts the release of the switched path.
	In addition, the controlling exchange will: (if applicable)
a)	return an indication (in band or out band) to the calling party (see § 2.2.4); or
b)	attempt to re–route the call set–up; or
c)	initiate release procedures to the preceding exchange (as described in § 2.2.4).
	In case a) above an indication is carried in the call progress message or address complete message indicating in–band information is available, (see § 2.2.4).
	When the controlling exchange is ready for circuit re–selection, a release complete message is sent to the succeeding exchange.
2.2.4	Tones and announcements
	If a call set–up fails and an in–band tone or announcement has to be returned to the calling party from an exchange or called party, the exchange or user concerned connects the in–band tone to the transmission path.
	If an address complete message has been returned to the preceding exchange a call progress message indicating that in–band tone information is available, is returned to the preceding exchange (see § 2.1.5).
	If an address complete message has not been returned to the preceding exchange already, an address complete message, with the appropriate cause parameter and the “in–band information” indicator set in the optional backward call indicator, will be returned to the originating exchange.
2.3	Normal call release
	The release procedures are based on a two message (release, release complete) approach whereby the release message initiates release of the circuit switched connection.
	The same procedures are used in the network irrespective of whether they are initiated by the calling party, the called party or the network. The normal release procedure can be prevented by the network if this is required on a particular call (§ 2.6).
	To satisfy the need for rapid transfer of release across the network, it is required that the circuit is selectable from the subsequent exchange within the mean cross–office transfer time, Tcu, for simple messages as specified in Recommendation Q.766.
2.3.1	Release initiated by a calling party
a)	Actions at the originating exchange
	On receipt of a request to release the call from the calling party, the originating exchange immediately starts the release of the switched path. A release message is sent to the succeeding exchange and a timer (T1) is started to ensure that a release complete message is received from the succeeding exchange within T1 (expiration of this time is covered in § 2.10.6).
b)	Actions at an intermediate exchange
On receipt of a release message from the preceding exchange, an intermediate exchange:
i)	immediately starts the release of the switched path; when the circuit is reselectable, a release complete message is returned to the preceding exchange;
ii)	at the same time as the start of the release of the switched path, sends a release message to the succeeding exchange. A timer (T1) is started to ensure that a release complete message is received from the succeeding exchange within time T1 (expiration of this time is covered in § 2.10.6).
c)	Actions at the destination exchange
	On receipt of a release message from the preceding exchange, the destination exchange will start the release of the switched path. When the circuit is ready for reselection a release complete message is returned to the preceding exchange.
d)	Charging
	Charging is stopped upon receipt of the release message at the charging exchange or on receipt of a request to release the call from the calling party when the charging exchange is the originating local exchange.
e)	Collision of release messages
	In the case when two points in the connection both initiate the release of a call, a release message may be received at an exchange from a succeeding or preceding exchange after the release of the switched path is initiated. In this case, the exchange will return a release complete message to the exchange from which the concerned release message was received. The release complete message will be sent when the circuit is ready for re–selection.
2.3.2	Release initiated by a called party
	The procedures in § 2.3.1 apply, except that the functions at the originating and destination exchanges are transposed.
2.3.3	Release initiated by the network
	The procedures in § 2.3.1 apply, except that they can be initiated at any exchange (originating, destination or intermediate).
2.3.4	Storage and release of IAM information
	Each exchange of the connection shall store during the call set–up the information contained in the initial address message sent (the originating exchange) or received (intermediate or destination exchange). The information to be stored includes all parameters in the IAM. The contents of the IAM information shall be updated, if the value of parameters change during the call set–up.
	The IAM information can be released from memory:
a)	in the originating exchange when the address complete message or connect message has been received and the calling party does not subscribe to a supplementary service which would cause a new call set–up (e.g. call transfer). The release of the information when the calling party does subscribe to a supplementary service is covered in Recommendation Q.730;
b)	in the intermediate exchange when the address complete message or the connect message has been received;
c)	in the destination exchange when the address complete message or connect message has been sent and the called party does not subscribe to a supplementary service which would cause a new call set–up (e.g. call transfer). The release of the information when the called party does subscribe to a supplementary service is covered in Recommendation Q.730,
and when the call is released earlier and no automatic repeat attempt is to be attempted.
2.4	Transfer of user–to–user information
2.4.1	Requirements for transfer of user–to–user data
	See Recommendation Q.730.
2.5	Suspend, resume
2.5.1	Suspend
	The suspend message indicates a temporary cessation of communication without releasing the call. It can only be accepted during the conversation/data phase. A suspend message can be either generated in response to a suspend request from the calling/called party or generated by the network in response to a clearback indication from an interworking node or an on–hook condition from an analogue called (telephone) party.
2.5.1.1	Suspend initiated by a calling party
	A suspend message is generated in response to a suspend request from a calling party.
a)	Actions at originating exchange
	On receipt of a suspend request from the calling party, the originating exchange sends a suspend message to the succeeding exchange.
b)	Actions at an intermediate exchange
	On receipt of the suspend message from the peceding exchange the intermediate exchange sends a suspend message to the succeeding exchange.
c)	Actions at destination exchange
	On receipt of the suspend message from the preceding exchange, the destination exchange informs the called party that a suspend has been requested.
d)	Actions at the suspend request controlling exchange
	On receipt of the suspend request from a user or the suspend message, the controlling exchange starts a timer (T2) to ensure that a resume request or resume message is received within timer (T2). If the timer (T2) expires, the procedures in § 2.5.3 apply.
2.5.1.2	Suspend initiated by a called party
	The procedures in § 2.5.1.1 apply, except that the functions at the originating and destination exchanges are transposed.
2.5.1.3	Suspend initiated by the network
	A suspend message can be generated by the network in response to a clearback indication from an interworking node or an on–hook condition from an analogue called party.
a)	Action at the terminating exchange (destination) or an interworking exchange
	On receipt of an on–hook condition in the terminating exchange or a clearback signal at the interworking exchange, the exchange may send a suspend (network) message to the preceding exchange.
b)	Action at the intermediate exchange
On receipt of a suspend message the exchange will send a suspend message to the preceding exchange.
c)	Action at the controlling exchange
	On receipt of the on–hook condition or clearback indication or suspend message, the controlling exchange starts a timer (T6) to ensure that an off–hook condition, a re–answer indication, a resume (network) message or a release message is received. The value of this timer (T6) is covered in Recommendation Q.118. If the timer (T6) expires, the procedures in § 2.5.3 apply.
2.5.2	Resume
	A resume message indicates a request to recommence communication. A request to release the call received from the calling or called party will override the suspend/resume sequence and the procedures given in § 2.3 will be followed.
2.5.2.1	Resume initiated by a calling party
	Having initiated a suspend condition, a calling party may request a reconnection within timer T2. The procedures in § 2.5.1.1 items a), b) and c) apply except that the resume message replaces the suspend message. On receipt of the resume message, the controlling exchange cancels the timer (T2).
2.5.2.2	Resume initiated by a called party
	The procedures in § 2.5.2.1 apply except that the functions at the originating and destination exchange are transposed.
2.5.2.3	Resume initiated by the network
	A resume message is initiated by the network, if a suspend message had previously been sent, in response to a re–answer indication from an interworking node or an off–hook condition from an analogue called party.
a)	Action at the terminating exchange or interworking exchange
	On receipt of a re–answer indication at the interworking exchange or an off–hook condition in the terminating exchange, the exchange may send a resume (network) message to the preceding exchange if a suspend (network) message had previously been sent.
b)	Actions of the intermediate exchange
On receipt of a resume message the exchange will send a resume message to the preceding exchange.
c)	Action of the controlling exchange (i.e. exchange controlling the call)
	On receipt of the off–hook condition, re–answer signal, release message or resume message the controlling exchange stops the timer (T6) [started in § 2.5.1.3 c)].
2.5.3	Expiration of timer (T2) or timer (T6)
	If a request for reconnection or a resume message is not received within timer (T2) or timer (T6) covered in Recommendation Q.118 then the controlling exchange will initiate the release procedure outlined in § 2.3.3.
2.6	Delayed release (national option)
	The delayed release message is generated by the network in response to a request from the calling/called party to release the call if the network is applying a hold to the connection. The delayed released message can be sent in either direction.
	The local exchange receiving the release request sends a delayed release message. The connection is split, timer (T3) is started (to prevent network lock–up) and charging is stopped. At the other end of the connection, the delayed release message causes an indication to be sent to the called/calling party.
	Receipt of a connect or reconnection request from the called/calling party during the held state (after the delayed release message has been sent) will not cause the network to set up or resume the connection. When the hold condition is removed or the timer (T3) matures, the network generates the normal release sequence (§ 2.3.3).
2.7	In–call modification
	At the start of the call, it is required to know whether the call is an alternate speech/64 kbit/s or alternate 64 kbit/s/speech unrestricted call request. If this is the case then the following procedures apply:
	Following call set–up the calling or called party may choose to modify the characteristics of the call during the conversation/data phase. During call set–up, the network will have chosen a suitable route (e.g. 64 kbit/s and ISDN user part signalling used all the way) according to information included in the initial address message.
2.7.1	Successful completion
2.7.1.1	Actions required at the exchange originating the call modification
a)	On receipt of a call modification request from the called/calling party, the initiating exchange checks that call modification is allowed and that the necessary resources are available. If acceptable, the resources are reserved and the call modification request message is sent. A timer (T4) is started to ensure that a call modification completed message is received within timer (T4).
b)	On receipt of the call modification complete message, the exchange modifies the resource and, when complete, informs the initiating party that the modification is complete. The timer (T4) is cancelled.
2.7.1.2	Actions required at intermediate exchanges
a)	On receipt of the call modification request message an intermediate exchange checks that the necessary resources are available. If acceptable, the resources are reserved and the call modification request message is passed on to the next exchange.
b)	On receipt of a call modification completed message, the intermediate exchange modifies the resource and, when complete, sends a call modification completed message to the next exchange.
2.7.1.3	Actions required at the local exchange receiving the request call for in–call modification
a)	On receipt of a call modification request message the exchange checks that call modification is allowed and that the necessary resources are available. If acceptable, the resources are reserved and the call modification indication is sent to the called/calling party.
b)	After the calling/called party has changed state and the modification in the local exchange has been completed, a call modification complete message is returned to the network.
2.7.2	Unsuccessful completion
	Basically three cases of unsuccessful completion can be identified:
i)	If the in call modification request fails at an intermediate or at the remote exchange, i.e. because no resources are available or in call modification is not allowed, a call modification reject message is returned in the direction of the exchange originating the in call modification request. The connection is maintained in its current mode.
ii)	If an intermediate exchange or the exchange initiating the call modification request fails to modify the characteristics of the transmission path, the connection is released.
iii)	If at the exchange initiating the call modification request timer (T4) expires, the connection is released.
2.7.2.1	Actions required at the local exchange initiating the call modification
	On receipt of the call modification reject message the exchange keeps the characteristics of the transmission path in the current mode, stops the timer (T4) and informs the initiating party. If resources have been reserved upon reception of the call modification request, they are released.
2.7.2.2	Actions required at an intermediate exchange
	If the in call modification request fails or if the call modification reject message is received by the intermediate exchange the characteristics of the transmission path are kept in the current mode and the call modification reject message is returned in the initiating direction. If resources have been reserved upon reception of the call modification request message, they are released.
	If an intermediate exchange, upon receipt of a call modification complete message, fails to change the characteristics of the transmission path, it initiates the release of the connection in both directions.
2.7.2.3	Action required at the remote local exchange receiving the call modification request from the network
	If at the remote local exchange the in call modification cannot be performed, the characteristics of the transmission path are kept in the current mode and the call modification reject message is returned to the network. If resources have been reserved upon reception of the call modification request message, they are released.
2.8	Echo control procedure
2.8.1	General
	The echo control procedure is used on a per call basis to convey information between exchange nodes about the demand and ability to insert echo control devices.
	The procedure is invoked when a call is to be routed on a connection for which echo control is necessary. It could be initiated at the originating exchange or at an intermediate exchange.
2.8.2	Forward direction
2.8.2.1	Actions at the originating exchange
	If an originating exchange has sufficient information to determine that echo control is necessary for the outgoing circuit then:
–	an outgoing half echo control device is enabled; and
–	the echo control device indicator of the nature of connection indicators parameter field in the IAM is set.
2.8.2.2	Actions at an intermediate exchange
	If an intermediate exchange has sufficient information to determine that echo control is required for the outgoing circuit then one of the following actions can occur:
a)	When the nature of connection indicators parameter field in the IAM indicates that an echo control device is already included:
–	no change to the nature of connection indicators parameter field in the IAM is made;
–	an incoming half echo control device is reserved; and
–	any outgoing half echo control device is disabled.
b)	When the nature of connection indicators parameters in the IAM does not indicate that an echo control device is already included:
–	an outgoing half echo control device is enabled; and
–	the echo control device indicator in the nature of connection indicators parameter field is set.

	If the intermediate exchange has sufficient information to determine that echo control is not required for the outgoing circuit then one of the following actions can occur:
a)	When the nature of connection indicators parameter field in the IAM indicates that an echo control device is already included:
–	no change to the nature of connection indicators parameter field in the IAM is made; and
–	an incoming half echo control device is reserved.
b)	When the nature of connection indicator parameter field in the IAM does not indicate that an echo control device is already included:
–	no additional action is required.
2.8.2.3	Actions at the destination exchange
	See § 2.8.3.1 below.
2.8.3	Backward direction
2.8.3.1	Actions at the destination exchange
	Upon the receipt of an IAM with the indication “outgoing half echo control device included” in the nature of connection indicators parameter field, the following action is taken:
–	an incoming half echo control device is enabled; and
–	the echo control device indicator of the backward call indicators parameter field in the first backward message (i.e. ACM or connect or call progress) is set.
	If the destination exchange is unable to include an incoming half echo control device, the information is conveyed to the preceding exchange by an echo control device indicator in the nature of connection indicators field not being set in the first backward message.
2.8.3.2	Actions at an intermediate exchange
	Upon receipt of the first backward message (i.e. ACM or connect or call progress) in response to an IAM with echo control indication, then one of the following actions can occur:
a)	When the backward call indicators parameter field indicates that an incoming half echo control device is not already included:
–	the reserved incoming half echo control device is included; and
–	the echo control device indicator in the backward call indicators parameter field is set.
b)	When the backward call indicators parameter field indicates that an incoming half echo control device is already included:
–	the reserved incoming half echo control is released; and
–	no change to the backward call indicators parameter field in the backward message is made.
2.8.3.3	Actions at the originating exchange
	No additional action is required.
2.9	Network features
2.9.1	Automatic repeat attempt
	Automatic repeat attempt, as defined in Recommendation Q.12, is provided in Signalling System No. 7. An automatic repeat attempt will be made (up to the point when the initial address message information is released, see § 2.3.4):
i)	on detection of dual seizure (at the non–control exchange) (see § 2.10.1.4);
ii)	on receipt of the blocking message after sending an address message and before any backward message has been received (see § 2.9.2);

iii)	on receipt of a reset circuit message after sending an address message and before a backward message has been received [see § 2.10.3.1 e)];
iv)	on failure of continuity–check, when a continuity check is performed;
v)	on receipt of an unreasonable message during call set up (see § 2.10.5).
2.9.2	Blocking and unblocking of circuits and circuit groups
	The blocking (unblocking) message and the circuit group blocking (unblocking) message are provided to permit the switching equipment or maintenance system to remove from (and return to) traffic the distant terminal(s) of a circuit or group of circuits because of a fault or to permit testing.
	Since the circuits served by the ISDN user part have both–way capability, the blocking message or circuit group blocking message can be originated by either exchange. The receipt of a blocking message or a circuit group blocking message will have the effect of prohibiting non test calls on the relevant circuit(s) outgoing from the exchange until an unblocking message or an appropriate circuit group unblocking message is received, but will not prohibit test calls incoming to that exchange. An acknowledgement sequence is always required for the blocking and unblocking message as well as for the circuit group blocking message and circuit group unblocking messages using the blocking acknowledgement message, the unblocking acknowledgement message, the appropriate circuit group blocking acknowledgement messages and the appropriate circuit group unblocking acknowledgement message respectively. The acknowledgement is not sent until the appropriate action – either blocking or unblocking – has been taken. The release message should not override a blocking message and return circuits to service which might be faulty. The blocked circuit(s) will be returned to service on transmission of the unblocking acknowledgement message or the appropriate circuit group unblocking acknowledgement message at one exchange and on receipt of the unblocking acknowledgement message or the appropriate circuit group unblocking acknowledgement message at the other exchange.
2.9.2.1	Other actions on receipt of a blocking message
	In the event of a blocking message being received, after an initial address message has been sent in the opposite direction on that circuit, and before a backward message relating to that call has been received, an automatic repeat attempt will be made on another circuit. The exchange receiving the blocking message releases the original call attempt in the normal manner after sending the blocking acknowledgement message and will not seize that circuit for subsequent calls.
	If the blocking message is received:
–	after an initial address message has been sent for that circuit in the opposite direction and after at least one backward message relating to that call has been received, or
–	after an intial address message has been received for that circuit beforehand,
the exchange will not seize that circuit for subsequent calls.
	The fact that the circuit is engaged on a call will not delay transmission of the blocking (unblocking) acknowledgement message.
	If a blocking message is sent and subsequently an initial address message is received in the opposite direction, the following action is taken:
–	for test calls, the call should be accepted, if possible. In the case where the test call cannot be accepted, the blocking message must be returned;
–	for calls other than test calls, the blocking message must be returned and the initial address message discarded.
	When a circuit is blocked by use of the blocking message the maintenance system should be informed at both ends of the circuit.
2.9.2.2	Circuit group blocking and unblocking messages
	The following circuit group blocking (unblocking) messages and their corresponding acknowledgement messages are provided:
–	maintenance oriented circuit group blocking (unblocking) message;
–	hardware failure oriented circuit group blocking (unblocking) message;
	The circuits to be blocked (unblocked) are indicated in the status field.
	The maximum number of circuits to be blocked (unblocked) with one circuit group blocking (unblocking) message is limited to 32.
	A received circuit group blocking (unblocking) acknowledgement message has to match in the parameter value of the circuit identification code, the circuit group supervision message type indicator, and the range field (see Recommendation Q.763) with the previously sent group blocking (unblocking) message in order to be considered a valid acknowledgement.
	A circuit is controlled by the ISND user part if it can be used by the ISDN user part as a circuit switched bearer. Hence, time slots in a digital path that are used for synchronisation (e.g. time slot 0 in a 2048 kbit/s digital path) or as signalling channels are not circuits whose control is allocated to the ISDN user part.
	Some of the circuit identification code values covered by the range field of a circuit group blocking (unblocking acknowledgement) message may not be allocated to any circuit. Then the corresponding status bits in the status field are set to 0. This is not allowed for the circuit identification code values related to status bits being set to 1. Those circuit identification code values must always be allocated to circuits whose control is allocated to the ISDN user part. In particular the circuit identification code value indicated in the label of a message must be allocated to a circuit.
	The maintenance oriented circuit group blocking (unblocking) procedures set (remove) the same blocking states as the blocking (unblocking) procedures. This means that a blocking state set by a maintenance oriented circuit group blocking message or indicated as blocked for maintenance purposes in the status field of a circuit group reset acknowledgement message can be removed by an unblocking message. Similarly, a blocking state set by a blocking message can be removed by a maintenance oriented circuit group unblocking message.
	The maintenance blocked state set by maintenance oriented circuit group blocking message, by a status indicator in a circuit group reset acknowledgement message or a blocking message cannot be removed by a hardware oriented circuit group unblocking message.
	The range of circuits to be blocked (unblocked) is indicated in the range field. Those circuits within the range that have to be blocked (unblocked) are indicated in the status field. The same rule applies to the acknowledgements.
	For the circuits blocked for maintenance reasons the same conditions apply and the same actions have to be taken as described in § 2.9.2.1.
	For the circuits seized by ongoing calls or call attempts and blocked for reasons of harware failure the following actions will be taken:
–	all interconnected circuits have to be released by the appropriate messages;
–	the affected circuits are set to the condition “idle hardware blocked” without any exchange of release messages.
	The fact that a circuit is engaged on a call will not delay the transmission of the corresponding circuit group blocking (unblocking) acknowledgement message.
	The hardware blocked state can only be removed by a hardware failure oriented circuit group unblocking message.
	For all instances of circuit group blocking the maintenance system should be notified at both ends of the circuit(s).
2.9.2.3	Abnormal blocking and circuit group blocking procedures
	The following procedures are designed to cover abnormal cases which may occur in the circuit group blocking/unblocking procedures.
i)	If a circuit group blocking message is received relating to remotely blocked circuits then blocking acknowledgement indications for those circuits are given in the status field of the corresponding circuit group blocking acknowledgement message which will be sent in response.
ii)	If a circuit group un unblocking message is received relating to circuits which are not in the state remotely blocked, then unblocking acknowledgement indications for those circuits are given in the status field of the corresponding circuit group unblocking acknowledgement message which will be sent in response.

iii)	When an exchange upon receipt of a circuit group blocking (unblocking) message is not able to give an appropriate blocking (unblocking) acknowledgement indication for each circuit identification code (e.g. because that/those circuit identification code(s) is(are) not allocated to any circuit at the receiving exchange) for which also a blocking (unblocking) indication is given in the status field of the received group blocking (unblocking) message, then no blocking (unblocking) acknowledgement indication relating to that/those circuit identification code(s) will be given in the status field of the corresponding circuit group blocking (unblocking) acknowledgement message which will be sent in response.
iv)	If a circuit group blocking acknowledgement message in response to a circuit group blocking message is received containing in the status field the indications no blocking aknowledgement for the circuits which are to be blocked due to the previously sent circuit group blocking message, then (a) circuit group blocking message(s) will be repeated for the circuits concerned (see § 2.10.4). The same rule applies to the unblocking procedures.
v)	If a circuit group blocking acknowledgement message in response to a circuit group blocking message is received containing in the status field blocking acknowledgement indications for the circuits which are not to be blocked due to the previously sent circuit group blocking message and are not marked locally blocked, then a circuit group unblocking message will be sent for the circuits concerned.
iv)	If a circuit group unblocking acknowledgement message in response to a group unblocking message is received containing in the status field unblocking acknowledgement indications for circuits which are not to be unblocked due to the previously sent circuit group unblocking message and have to remain marked locally blocked, then a circuit group blocking message will be sent for the circuits concerned.
vii)	If a circuit group blocking acknowledgment message which is not expected as an acknowledgent for any circuit group blocking message is received:
–	relating to circuits which all are in the status locally blocked the received circuit group blocking acknowledgement will be discarded;
–	relating to circuits part or all of which are not in the status locally blocked then a circuit group unblocking message will be sent for the relevant circuits.
viii)	If a circuit group unblocking acknowledgement message which is not expected as an acknowledgement for any circuit group unblocking message is received:
–	relating to circuits none of which is in the status locally blocked then the circuit group unblocking acknowledgement message will be discarded;
–	relating to circuits part or all of which are locally blocked then a circuit group blocking message will be sent for the relevant circuits.
ix)	If a circuit group blocking (unblocking) message or a circuit group blocking (unblocking) acknowledgement message refers to status changes for more than 32 circuits the receiving exchange may discard that message.
x)	If a blocking message is received for a blocked circuit, a blocking acknowledgement message will be sent.
xi)	If an unblocking message is received for an unblocked circuit, an unblocking acknowledgement message will be sent.
xii)	If a blocking acknowledgement message, which is not expected as an acknowledgement for a blocking message, is received:
–	relating to a circuit which is locally blocked, the blocking acknowledgement message is discarded;
–	relating to a circuit which is not locally blocked, then an unblocking message will be sent;
xiii)	If an unblocking acknowledgement message, which is not an expected response to an unblocking message, is received:
–	relating to a circuit which is not locally blocked, the received unblocking acknowledgement message is discarded;
–	relating to a circuit which is locally blocked then a blocking message will be sent.
xiv)	If a non test initial address message is received on a remotely blocked circuit, the remotely blocked state of the circuit is removed and the initial address message is processed normally unless the circuit is also locally blocked in which case the initial address message is discarded. This applies to the blocking state whether maintenance, hardware or both. However it should not be the preferred method of unblocking a circuit.