INSTYTUT TELEKOMUNIKACJI
ZAKA
AD SYSTEMÓW TELEKOMUNIKACYJNYCH
ĆWICZENIE LABORATORYJNE
System sygnalizacji nr 7
ZAA

CZNIKI
1. Fragmenty zalecenia Q.762 - Signalling System No. 7 
ISDN User Part general functions of messages and signals
2. Fragmenty zalecenia Q.763 - Signalling system No. 7 
ISDN User Part formats and codes
Warszawa 2003
2
INTERNATIONAL TELECOMMUNICATION UNION
ITU-T
Q.762
TELECOMMUNICATION
(12/1999)
STANDARDIZATION SECTOR
OF ITU
SERIES Q: SWITCHING AND SIGNALLING
Specifications of Signalling System No. 7  ISDN user
part
Signalling System No. 7  ISDN User Part general
functions of messages and signals
ITU-T Recommendation Q.762
(Formerly CCITT Recommendation)
3
Załącznik nr 1  Zalecenie Q.762
Signalling System No. 7  ISDN User Part general functions of messages and signals
1 General (Ogólne)
1.1 Scope
This ITU-T Recommendation describes the elements of signalling information used by the ISDN user part protocol
and their function. The encoding of these elements, the format of the messages in which they are conveyed, and an
indication of whether or not they are for national use, are described in ITU-T Recommendation Q.763 [1].
Table 1 defines the acronyms used for ISDN user part messages.
Table 1/Q.762  ISDN user part message acronyms
Acronym Message (Komunikat)
ACM Address complete
ANM Answer
APM Application transport
BLA Blocking acknowledgement
BLO Blocking
CCR Continuity check request
CFN Confusion
CGB Circuit group blocking
CGBA Circuit group blocking acknowledgement
CGU Circuit group unblocking
CGUA Circuit group unblocking acknowledgement
CON Connect
COT Continuity
CPG Call progress
CRG Charge information
CQM Circuit group query
CQR Circuit group query response
DRS Delayed release (reserved  used in 1988 version)
FAA Facility accepted
FAC Facility
FAR Facility request
FOT Forward transfer
FRJ Facility reject
GRA Circuit group reset acknowledgement
GRS Circuit group reset
IAM Initial address
IDR Identification request
IRS Identification response
INF Information
INR Information request
LPA Loop back acknowledgement
LOP Loop prevention
NRM Network resource management
OLM Overload
PAM Pass-along
PRI Pre-release information
REL Release
RES Resume
RLC Release complete
RSC Reset circuit
SAM Subsequent address
SDM Subsequent directory number
SGM Segmentation
SUS Suspend
UBL Unblocking
UBA Unblocking acknowledgement
UCIC Unequipped circuit identification code
UPA User part available
UPT User part test
USR User-to-user information
4
Załącznik nr 1  Zalecenie Q.762
2 Signalling messages (Komunikaty sygnalizacyjne)
2.1 Address Complete Message (ACM): A message sent in the backward direction indicating that all the address
signals required for routeing the call to the called party have been received.
2.2 Answer message (ANM): A message sent in the backward direction indicating that the call has been answered. In
semi-automatic working, this message has a supervisory function. In automatic working, this message is used in
conjunction with charging information in order to:
 start metering the charge to the calling subscriber (see Recommendation Q.28 [2]); and
 start measurement of call duration for international accounting purposes (see Recommendation E.260 [3]).
2.3 Application Transport message (APM): A message sent in either direction to convey application information
using the Application Transport mechanism.
2.4 Blocking message (BLO): A message sent only for maintenance purposes to the exchange at the other end of a
circuit, to cause an engaged condition of that circuit for subsequent calls outgoing from that exchange. When a
circuit is used in the bothway mode of operation, an exchange receiving the blocking message must be capable of
accepting incoming calls on the concerned circuit unless it has also sent a blocking message. Under certain
conditions, a blocking message is also a proper response to a reset circuit message.
2.5 Blocking Acknowledgement message (BLA): A message sent in response to a blocking message indicating that
the circuit has been blocked.
2.6 Call Progress message (CPG): A message, sent in either direction during the setup or active phase of the call,
indicating that an event, which is of significance, and should be relayed to the originating or terminating access, has
occurred.
2.7 Charge information message (CRG): Information sent in either direction for accounting and/or call charging
purposes.
2.8 Circuit Group Blocking message (CGB): A message sent to the exchange at the other end of an identified group
of circuits to cause an engaged condition of this group of circuits for subsequent calls outgoing from that exchange.
An exchange receiving a circuit group blocking message must be able to accept incoming calls on the group of
blocked circuits unless it has also sent a blocking message. Under certain conditions, a circuit group blocking
message is also a proper response to a reset circuit message.
2.9 Circuit Group Blocking Acknowledgement message (CGBA): A message sent in response to a circuit group
blocking message to indicate that the requested group of circuits has been blocked.
2.10 circuit Group Reset message (GRS): A message sent to release an identified group of circuits when, due to
memory mutilation or other causes, it is unknown whether for example, a release or release complete message is
appropriate for each of the circuits in the group. If at the receiving end a circuit is remotely blocked, reception of
this message should cause that condition to be removed.
2.11 circuit Group Reset Acknowledgement message (GRA): A message sent in response to a circuit group reset
message and indicating that the requested group of circuits has been reset. The message also indicates the
maintenance blocking state of each circuit.
2.12 Circuit Group Unblocking message (CGU): A message sent to the exchange at the other end of an identified
group of circuits to cause cancellation in that group of circuits of an engaged condition invoked earlier by a
blocking or circuit group blocking message.
2.13 Circuit Group Unblocking Acknowledgement message (CGUA): A message sent in response to a circuit group
unblocking message to indicate that the requested group of circuits has been unblocked.
2.14 Circuit group Query Message (CQM): A message sent on a routine or demand basis to request the far-end
exchange to give the state of all circuits in a particular range.
2.15 Circuit group Query Response message (CQR): A message sent in response to a circuit group query message to
indicate the state of all circuits in a particular range.
2.16 Confusion message (CFN): A message sent in response to any message (other than a confusion message) if the
exchange does not recognize the message or detects a part of the message as being unrecognized.
2.17 Connect message (CON): A message sent in the backward direction indicating that all the address signals required
for routeing the call to the called party have been received and that the call has been answered.
2.18 Continuity message (COT): A message sent in the forward direction indicating whether or not there is continuity
on the preceding circuit(s) as well as of the selected circuit to the following exchange, including verification of the
communication path across the exchange with the specified degree of reliability.
2.19 Continuity Check Request message (CCR): A message sent by an exchange for a circuit on which a continuity
check is to be performed, to the exchange at the other end of the circuit, requesting continuity checking equipment
to be attached.
2.20 Facility Accepted message (FAA): A message sent in response to a facility request message indicating that the
requested facility has been invoked.
2.21 Facility message (FAC): A message sent in either direction at any phase of the call to request an action at another
exchange. The message is also used to carry the results, error or rejection of a previously requested action.
2.22 Facility Reject message (FRJ): A message sent in response to a facility request message to indicate that the
facility request has been rejected.
5
Załącznik nr 1  Zalecenie Q.762
2.23 Facility Request message (FAR): A message sent from an exchange to another exchange to request activation of a
facility.
2.24 Forward Transfer message (FOT): A message sent in the forward direction on semi-automatic calls when the
outgoing international exchange operator wants the help of an operator at the incoming international exchange. The
message will normally serve to bring an assistance operator (see Recommendation Q.101 [4]) into the circuit if the
call is automatically set up at the exchange. When the call is completed via an operator (incoming or delay
operator) at the incoming international exchange, the message should preferably cause this operator to be recalled.
2.25 Identification Request message (IDR): A message sent in the backward direction to request action regarding the
malicious call identification supplementary service.
2.26 Identification Response message (IRS): A message sent in response to the identification request message.
2.27 Information message (INF): A message sent to convey information in association with a call, which may have
been requested in an information request message.
2.28 Information Request message (INR): A message sent by an exchange to request information in association with a
call.
2.29 Initial Address message (IAM): A message sent in the forward direction to initiate seizure of an outgoing circuit
and to transmit number and other information relating to the routeing and handling of a call.
2.30 Loop back Acknowledgement message (LPA): A message sent in the backward direction in response to a
continuity check request message indicating that a loop (or transceiver in the case of a 2-wire circuit) has been
connected.
2.31 Loop Prevention message (LOP): A message sent to convey information required by the ECT supplementary
service.
2.32 Network Resource Management message (NRM): A message sent in order to modify network resources
associated with a certain call. The message is sent along an established path in any direction in any phase of the
call.
2.33 Overload Message (OLM): A message sent in the backward direction, on non-priority calls in response to an
IAM, to invoke temporary trunk blocking of the circuit concerned when the exchange generating the message is
subject to load control.
2.34 Pass-Along Message (PAM): A message that may be sent in either direction to transfer information between two
signalling points along the same signalling path as that used to establish a physical connection between those two
points.
2.35 Pre-release Information message (PRI): A message to be used with the Release message for the transport of
information where sending of that information in the Release message itself would cause compatibility problems
with ISUP 1992 and subsequent versions of the ISUP protocol.
2.36 Release message (REL): A message sent in either direction to indicate that the circuit is being released due to the
reason (cause) supplied and is ready to be put into the idle state on receipt of the release complete message. Where
the call is to be redirected the message will also carry the redirection number.
2.37 Release Complete message (RLC): A message sent in either direction in response to the receipt of a release
message, or if appropriate to a reset circuit message, when the circuit concerned has been brought into the idle
condition.
2.38 Reset Circuit message (RSC): A message sent to release a circuit when, due to memory mutilation or other
causes, it is unknown whether for example, a release or a release complete message is appropriate. If, at the
receiving end, the circuit is remotely blocked, reception of this message should cause that condition to be removed.
2.39 Resume message (RES): A message sent in either direction indicating that the calling or called party, after having
been suspended, is reconnected.
2.40 Segmentation Message (SGM): A message sent in either direction to convey an additional segment of an
overlength message.
2.41 Subsequent Directory Number message (SDM): A message that may be sent in the forward direction following
an Initial Address Message, to convey additional called party number information, when the called party number in
the Initial Address Message was contained in the Called Directory Number parameter.
2.42 Subsequent Address Message (SAM): A message that may be sent in the forward direction following an initial
address message, to convey additional called party number information.
2.43 Suspend message (SUS): A message sent in either direction indicating that the calling or called party has been
temporarily disconnected.
2.44 Unblocking message (UBL): A message sent to the exchange at the other end of a circuit to cancel, in that
exchange, the engaged condition of the circuit caused by a previously sent blocking or circuit group blocking
message.
2.45 Unblocking Acknowledgement Message (UBA): A message sent in response to an unblocking message indicating
that the circuit has been unblocked.
2.46 Unequipped Circuit Identification Code message (UCIC): A message sent from one exchange to another when
it receives an unequipped circuit identification code.
2.47 User Part Available message (UPA): A message sent in either direction as a response to a user part test message,
to indicate that the user part is available.
6
Załącznik nr 1  Zalecenie Q.762
2.48 User Part Test message (UPT): A message sent in either direction to test the status of a user part marked as
unavailable for a signalling point.
2.49 User-to-user information message (USR): A message to be used for the transport of user-to-user signalling
independent of call control messages.
3 Signalling parameters (Elementy informacyjne)
3.1 access delivery information: Information sent in the backward direction indicating that a SETUP message was
generated at the destination access.
3.2 access transport: Information generated on the access side of a call and transferred transparently in either
direction between originating and terminating local exchanges. The information is significant to both users and local
exchanges.
3.3 application transport parameter (APP): Information sent in either direction to allow the peer-to-peer
communication of Application Transport mechanism user applications.
3.4 automatic congestion level: Information sent to the exchange at the other end of a circuit to indicate that a
particular level of congestion exists at the sending exchange.
3.5 backward call indicators: Information relating to the characteristics of the connection, signalling path and
called party sent in the backward direction.
3.6 backward GVNS: Information sent in the backward direction used for a GVNS call to convey GVNS related
information.
3.7 call diversion information: Information sent in the backward direction indicating the redirecting reason and the
notification subscription option of the redirecting user.
3.8 call diversion treatment indicators: Information sent in the forward direction concerning treatment of call
diversion.
3.9 call history information: Information sent in the backward direction to indicate the accumulated propagation
delay of a connection.
3.10 call offering treatment indicators: Information sent in the forward direction concerning treatment of call
offering.
3.11 call reference: Circuit independent information identifying a particular call.
3.12 call transfer number: Information sent in both directions to identify each of the users involved in a call
transfer.
3.13 call transfer reference: Information used to convey a reference number associated with the ECT supplementary
service.
3.14 called directory number: Information to indicate the directory number. The directory number is a number in
the national numbering scheme that is allocated to a customer for a telephony service.
3.15 called IN number: Information indicating the number which was received in the SSP as called party number in
IAM and SAM messages.
3.16 called party number: Information to identify the called party.
3.18 calling party number: Information sent in the forward direction to identify the calling party.
3.19 calling party's category: Information sent in the forward direction indicating the category of the calling party
and, in case of semi-automatic calls, the service language to be spoken by the incoming, delay and assistance operators.
3.20 cause indicators: Information sent in either direction indicating the reason for sending the message (e.g. release
message).
3.21 CCNR possible indicator: Information sent in ACM (subscriber free)/CPG (alerting) to indicate the possibility
to invoke a possible succeeding CCNR service request.
3.22 CCSS: Information sent in an initial address message indicating that a call is a CCBS or a CCNR call as
defined in the CCBS or CCNR supplementary service.
3.23 charged party identification: Information identifying the charged party, e.g. the account number.
3.24 circuit assignment map: Information sent in the forward direction to identify the circuits used for an N × 64
kbit/s connection.
3.25 circuit group supervision message type: Information sent in a circuit group blocking or unblocking message,
indicating whether blocking (unblocking) is maintenance oriented or hardware oriented.
3.26 circuit state indicator: Information indicating the state of a circuit according to the sending exchange.
3.27 closed user group interlock code: Information uniquely identifying a closed user group within a network.
3.28 collect call request: Information sent in the forward direction indicating whether or not a call is a collect call.
3.29 conference treatment indicators: Information sent in both directions concerning treatment of a multi-party
call.
3.30 connected number: Information sent in the backward direction to identify the connected party.
3.31 connection request: Information sent in the forward direction on behalf of the signalling connection control
part requesting the establishment of an end-to-end connection.
3.32 continuity indicators: Information sent in the forward direction indicating whether or not the continuity check
on the outgoing circuit was successful. A continuity check successful indication also implies continuity of the preceding
circuits and successful verification of the path across the exchange with the specified degree of reliability.
7
Załącznik nr 1  Zalecenie Q.762
3.33 correlation id: Information used by the SCF for correlation with a previous connection (see ITU-T
Recommendations Q.1218 [5] and Q.1228 [6]  Definition of common data types).
3.34 display information: Information sent in either direction indicating a text string to be sent to the user.
3.35 echo control information: Indicators used to request activation and deactivation of echo control devices, and to
respond to such requests.
3.36 end of optional parameters: The end of optional parameters field indicates that there are no more optional
parameters in the message.
3.37 event information: Information indicating the type of event which caused a call progress message to be sent.
3.38 facility indicator: Information sent in facility related messages identifying the facility or facilities with which
the message is concerned.
3.39 forward call indicators: Information relating to the characteristics of the connection, signalling path and
calling party sent in the forward direction.
3.40 forward GVNS: Information sent in the forward direction used for a GVNS call to convey GVNS related
information.
3.41 generic digits: Digit information, which is not suitable to be sent within numbering address parameter, sent in
either direction to convey information between exchanges due to supplementary service.
3.42 generic notification: Information sent in either direction intended to provide supplementary service notification
to a user.
3.43 generic number: Number information sent in either direction to enhance network operation or for
supplementary services.
3.44 generic reference: (not used in the 1997 and subsequent versions of the ISUP Recommendations).
3.45 hop counter: Information sent in the forward direction to minimize the impact of looping. The initial count
determines the maximum number of contiguous ISUP interexchange circuits that are allowed to complete the call,
assuming all subsequent intermediate exchanges decrement the hop counter.
3.47 information indicators: Information identifying the optional parameters included in a message.
3.48 information request indicators: Information identifying the optional parameters requested in a message.
3.49 location number: Information sent to identify the geographical area (e.g. region, country, city, etc.) of the
origin of a call. It is primarily intended to provide services for mobile originated calls.
3.50 loop prevention indicators: Information sent in association with a request (or response to a request) when the
loop prevention procedure is performed in the ECT supplementary service.
3.51 MCID request indicator: Information sent in the backward direction to request the identity of the calling party
for the purpose of malicious call identification.
3.52 MCID response indicator: Information sent in the forward direction to respond to a MCID request and
indicating whether or not the MCID information is available.
3.53 message compatibility information: Information sent in either direction indicating how an exchange should
react in case this message is unrecognized.
3.54 MLPP precedence: Information relating specifically to the multilevel precedence and pre-emption service.
3.55 nature of connection indicators: Information relating to the transmission path used on a connection.
3.56 network management controls: Information sent in the forward direction concerning network management
related action for a call.
3.57 network routeing number: Information to indicate the network routeing number. The network routeing
number is a number used by the network to route a call.
3.58 network specific facility: Service related information transparently transferred in either direction between the
local exchange and the identified network which contracts the service. The information is significant to both user and the
identified network.
3.59 number portability forward information: Information sent in the forward direction concerning treatment of
number portability.
3.60 optional backward call indicators: Information relating to the characteristics of the connection, signalling path
and called party sent in the backward direction.
3.61 optional forward call indicators: Information relating to the characteristics of the connection, signalling path
and called party sent in the forward direction.
3.62 original called number: Information sent in the forward direction when a call is redirected and identifies the
original called party.
3.63 original called IN number: Information sent in the forward direction indicating the original called IN number,
if multiple IN interactions have taken place.
3.65 parameter compatibility information: Information sent in either direction indicating how an exchange should
react in case the parameter is unrecognized.
3.74 range and status: Information sent in a circuit group supervision message (e.g. circuit group blocking) to
indicate the range and status of circuits affected by the action in the message.
8
Załącznik nr 1  Zalecenie Q.762
3.84 remote operations: The Remote Operations parameter is used to indicate the invocation of a supplementary
service identified by an operation value and also carry the result or error indications depending on the outcome of the
operation.
3.85 SCF id: Information indicating the SCF identifier (see ITU-T Recommendations Q.1218 [5] and Q.1228 [6] 
Definition of common data types).
3.86 service activation: Information sent in either direction to indicate the invocation, acceptance or rejection of
supplementary services, when no service associated parameter is to be sent.
3.87 signalling point code: Information sent to identify the signalling point in which an event occurred.
3.88 subsequent number: Additional called party address digits sent subsequent to the sending of the called party
number parameter.
3.89 suspend/resume indicators: Information sent in the suspend and resume messages to indicate whether
suspend/resume was initiated by an ISDN subscriber or by the network.
3.90 transit network selection: Information sent in the initial address message indicating the transit network
requested to be used in the call.
3.91 transmission medium requirement: Information sent in the forward direction indicating the type of
transmission medium required for the connection (e.g. 64 kbit/s unrestricted, speech).
3.92 transmission medium requirement prime: Information sent in the forward direction indicating the fallback
connection type in case of fallback.
3.93 transmission medium used: Information sent in the backward direction indicating a resulting fallback
connection type used for a call after fallback has occurred.
3.94 UID action indicators: Information sent in the backward direction to instruct preceding exchanges to enable a
user interactive dialogue to occur.
3.95 UID capability indicators: Information sent in the forward direction to inform succeeding exchanges that on
request a user interactive dialogue is possible.
3.96 user service information: Information sent in the forward direction indicating the bearer capability requested
by the calling party.
3.97 user service information prime: Information sent in the forward direction indicating the additional bearer
capability requested by the calling party.
3.98 user teleservice information: Information sent in the initial address message indicating the Higher Layer
Compatibility information requested by the calling party.
3.99 user-to-user indicators: Information sent in association with a request (or response to a request) for
user-to-user signalling supplementary service(s).
3.100 user-to-user information: Information generated by a user and transferred transparently through the
interexchange network between the originating and terminating local exchanges.
4 Parameter information
4.1 access delivery indicator: Information sent in the backward direction indicating that a SETUP message was
generated at the destination access.
4.2 address presentation restricted indicator: Information sent in either direction to indicate that the address
information is not to be presented to a public network user, but can be passed to another public network. It may also be
used to indicate that the address cannot be ascertained.
4.3 address signal: An element of information in a network number. The address signal may indicate digit values 0
to 9, code 11 or code 12. One address Signal Value (ST) is reserved to indicate the end of the called party number.
4.4 altitude: Information that indicates the geodetic location of the calling party in terms of distance above or below
the WGS-84 ellipsoid surface.
4.5 altitude sign: Information that indicates the geodetic location of the calling party in terms of above or below the
WGS-84 ellipsoid surface.
4.6 altitude uncertainty code: Information indicating the level of uncertainty inherent to the associated altitude
information.
4.7 APM Segmentation indicator: Information sent in either direction to indicate the number of remaining
segments carrying information using the APM mechanism that will be forwarded.
4.8 application context identifier: A value that uniquely identifies the application using the application transport
mechanism.
4.10 binary code: A code allocated to a closed user group administered by a particular ISDN or data network.
4.11 call diversion may occur indicator: Information sent in the backward direction indicating that call diversion
may occur, depending on the response received (or lack thereof) from the called party.
4.12 call identity: Information sent in the call reference parameter indicating the identity of a call in a signalling
point.
4.13 call to be diverted indicator: Information sent in the forward direction indicating whether diverting of the call
shall be accepted.
4.14 call to be offered indicator: Information sent in the forward direction indicating whether the call shall be
offered if the access is marked with call offering restrictions.
9
Załącznik nr 1  Zalecenie Q.762
4.15 called party's category indicator: Information sent in the backward direction indicating the category of the
called party, e.g. ordinary subscriber or payphone.
4.16 called party's status indicator: Information sent in the backward direction indicating the status of the called
party, e.g. subscriber free.
4.17 calling party address request indicator: Information sent in the backward direction indicating a request for the
calling party address to be returned.
4.18 calling party address response indicator: Information sent in response to a request for the calling party
address, indicating whether the requested address is included, not included, not available or incomplete.
4.19 calling party's category request indicator: Information sent in the backward direction indicating a request for
the calling party's category to be returned.
4.20 calling party's category response indicator: Information sent in response to a request for the calling party's
category, indicating whether or not the requested information is included in the response.
4.21 cause value: Information sent in either direction indicating the reason for sending the message (e.g. release
message). Definitions for each cause value are defined in ITU-T Recommendation Q.850 [8].
4.24 charge indicator: Information sent in the backward direction indicating whether or not the call is chargeable.
4.25 charge information request indicator: Information sent in either direction requesting charge information to be
returned.
4.26 charge information response indicator: Information sent in response to a request for charge information
indicating whether or not the requested information is included.
4.27 circuit identification code: Information identifying the physical path between a pair of exchanges.
4.28 closed user group call indicator: Information indicating whether or not the concerned call can be set up as a
closed user group call and, if a closed user group call, whether or not outgoing access is allowed.
4.29 coding standard: Information sent in association with a parameter (e.g. cause indicators) identifying the
standard in which the parameter format is described.
4.33 confidence: Information identifying the confidence by which it is known that the calling party lies within the
associated shape description.
4.34 conference acceptance indicator: Information sent in both directions indicating whether a request for a
multi-party call, i.e. conference or three-party call, shall be accepted.
4.35 connected line identity request indicator: Information sent in the forward direction indicating a request for the
connected party number to be returned.
4.36 continuity check indicator: Information sent in the forward direction indicating whether or not a continuity
check will be performed on the circuit(s) concerned or is being (has been) performed on a previous circuit in the
connection.
4.40 diagnostic: Information sent in association with a cause and which provides supplementary information about
the reason for sending the message.
4.41 discard message indicator: Information sent to inform another node to discard the related message, due to
compatibility reasons.
4.42 discard parameter indicator: Information sent to inform another node to discard the related parameter, due to
compatibility reasons.
4.43 echo control device indicator: Information indicating whether or not an echo control device is included in the
connection.
4.48 encapsulated application information: Application information required to be transported by the application
transport mechanism.
4.49 encoding scheme: Information sent to indicate the coding type for the digit information, e.g. BCD-coded.
4.50 end-to-end information indicator: Information sent in either direction indicating whether or not the sending
exchange has further call information available for end-to-end transmission. In the forward direction, an indication that
end-to-end information is available will imply that the destination exchange may obtain the information before alerting
the called party.
4.51 end-to-end method indicator: Information sent in either direction indicating the available methods, if any, for
end-to-end transfer of information.
4.52 error code: The Error code element contains the reason why an operation cannot be completed successfully. It
is present only in a Return Error component. As with operations, errors may be local or global. These errors and
associated parameters are defined in relevant supplementary service specifications.
4.53 event indicator: Information indicating the type of event which caused a call progress message to be sent.
4.54 event presentation restricted indicator: Information sent in the backward direction indicating that the event
should not be presented to the calling party.
4.55 extension indicator: Information sent in every octet in a multi-octet parameter field with variable length,
indicating whether the octet is the last one or is followed by another one.
10
Załącznik nr 1  Zalecenie Q.762
4.57 feature code: Information sent in either direction to invoke, accept, or reject a specific action for a
supplementary service.
4.58 filler: A number of bits used to complete a partially used octet to full octet length. Mainly the filler is used in
number parameters that are carrying odd number of digits, where the remaining four bits in the last octet have no digit
information.
4.59 holding indicator: Information sent in the backward direction indicating that holding of the connection is
requested.
4.60 hold provided indicator: Information sent in the forward direction indicating that the connection will be held
after the calling or called party has attempted to release.
4.61 in-band information indicator: Information sent in the backward direction indicating that in-band information
or an appropriate pattern is now available.
4.62 included angle: Information identifying the included angle of a circle sector.
4.63 incoming echo control device request indicator: Information sent to request the activation or deactivation of
an incoming echo control device.
4.64 incoming echo control device information indicator: Information sent to inform whether an incoming echo
control device has been included or not and, if not, whether the device is available or not.
4.66 internal network number: Information sent to the destination exchange for specific numbers, e.g. roaming
numbers indicating whether or not the number contained in the parameter is generated by the network.
4.67 interworking indicator: Information sent in either direction indicating whether or not Signalling System No. 7
is used in all parts of the network connection.
4.68 interworking to redirection indicator: Information used to indicate whether interworking from pivot routeing
to redirection is allowed.
4.69 invoke ID: An Invoke ID is used as a reference number to identify uniquely an operation invocation. It is
present in the Invoke component and in any reply to the Invoke (Return Result, Return Error or Reject), enabling the
reply to be correlated with the invoke.
4.70 invoking pivot reason: Information sent in the pivot routeing backward information parameter or the pivot
routeing forward information parameter that conveys the reason for invoking the pivot function.
4.71 invoking redirect reason: Information sent in the redirect backward information parameter or the redirect
forward information parameter that conveys the reason for invoking the redirection function.
4.72 ISDN access indicator: Information sent in either direction indicating whether or not the access signalling
protocol is ISDN.
4.73 ISDN user part indicator: Information sent in either direction to indicate that the ISDN user part is used in all
preceding parts of the network connection. When sent in the backward direction, the preceding parts are those towards
the called party.
4.74 ISDN user part preference indicator: Information sent in the forward direction indicating whether or not the
ISDN user part is required or preferred in all parts of the network connection.
4.75 length (of each component or of an information element): Binary coded information indicating the number of
octets in a component or information element. The value does not include the parameter name, length or end of optional
parameters octets.
4.76 linked ID: A Linked ID is included in an Invoke component by a node when it responds to an operation
invocation with a linked operation invocation. The node receiving the Linked ID uses it for correlation purposes in the
same way that it uses the Invoke ID in Return Result, Return Error and Reject components.
4.77 local reference: Information sent in the connection request, indicating the local reference allocated by the
signalling connection control part to an end-to-end connection.
4.78 latitude sign: Information that indicates the geodetic location of the calling party in terms of northern or
southern Hemisphere.
4.79 location: Information sent in either direction indicating where an event (e.g. release) was generated. Definition
of each location value is given in ITU-T Recommendation Q.850 [8].
4.80 location presentation restricted indicator: Information that indicates that the geodetic location information is
not to be presented to a public network user, but can be passed to another public network. It may also be used to indicate
that the geodetic location cannot be ascertained.
4.81 Look For Busy (LFB): Information sent in the forward direction to indicate whether the LFB option is allowed
or if the path for the call is reserved.
4.82 major radius: Information identifying the size of the major axis of an ellipse on the ellipsoid shape description.
4.83 minor radius: Information identifying the size of the minor axis of an ellipse on the ellipsoid shape description.
4.84 MLPP service domain: Information sent in the forward direction to identify the specific MLPP service domain
subscribed to by the calling user.
4.85 MLPP user indicator: Information sent in the backward direction to indicate that the called user is an MLPP
user.
4.86 more instruction indicators: Octets reserved for future use for enhancement of the instruction indicators.
4.87 national/international call indicator: Information sent in the forward direction indicating in the destination
national network whether the call has to be treated as an international call or as a national call.
11
Załącznik nr 1  Zalecenie Q.762
4.88 nature of address indicator: Information sent in association with an address indicating the nature of that
address, e.g. ISDN international number, ISDN national significant number, or ISDN subscriber number.
4.89 network discard indicator: This indicator indicates that user-to-user information included in the call control
message has been discarded by the network.
4.90 network identification plan: Information sent to indicate the identification plan for identifying the network,
e.g. ITU-T Recommendation X.121 [10] or E.212 [11] (DNIC or MNIC).
4.91 network identification: Information sent to identify a network.
4.92 network identity: Information sent to identify the network which administers the supplementary service.
4.93 network specific facility indicator: Information identifying specific facilities requested or provided.
4.94 notification indicator: Information sent in either direction intended to provide supplementary service
notification to a user.
4.95 notification subscription option: Information sent in the backward direction indicating that the diversion with
or without redirection number can be presented to the calling user.
4.96 Nth upgraded parameter name: Information identifying the Nth parameter which has been upgraded for
compatibility purposes.
4.97 number incomplete indicator: Information sent to indicate whether the delivered number is complete or
incomplete.
4.98 number portability status indicator: Information sent in the forward direction identifying whether number
portability checks have taken place at an exchange in the call path and also whether the called number is ported or non-
ported.
4.99 number qualifier indicator: Information sent in association with a generic number, qualifying the number that
is transferred, e.g. a network specific number or a number related to a specific supplementary service.
4.100 numbering plan indicator: Information sent in association with a number indicating the numbering plan used
for that number (e.g. ISDN number, Telex number).
4.101 odd/even indicator: Information sent in association with an address, indicating whether the number of address
signals contained in the address is even or odd.
4.103 operation code: The Operation code element indicates the precise operation to be invoked, and is present in an
Invoke component type. It is also present in the Return Result component if the result contains parameters. The operation
may be a local operation or a global operation. A local operation can be used in one ASE only. The same global
operation can be used in several different ASEs. The actual operation codes, the definition of the operations and their
associated parameters, are defined in relevant supplementary service specifications.
4.104 orientation: Information identifying the orientation of an ellipse on the ellipsoid.
4.105 original redirection reason: Information sent in either direction indicating the reason why the call was
originally redirected.
4.106 originating participating service provider identification: Information sent in the forward direction that
uniquely identifies the participating service provider that provides customer access to GVNS to the calling user/interface.
4.107 outgoing echo control device request indicator: Information sent to request the activation or deactivation of
an outgoing echo control device.
4.108 outgoing echo control device information indicator: Information sent to inform whether an outgoing echo
control device has been included or not and, if not, whether the device is available or not.
4.109 parameter tag: Information identifying the type of parameter used in remote operations.
4.110 pass on not possible indicator: Information sent to inform another node on what action to take if "pass on" was
requested due to compatibility reason but "pass on" was not possible due to interworking with pre-ISUP 1992 signalling.
4.111 performing pivot indicator: Information sent in the pivot routeing forward informauion parameter that
indicates a willingness to perform the pivot function for a particular reason.
4.112 performing redirect indicator: Information sent in the redirect forward information parameter that indicates a
willingness to perform redirection for a particular reason.
4.116 precedence level: Information sent in the forward direction to indicate the priority of the call.
4.117 problem code: The Problem code element used in remote operations contains the reason for the rejection of a
component and one such element is present in a Reject component. Four problem code elements are defined, viz.:
a) General Problem
This element contains one of the problem codes which apply to the Remote Operation capability of ISUP
in general and which do not relate to any specific component type. All of these are generated by the Remote
Operation capability of ISUP. They are:
 Unrecognized Component:
The component type is not recognized as being one of those defined in 4.118 describing component
types.
 Mistyped Component:
The elemental structure of a component does not conform to the structure of that component as
defined in ITU-T Recommendation Q.763 [1].
 Badly Structured Component:
12
Załącznik nr 1  Zalecenie Q.762
The contents of the component do not conform to the encoding rules defined in ITU-T
Recommendation Q.763 [1].
b) Invoke problem
This element contains one of the problem codes that relate only to the Invoke component type. They are:
 Duplicate Invoke ID:
The Invoke ID is already in use by a previously invoked operation.
 Unrecognized operation:
The operation code value is not one of those used by the ASE.
 Mistyped Parameter:
Signifies that the t{pe of invoke parameter is not that agreed between the users.
 Resource Limitation:
Sufficient resources are not available to perform the requested operation.
 Initiating Release:
The requested operation cannot be invoked because the association is about to be released.
 Unrecognized Linked ID:
The Linked ID does not correspond to a previously invoked operation.
 Linked Response Unexpected:
The operation referred to by the Linked ID is not an operation for which linked invokes are allowed.
 Unexpected Linked Operation:
The operation referred to by the Linked ID does not allow this linked operation.
c) Return Result Problem
This element contains one of the problem codes that relate only to the Return Result component type.
They are:
 Unrecognized Invoke ID:
No operation with the specified Invoke ID is in progress.
 Return Result Unexpected:
The invoked operation does not report success.
 Mistyped Parameter:
Signifies that the type of Return Result parameter is not that agreed between the users.
d) Return Error Problem
This element contains one of the problem codes that relate only to the Return Error component type. They
are:
 Unrecognized Invoke ID:
No operation with the specified Invoke ID is in progress.
 Return Error Unexpected:
The invoked operation does not report failure.
 Unrecognized Error:
The reported error is not one of those defined for the invoked operation.
 Unexpected Error:
The received error is not one of those that the invoked operation may report.
 Mistyped Parameter:
Signifies that the type of Error parameter is not that agreed between the users.
4.118 protocol class: Information indicating the protocol class requested by the signalling connection control part for
the end-to-end connection.
4.119 protocol profile: Information sent in either direction to indicate the protocol used in the Remote Operations
parameter.
4.120 protocol control indicator: Information consisting of the end-to-end method indicator, the interworking
indicator, the end-to-end information indicator, the SCCP method indicator and the ISDN user part indicator sent in
either direction to describe the signalling capabilities within the network connection.
4.122 range: Information sent in a circuit group supervision message (e.g. circuit group blocking) to indicate the range
of circuits affected by the action in the message.
4.123 redirect possible indicator: Information sent in the forward direction to indicate that at least one exchange in
the connection is able to redirect the call and the call states in which the procedure is possible.
4.124 redirecting indicator: Information sent in either direction indicating whether the call has been diverted or
rerouted and whether or not presentation of redirection information to the calling party is restricted.
4.125 redirecting reason: Information sent in either direction indicating, in the case of calls undergoing redirection,
the reason why the call has been redirected.
4.126 redirection counter: Information sent in either direction indicating the number of redirections which have
occurred on a call.
13
Załącznik nr 1  Zalecenie Q.762
4.127 release call indicator: Information sent to inform another node to release the call or not, by compatibility
reasons, if the related message or parameter is unrecognized.
4.128 return to invoking exchange call identifier: Information used by the return to invoking exchange function to
identify a call.
4.129 return to invoking exchange duration: Information sent in the backward direction to indicate how long
information will be retained at the invoking exchange to facilitate the return to invoking exchange function.
4.130 return to invoking exchange possible: Information sent in the forward direction to indicate the capability to
make use of the return to invoking exchange call identifier and return to invoking exchange duration.
4.132 satellite indicator: Information sent in the forward direction indicating the number of satellite circuits in the
connection.
4.133 SCCP method indicator: Information sent in either direction indicating the available SCCP methods, if any,
for end-to-end transfer of information.
4.134 screening indicator: Information sent in either direction to indicate whether the address/location information
was provided by the user or network.
4.135 segmentation local reference (SLR): A unique value to a call used to associate segments in an APM
segmentation procedure.
4.136 send notification indicator: Information sent to inform another node to send notification, due to compatibility
reason, if the related message or parameter is unrecognized.
4.137 sequence: The sequence is an ordered set used in remote operations.
4.138 sequence indicator: Used to indicate the beginning (first segment) of an APM segmentation procedure
sequence.
4.139 set: The Set element is used in remote operations to contain a set of information elements accompanying a
component. It is required in the case of more than one information elements being included in a component. The
information elements themselves are defined in relevant supplementary service specifications.
4.140 shape description: Information that describes the geodetic location of the calling party.
4.141 signalling point code: Information identifying the signalling point.
4.142 simple segmentation indicator: Information sent in either direction to indicate that additional information will
be forwarded in a segmentation message (unsolicited).
4.143 solicited information indicator: Information sent in an information message to indicate whether or not the
message is a response to an information request message.
4.144 status: Information sent in a circuit group supervision message (e.g. circuit group blocking) to indicate the
specific circuits, within the range of circuits stated in the message, that are affected by the action specified in the
message.
4.147 temporary alternative routeing indicator: Information sent in the forward direction indicating that a call is a
temporary alternative routeing controlled call.
4.148 terminating access indicator: Information sent in the backward direction that identifies the type of terminating
access from a GVNS terminating participating service provider actually used to complete the call.
4.149 terminating network routeing number: A number sent in the forward direction which a terminating functional
entity may use to complete a GVNS call to on-net locations.
4.150 through connection indicator: Information sent in the forward direction to inform succeeding exchanges that
on request through-connection of the transmission path in both directions is possible.
4.151 through connection instruction indicator: Information sent in the backward direction to instruct preceding
exchanges to through-connect the transmission path in both directions.
4.152 transit at intermediate exchange indicator: Information sent to inform a transit node (type B), whether it shall
react on the rest of the instruction indicators or not, if the related message or parameter is unrecognized.
4.153 type: Information sent in either direction to indicate whether the message is a request or a response.
4.155 type of network identification: Information sent to inform whether the identification of a network is by ITU-T
standardization identification or by national network identification.
4.156 type of shape: Information that indicates the format of the geodetic location information held in the associated
shape description.
14
Załącznik nr 2  Zalecenie Q.763
INTERNATIONAL TELECOMMUNICATION UNION
ITU-T
Q.763
TELECOMMUNICATION
(12/1999)
STANDARDIZATION SECTOR
OF ITU
SERIES Q: SWITCHING AND SIGNALLING
Specifications of Signalling System No. 7  ISDN user
part
Signalling system No. 7  ISDN user part formats and
codes
ITU-T Recommendation Q.763
(Formerly CCITT Recommendation)
15
Załącznik nr 2  Zalecenie Q.763
Signalling System no. 7  ISDN User Part formats and codes
1. Summary
This Recommendation specifies the formats and codes of the ISDN user part messages and parameters
required to support basic bearer services and supplementary services.
1.0.1 Scope
This Recommendation specifies the formats and codes of the ISDN user part messages and parameters
required to support basic bearer services and supplementary services.
1.0.5 General coding principles
ISDN user part messages are carried on the signalling link by means of message signal units the format of
which is described in Subclause 2.2/Q.703.
The format of and the codes used in the service information octet are described in Subclause 14.2/Q.704. The
service indicator for the ISDN user part is coded 0101.
The signalling information field of each message signal unit containing an ISDN user part message consists
of an integral number of octets and encompasses the following parts (see Figure 1):
a) routeing label;
b) circuit identification code;
c) message type code;
d) the mandatory fixed part;
e) the mandatory variable part;
f) the optional part, which may contain fixed length and variable length parameter fields.
NOTE  The service information octet, the routeing label and circuit identification code are not included in the SCCP user
data parameter transferred between the ISDN user part and signalling connection control part.
Routeing label
Circuit identification code
Message type code
Mandatory fixed part
Mandatory variable part
Optional part
Figure 1/Q.763  ISDN user part message parts
A description of the various message parts is given in the following subclauses.
1.2 Circuit identification code (Kod łącza rozmównego)
The format of the Circuit Identification Code (CIC) is shown in Figure 2.
87654321
1 Circuit identification code (CIC) lsb
2spare msb
Figure 2/Q.763  Circuit identification field
The allocation of circuit identification codes to individual circuits is determined by bilateral agreement and/or
in accordance with applicable predetermined rules.
For international applications, the four spare bits of the circuit identification field are reserved for CIC
extension, provided that bilateral agreement is obtained before any increase in size is performed. For national
applications, the four spare bits can be used as required.
Allocations for certain applications are defined below:
a) 2048 kbit/s digital path
 16 
Załącznik nr 2  Zalecenie Q.763
For circuits which are derived from a 2048 kbit/s digital path (Recommendations G.732 and G.734) the
circuit identification code contains in the 5 least significant bits a binary representation of the actual
number of the time slot which is assigned to the communication path.
The remaining bits in the circuit identification code are used, where necessary, to identify these circuits
uniquely among all other circuits of other systems interconnecting an originating and destination point.
b) 8448 kbit/s digital path
For circuits which are derived from a 8448 kbit/s digital path (Recommendations G.744 and G.747) the
circuit identification code contains in the 7 least significant bits an identification of the circuit which is
assigned to the communication path. The codes in Table 1 are used.
The remaining bits in the circuit identification code are used, where necessary, to identify these circuits
uniquely among all other circuits of other systems interconnecting an originating and destination point.
c) Frequency Division Multiplex (FDM) systems in networks using the 2048 kbit/s pulse code modulation
standard
For frequency division multiplex systems existing in networks that also use the 2048 kbit/s pulse code
modulation standard, the circuit identification code contains in the 6 least significant bits the
identification of a circuit within a group of 60 circuits carried by 5 basic frequency division multiplex
groups which may or may not be part of the same supergroup. The codes in Table 2 are used.
The remaining bits in the circuit identification code are used, where necessary, to identify these circuits
uniquely among all other circuits of other systems interconnecting an originating and destination point.
d) For a multirate connection type call, the CIC used in call connection messages shall be that of the
lowest numbered CIC of the circuits used in the multirate connection types. Where the circuits used are
derived from a 2048 kbit/s digital path, they shall be in fixed groups of contiguous time slots
(excluding time slot 0 and 16), in accordance with Table 3 (Part 1).
e) For the N × 64 kbit/s connection types, circuits used may be either contiguous or non-contiguous. In a
2048 kbit/s digital path, the N can be a value from 2 to 30. In a 1544 kbit/s digital path, the N can be a
value from 2 to 24.
NOTE  At an international interface with inflexible mapping between the 2048 kbit/s and 1544 kbit/s digital
paths, the circuits used shall be in a fixed group of contiguous time slots in accordance with Table 3 (Part 2) per
bilateral agreement.
1.3 Message type code (Kody komunikatów)
The message type code consists of a one-octet field and is mandatory for all messages. The message type
code uniquely defines the function and format of each ISDN user part message.
The allocation with reference to the appropriate descriptive tables in this Recommendation is summarized in
Table 4.
Table 4/Q.763
Reference
Message type Code
(Table)
Address complete 21 0 0 0 0 0 1 1 0
Answer 22 0 0 0 0 1 0 0 1
Application transport 51 0 1 0 0 0 0 0 1
Blocking 39 0 0 0 1 0 0 1 1
Blocking acknowledgement 39 0 0 0 1 0 1 0 1
Call progress 23 0 0 1 0 1 1 0 0
Circuit group blocking 40 0 0 0 1 1 0 0 0
Circuit group blocking acknowledgement 40 0 0 0 1 1 0 1 0
Circuit group query (national use) 41 0 0 1 0 1 0 1 0
Circuit group query response (national use) 24 0 0 1 0 1 0 1 1
Circuit group reset 41 0 0 0 1 0 1 1 1
Circuit group reset acknowledgement 25 0 0 1 0 1 0 0 1
Circuit group unblocking 40 0 0 0 1 1 0 0 1
Circuit group unblocking acknowledgement 40 0 0 0 1 1 0 1 1
Charge information (national use) (Note) 0 0 1 1 0 0 0 1
Confusion 26 0 0 1 0 1 1 1 1
Connect 27 0 0 0 0 0 1 1 1
Continuity 28 0 0 0 0 0 1 0 1
Continuity check request 39 0 0 0 1 0 0 0 1
Facility 45 0 0 1 1 0 0 1 1
Facility accepted 42 0 0 1 0 0 0 0 0
 17 
Załącznik nr 2  Zalecenie Q.763
Table 4/Q.763
Reference
Message type Code
(Table)
Facility reject 29 0 0 1 0 0 0 0 1
Facility request 42 0 0 0 1 1 1 1 1
Forward transfer 37 0 0 0 0 1 0 0 0
Identification request 47 0 0 1 1 0 1 1 0
Identification response 48 0 0 1 1 0 1 1 1
Information (national use) 30 0 0 0 0 0 1 0 0
Information request (national use) 31 0 0 0 0 0 0 1 1
Initial address 32 0 0 0 0 0 0 0 1
Loop back acknowledgement (national use) 39 0 0 1 0 0 1 0 0
Loop prevention 50 0 1 0 0 0 0 0 0
Network resource management 46 0 0 1 1 0 0 1 0
Overload (national use) 39 0 0 1 1 0 0 0 0
Pass-along (national use) 43 0 0 1 0 1 0 0 0
Pre-release information 52 0 1 0 0 0 0 1 0
Release 33 0 0 0 0 1 1 0 0
Release complete 34 0 0 0 1 0 0 0 0
Reset circuit 39 0 0 0 1 0 0 1 0
Resume 38 0 0 0 0 1 1 1 0
Segmentation 49 0 0 1 1 1 0 0 0
Subsequent address 35 0 0 0 0 0 0 1 0
Subsequent Directory Number (national use) 53 0 1 0 0 0 0 1 1
Suspend 38 0 0 0 0 1 1 0 1
Unblocking 39 0 0 0 1 0 1 0 0
Unblocking acknowledgement 39 0 0 0 1 0 1 1 0
Unequipped CIC (national use) 39 0 0 1 0 1 1 1 0
User Part available 44 0 0 1 1 0 1 0 1
User Part test 44 0 0 1 1 0 1 0 0
User-to-user information 36 0 0 1 0 1 1 0 1
1.4 Formatting principles
Each message consists of a number of PARAMETERS listed and described in Clause 3. Each parameter has
a NAME which is coded as a single octet (see Table 5). The length of a parameter may be fixed or variable, and
a LENGTH INDICATOR of one octet for each parameter may be included as described below.
The detailed format is uniquely defined for each message type as described in Clause 4.
Between parameters there should be no unused (i.e. dummy) octets.
A general format diagram is shown in Figure 3.
1.5 Mandatory fixed part (Cześć obowiązkowych elementów stałej długości)
Those parameters that are mandatory and of fixed length for a particular message type will be contained in
the mandatory fixed part. The position, length and order of the parameters is uniquely defined by the message
type; thus, the names of the parameters and the length indicators are not included in the message.
1.6 Mandatory variable part (Cześć obowiązkowych elementów o zmiennej długości)
Mandatory parameters of variable length will be included in the mandatory variable part. Pointers are used
to indicate the beginning of each parameter. Each pointer is encoded as a single octet. The name of each
parameter and the order in which the pointers are sent is implicit in the message type. Parameter names are,
therefore, not included in the message. The details of how pointers are encoded is found in Subclause 2.3. The
number of parameters, and thus the number of pointers, is uniquely defined by the message type.
A pointer is also included to indicate the beginning of the optional part. If the message type indicates that no
optional part is allowed, then this pointer will not be present. If the message type indicates that an optional part is
possible (reflected by the presence of an "end of optional parameter" octet in Tables 21 through 50), but there is
no optional part included in this particular message, then a pointer field containing all zeros will be used. It is
recommended that all future message types with a mandatory variable part indicate that an optional part is
allowed.
All the pointers are sent consecutively at the beginning of the mandatory variable part. Each parameter
contains the parameter length indicator followed by the contents of the parameters. If there are no mandatory
variable parameters, but optional parameters are possible, the start of optional parameters pointer (coded all "0"s
if no optional parameter is present and coded "0000 0001" if any optional parameter is present) will be included.
 18 
Załącznik nr 2  Zalecenie Q.763
1.7 Optional part
The optional part consists of parameters that may or may not occur in any particular message type. Both
fixed length and variable length parameters may be included. Unless it is explicitly stated to the contrary within
this Recommendation, an optional parameter cannot occur multiple times within one message. Optional
parameters may be transmitted in any order. Each optional parameter will include the parameter name (one octet)
and the length indicator (one octet) followed by the parameter contents.
1.8 End of optional parameters octet
If optional parameters are present and after all optional parameters have been sent, an "end of optional
parameters" octet containing all zeros will be transmitted. If no optional parameter is present, an "end of optional
parameters" octet is not transmitted.
1.10 Coding of spare bits (Kodowanie niewykorzytywanych bitów)
Spare bits are coded 0 unless indicated otherwise.
1.11 National message types and parameters
If message type codes and parameter name codes are required for national uses not included in this
Recommendation, the codes chosen should be from the highest code downwards, that is, starting at code
1111_1111. Message type codes in the range 1111_1111 to 1110_0000 and parameter name codes in the range
1111_1111 to 1100_0001 are reserved exclusively for national use.
2 Parameter codes (Kody parametrów)
2.1 Message type codes
The encoding of the message type is shown in Table 4.
2.2 Coding of the length indicator
The length indicator field is binary coded to indicate the number of octets in the parameter content field. The
length indicated does not include the parameter name octet or the length indicator octet.
2.3 Coding of the pointers
The pointer value (in binary) gives the number of octets between the pointer itself (included) and the first
octet (not included) of the parameter associated with that pointer.
The pointer value all zeros is used to indicate that, in the case of optional parameters, no optional parameter
is present.
3 ISDN user part parameters1
3.1 Parameter names
The parameter name codes are given in Table 5 together with references to the subclauses in which they are
described.
Table 5/Q.763
Parameter name Reference Code
(subclause)
Access delivery information 3.2 0 0 1 0 1 1 1 0
Access transport 3.3 0 0 0 0 0 0 1 1
Application transport 3.82 0 1 1 1 1 0 0 0
Automatic congestion level 3.4 0 0 1 0 0 1 1 1
1
The clause numbering of the parameters in the previous version (1993) of this Recommendation is
retained; new parameters are added to the end of Clause 3.
 19 
Załącznik nr 2  Zalecenie Q.763
Table 5/Q.763
Parameter name Reference Code
(subclause)
Backward call indicators 3.5 0 0 0 1 0 0 0 1
Backward GVNS 3.62 0 1 0 0 1 1 0 1
Call diversion information 3.6 0 0 1 1 0 1 1 0
Call diversion treatment indicators 3.72 0 1 1 0 1 1 1 0
Call history information 3.7 0 0 1 0 1 1 0 1
Call offering treatment indicators 3.74 0 1 1 1 0 0 0 0
Call reference (national use) 3.8 0 0 0 0 0 0 0 1
Call transfer number 3.64 0 1 0 0 0 1 0 1
Call transfer reference 3.65 0 1 0 0 0 0 1 1
Called IN number 3.73 0 1 1 0 1 1 1 1
Called directory number (national use) 3.86 0 1 1 1 1 1 0 1
Called party number 3.9 0 0 0 0 0 1 0 0
Calling party number 3.10 0 0 0 0 1 0 1 0
Calling party's category 3.11 0 0 0 0 1 0 0 1
Cause indicators 3.12 0 0 0 1 0 0 1 0
CCNR possible indicator 3.83 0 1 1 1 1 0 1 0
CCSS 3.63 0 1 0 0 1 0 1 1
Charged party identification (national use) 3.75 0 1 1 1 0 0 0 1
Circuit assignment map 3.69 0 0 1 0 0 1 0 1
Circuit group supervision message type 3.13 0 0 0 1 0 1 0 1
Circuit state indicator (national use) 3.140 0 1 0 0 1 1 0
Closed user group interlock code 3.15 0 0 0 1 1 0 1 0
Collect call request 3.81 0 1 1 1 1 0 0 1
Conference treatment indicators 3.76 0 1 1 1 0 0 1 0
Connected number 3.160 0 1 0 0 0 0 1
Connection request 3.17 0 0 0 0 1 1 0 1
Continuity indicators 3.18 0 0 0 1 0 0 0 0
Correlation id 3.70 0 1 1 0 0 1 0 1
Display information 3.77 0 1 1 1 0 0 1 1
Echo control information 3.190 0 1 1 0 1 1 1
End of optional parameters 3.20 0 0 0 0 0 0 0 0
Event information 3.21 0 0 1 0 0 1 0 0
Facility indicator 3.22 0 0 0 1 1 0 0 0
Forward call indicators 3.23 0 0 0 0 0 1 1 1
Forward GVNS 3.66 0 1 0 0 1 1 0 0
Generic digits (national use) 3.24 1 1 0 0 0 0 0 1
Generic notification indicator 3.25 0 0 1 0 1 1 0 0
Generic number 3.26 1 1 0 0 0 0 0 0
Calling geodetic location 3.88 1 0 0 0 0 0 0 1
HTR information 3.89 1 0 0 0 0 0 1 0
Hop counter 3.80 0 0 1 1 1 1 0 1
Information indicators (national use) 3.28 0 0 0 0 1 1 1 1
Information request indicators (national use) 3.29 0 0 0 0 1 1 1 0
Location number 3.30 0 0 1 1 1 1 1 1
Loop prevention indicators 3.67 0 1 0 0 0 1 0 0
MCID request indicators 3.31 0 0 1 1 1 0 1 1
MCID response indicators 3.32 0 0 1 1 1 1 0 0
Message compatibility information 3.33 0 0 1 1 1 0 0 0
MLPP precedence 3.34 0 0 1 1 1 0 1 0
Nature of connection indicators 3.35 0 0 0 0 0 1 1 0
Network management controls 3.68 0 1 0 1 1 0 1 1
Network routeing number (national use) 3.90 1 0 0 0 0 1 0 0
Network specific facility (national use) 3.36 0 0 1 0 1 1 1 1
Number portability forward information (network option) 3.1011 0 0 0 1 1 0 1
Optional backward call indicators 3.37 0 0 1 0 1 0 0 1
Optional forward call indicators 3.38 0 0 0 0 1 0 0 0
Original called number 3.39 0 0 1 0 1 0 0 0
Original called IN number 3.87 0 1 1 1 1 1 1 1
Origination ISC point code 3.40 0 0 1 0 1 0 1 1
Parameter compatibility information 3.41 0 0 1 1 1 0 0 1
Pivot capability 3.84 0 1 1 1 1 0 1 1
Pivot counter 3.93 1 0 0 0 0 1 1 1
Pivot routeing backward information 3.95 1 0 0 0 1 0 0 1
Pivot routeing forward information 3.94 1 0 0 0 1 0 0 0
Pivot routeing indicators 3.85 0 1 1 1 1 1 0 0
Pivot status (national use) 3.92 1 0 0 0 0 1 1 0
 20 
Załącznik nr 2  Zalecenie Q.763
Table 5/Q.763
Parameter name Reference Code
(subclause)
Propagation delay counter 3.42 0 0 1 1 0 0 0 1
Query on release capability (network option) 3.911 0 0 0 0 1 0 1
Range and status 3.43 0 0 0 1 0 1 1 0
Redirect backward information (national use) 3.100 1 0 0 0 1 1 0 0
Redirect capability (national use) 3.96 0 1 0 0 1 1 1 0
Redirect counter (national use) 3.97 0 1 1 1 0 1 1 1
Redirect forward information (national use) 3.99 1 0 0 0 1 0 1 1
Redirect status (national use) 3.98 1 0 0 0 1 0 1 0
Redirecting number 3.44 0 0 0 0 1 0 1 1
Redirection information 3.45 0 0 0 1 0 0 1 1
Redirection number 3.46 0 0 0 0 1 1 0 0
Redirection number restriction 3.47 0 1 0 0 0 0 0 0
Remote operations (national use) 3.48 0 0 1 1 0 0 1 0
SCF id 3.71 0 1 1 0 0 1 1 0
Service activation 3.49 0 0 1 1 0 0 1 1
Signalling point code (national use) 3.50 0 0 0 1 1 1 1 0
Subsequent number 3.51 0 0 0 0 0 1 0 1
Suspend/Resume indicators 3.52 0 0 1 0 0 0 1 0
Transit network selection (national use) 3.53 0 0 1 0 0 0 1 1
Transmission medium requirement 3.54 0 0 0 0 0 0 1 0
Transmission medium requirement prime 3.55 0 0 1 1 1 1 1 0
Transmission medium used 3.56 0 0 1 1 0 1 0 1
UID action indicators 3.78 0 1 1 1 0 1 0 0
UID capability indicators 3.79 0 1 1 1 0 1 0 1
User service information 3.57 0 0 0 1 1 1 0 1
User service information prime 3.58 0 0 1 1 0 0 0 0
User teleservice information 3.59 0 0 1 1 0 1 0 0
User-to-user indicators 3.60 0 0 1 0 1 0 1 0
User-to-user information 3.61 0 0 1 0 0 0 0 0
3.3 Access transport
The format of the access transport parameter field is shown in Figure 5.
87654321
1
:
: Information element(s)
:
n
Figure 5/Q.763  Access transport parameter field
The information element is coded as described in 4.5/Q.931. Multiple Q.931 information elements can be
included within the access transport parameter. The information elements applicable to a particular usage of the
access transport parameter are dependent on, and will be determined by, the relevant procedures. The maximum
length of the access transport parameter should only be limited by the message length as the content of the ATP
will probably evolve in the future.
3.5 Backward call indicators
The format of the backward call indicators parameter field is shown in Figure 7.
87654321
1 HG F EDCBA
2 P O N M L K J I
Figure 7/Q.763  Backward call indicators parameter field
The following codes are used in the backward call indicators parameter field:
bits : Charge indicator (Note 1)
BA
0 0 no indication
 21 
Załącznik nr 2  Zalecenie Q.763
0 1 no charge
1 0 charge
1 1 spare
NOTE 1  The interpretation of these bits depends only on the charging exchange.
bits : Called party's status indicator
DC
0 0 no indication
0 1 subscriber free
1 0 connect when free (national use)
1 1 spare
bits : Called party's category indicator
FE
0 0 no indication
0 1 ordinary subscriber
1 0 payphone
1 1 spare
bits : End-to-end method indicator (Note 2)
HG
0 0 no end-to-end method available (only link-by-link method available)
0 1 pass-along method available (national use)
1 0 SCCP method available
1 0 pass-along and SCCP methods available (national use)
bit I: Interworking indicator (Note 2)
0 no interworking encountered (Signalling System No. 7 all the way)
1 interworking encountered
bit J: End-to-end information indicator (national use) (Note 2)
0 no end-to-end information available
1 end-to-end information available
bit K: ISDN user part indicator (Note 2)
0 ISDN user part not used all the way
1 ISDN user part used all the way
bit L: Holding indicator (national use)
0 holding not requested
1 holding requested
bit M: ISDN access indicator
0 terminating access non-ISDN
1 terminating access ISDN
bit N: Echo control device indicator
0 incoming echo control device not included
1 incoming echo control device included
bits : SCCP method indicator (Note 2)
PO
0 0 no indication
0 1 connectionless method available (national use)
1 0 connection oriented method available
1 1 connectionless and connection oriented methods available (national use)
NOTE 2  Bits G-K and O-P constitute the protocol control indicator.
3.6 Call diversion information
The format of the call diversion information parameter field is shown in Figure 8.
 22 
Załącznik nr 2  Zalecenie Q.763
87654321
HGF EDCBA
Figure 8/Q.763  Call diversion information parameter field
The following codes are used in the call diversion information parameter field.
a) Notification subscription options
bits CBA:
0 0 0 Unknown
0 0 1 presentation not allowed
0 1 0 presentation allowed with redirection number
0 1 1 presentation allowed without redirection number
b) Redirecting reason
bits
GFED:
0 0 0 0 Unknown
0 0 0 1 User busy
0 0 1 0 no reply
0 0 1 1 unconditional
0 1 0 deflection during alerting
0
0 1 0 deflection immediate response
1
0 1 1 mobile subscriber not reachable
0
bit H: spare
3.8 Call reference (national use)
The format of the call reference parameter is shown in Figure 9.
87654321
1
2 Call identity
3
4 Signalling lsb
5 spare msb point code
Figure 9/Q.763  Call reference parameter field
The following codes are used in the subfields of the call reference parameter field:
a) Call identity
A code expressing in pure binary representation the identification number allocated to the call.
b) Signalling point code
The code of the signalling point in which the call identity is relevant.
3.9 Called party number (Numer abonenta wywoływanego)
The format of the called party number parameter field is shown in Figure 10.
87654321
1 O/E Nature of address indicator
2 INN Numbering plan indicator spare
3 2nd address signal 1st address signal
:
:
m Filler (if necessary) nth address signal
Figure 10/Q.763  Called party number parameter field
 23 
Załącznik nr 2  Zalecenie Q.763
The following codes are used in the subfields of the called party number parameter field:
a) Odd/even indicator (O/E)
0 even number of address signals
1 odd number of address signals
b) Nature of address indicator
0 0 0 0 0 0 0 spare
0 0 0 0 0 0 1 subscriber number (national use)
0 0 0 0 0 1 0 unknown (national use)
0 0 0 0 0 1 1 national (significant) number
0 0 0 0 1 0 0 international number
0 0 0 0 1 0 1 network-specific number (national use)
0 0 0 0 1 1 0 network routeing number in national (significant) number format (national use)
0 0 0 0 1 1 1 network routeing number in network-specific number format (national use)
0 0 0 1 0 0 0 network routeing number concatenated with Called Directory Number (national use)
c) Internal Network Number indicator (INN)
0 routeing to internal network number allowed
1 routeing to internal network number not allowed
d) Numbering plan indicator
0 0 0 spare
0 0 1 ISDN (Telephony) numbering plan (Recommendation E.164)
0 1 0spare
0 1 1 Data numbering plan (Recommendation X.121) (national use)
1 0 0 Telex numbering plan (Recommendation F.69) (national use)
1 0 1 reserved for national use
1 1 0 reserved for national use
1 1 1 spare
e) Address signal
0 0 0 0 digit 0
0 0 0 1 digit 1
0 0 1 0 digit 2
0 0 1 1 digit 3
0 1 0 0 digit 4
0 1 0 1 digit 5
0 1 1 0 digit 6
0 1 1 1 digit 7
1 0 0 0 digit 8
1 0 0 1 digit 9
1 0 1 0spare
1 0 1 1 code 11
1 1 0 0 code 12
1 1 0 1 spare
1 1 1 0spare
1 1 1 1 ST
The most significant address signal is sent first. Subsequent address signals are sent in successive 4-bit
fields.
f) Filler
In case of an odd number of address signals, the filler code 0000 is inserted after the last address
signal.
3.10 Calling party number (Numer abonenta wywołującego)
The format of the calling party number parameter field is shown in Figure 11.
 24 
Załącznik nr 2  Zalecenie Q.763
87654321
1 O/E Nature of address indicator
2 NI Numbering plan indicator Address presentation Screening indicator
restricted indicator
3 2nd address signal 1st address signal
:
:
m Filler (if necessary) nth address signal
Figure 11/Q.763  Calling party number parameter field
The following codes are used in the calling party number parameter field.
a) Odd/even indicator (O/E): as Subclause 3.9 a)
b) Nature of address indicator
0 0 0 0 0 0 0 spare
0 0 0 0 0 0 1 subscriber number (national use)
0 0 0 0 0 1 0 unknown (national use)
0 0 0 0 0 1 1 national (significant) number (national use)
0 0 0 0 1 0 0 international number
c) Number Incomplete indicator (NI)
0 complete
1 incomplete
d) Numbering plan indicator: as Subclause 3.9 d)
e) Address presentation restricted indicator
0 0 presentation allowed
0 1 presentation restricted
1 0 address not available (Note) (national use)
1 1 reserved for restriction by the network
NOTE  If the parameter is included and the address presentation restricted indicator indicates address not
available, octets 3 to n are omitted, the subfields in items a), b), c) and d) are coded with 0's, and the subfield f) is
coded with 11.
f) Screening indicator
0 0 reserved (Note)
0 1 user provided, verified and passed
1 0 reserved (Note)
1 1 network provided
NOTE  Code 00 and 10 are reserved for "user provided, not verified" and "user provided, verified and
failed" respectively. Codes 00 and 10 are for national use.
g) Address signal
0 0 0 0 digit 0
0 0 0 1 digit 1
0 0 1 0 digit 2
0 0 1 1 digit 3
0 1 0 0 digit 4
0 1 0 1 digit 5
0 1 1 0 digit 6
0 1 1 1 digit 7
1 0 0 0 digit 8
1 0 0 1 digit 9
1 0 1 0spare
1 0 1 1 code 11
1 1 0 0 code 12
 25 
Załącznik nr 2  Zalecenie Q.763
3.11 Calling party's category
The format of the calling party's category parameter field is shown in Figure 12.
87654321
Calling party's category
Figure 12/Q.763  Calling party's category parameter field
The following codes are used in the calling party's category parameter field.
calling party's category unknown at this time (national use)
0 0 0 0 0 0 0
0
0 0 0 0 0 0 0
operator, language French
1
0 0 0 0 0 0 1
operator, language English
0
0 0 0 0 0 0 1
operator, language German
1
0 0 0 0 0 1 0
operator, language Russian
0
0 0 0 0 0 1 0
operator, language Spanish
1
0 0 0 0 1 0 0
reserved (see Recommendation Q.104) (Note) (national use)
1
0 0 0 0 1 0 1
ordinary calling subscriber
0
0 0 0 0 1 0 1
calling subscriber with priority
1
0 0 0 0 1 1 0
data call (voice band data)
0
0 0 0 0 1 1 0
test call
1
0 0 0 0 1 1 1
spare
0
0 0 0 0 1 1 1
payphone
1
3.12 Cause indicators
The format of the cause indicators parameter field is shown in Figure 13.
87654321
1 ext. Coding standard spare Location
2 ext. Cause value
3
: Diagnostic(s) (if any)
:
3n
NOTE - Octets 3 to 3n may be omitted or repeated, e.g. 3 to 3n .
Figure 13/Q.763  Cause indicators parameter field
The codes to be used in the subfields of the cause indicators parameter fields are defined in Recommendation
Q.850.
3.13 Circuit group supervision message type
The format of the circuit group supervision message type parameter field is shown in Figure 14.
87654321
HGF EDCBA
Figure 14/Q.763  Circuit group supervision message type parameter field
 26 
Załącznik nr 2  Zalecenie Q.763
The following codes are used in the circuit group supervision message type parameter field:
bits BA: Circuit group supervision message type indicator
0 0 maintenance oriented
0 1 hardware failure oriented
1 0 reserved for national use (used in 1984 version)
1 1 spare
3.14 Circuit state indicator (national use)
The format of the circuit state indicator parameter field is shown in Figure 15.
87654321
1 HGF EDCBA
:
:
:
n H G F E D C B A
Figure 15/Q.763  Circuit state indicator parameter field
The number of octets in the circuit state indicator parameter field is equal to the specified range + 1. Each
circuit state indicator octet is associated with a circuit identification code such that octet n is associated with
circuit identification code m + n - 1, where m is the circuit identification code contained in the message.
The following codes are used in each circuit state indicator octet:
a) for bits D C = 00
bits BA: Maintenance blocking state
0 0 transient
0 1 spare
1 0spare
1 1 unequipped
bits H-E: spare
b) for bits D C not equal to 00
bits BA: Maintenance blocking state
0 0 no blocking (active)
0 1 locally blocked
1 0 remotely blocked
1 1 locally and remotely blocked
bits DC: Call processing state
0 1 circuit incoming busy
1 0 circuit outgoing busy
1 1 idle
bits F E: Hardware blocking state (Note)
0 0 no blocking (active)
0 1 locally blocked
1 0 remotely blocked
1 1 locally and remotely blocked
bits H-G: spare
NOTE  If bits F E are not coded 0 0, bits D C must be coded 1 1.
3.15 Closed user group interlock code
The format of the closed user group interlock code parameter field is shown in Figure 16.
 27 
Załącznik nr 2  Zalecenie Q.763
87654321
11st NI digit 2nd NI digit
2 3rd NI digit 4th NI digit
3 msb
4 Binary code lsb
Figure 16/Q.763  Closed user group interlock code parameter field
The following codes are used in the subfields of the closed user group interlock code parameter field:
a) Network Identity (NI) (octets 1 and 2)
Each digit is coded in the binary coded decimal representation from 0 to 9. If the first digit of this field
is coded 0 or 9, the TCC (Telephony Country Code) follows in the second to fourth NI digits (the most
significant TCC digit is in the 2nd NI digit). If the TCC is one or two digits long, the excess digit(s) is
inserted with the code for RPOA or network identification, if necessary. If octet 2 is not required, it is
coded all zeros.
Coding of the first digit as 1 or 8 is excluded.
If the first digit is not 0, 9, 1 or 8, this field contains a DNIC (Data Network Identification Code) as
defined in Recommendation X.121.
b) Binary code (octets 3 and 4)
A code allocated to a closed user group administered by a particular ISDN or data network. Bit 8 of
octet 3 is the most significant and bit 1 of octet 4 is the least significant.
3.16 Connected number
The format of the connected number parameter field is shown in Figure 17.
87654321
1 O/E Nature of address indicator
2 spare Numbering plan indicator Address presentation Screening indicator
restricted indicator
3 2nd address signal 1st address signal
:
:
m Filler (if necessary) nth address signal
Figure 17/Q.763  Connected number parameter field
The following codes are used in the subfields of the connected number parameter field:
a) Odd/even indicator (O/E): as Subclause 3.9 a).
b) Nature of address indicator: as Subclause 3.10 b).
c) Numbering plan indicator: as Subclause 3.9 d).
d) Address presentation restricted indicator:
0 0 presentation allowed
0 1 presentation restricted
1 0 address not available
1 1 spare
NOTE  If the parameter is included and the address presentation restricted indicator indicates address not
available, octets 3 to n are omitted, the subfields in items a), b), and c) are coded with 0's, and the screening
indicator is set to 11 network provided.
e) Screening indicator: as Subclause 3.10 f).
f) Address signal: as Subclause 3.10 g).
g) Filler: as Subclause 3.9 f).
3.17 Connection request
The format of the connection request parameter field is shown in Figure 18.
 28 
Załącznik nr 2  Zalecenie Q.763
87654321
1
2 Local reference
3
4 Signalling point lsb
5 spare msb code
6 Protocol class
7Credit
NOTE - Octets 6 and 7 may be omitted if protocol class requested is 2.
Figure 18/Q.763  Connection request parameter field
The following codes are used in the subfields of the connection request parameter field:
a) Local reference
A code indicating the local reference allocated by the signalling connection control part to the end-to-
end connection.
b) Signalling point code
A code identifying the signalling point at which the connection request originated.
c) Protocol class
A code identifying in pure binary representation, the protocol class requested for the end-to-end
connection.
d) Credit
A code identifying in pure binary representation the window size requested for the end-to-end
connection.
3.18 Continuity indicators
The format of the continuity indicators parameter field is shown in Figure 19.
87654321
HGFEDCBA
Figure 19/Q.763  Continuity indicators parameter field
The following codes are used in the continuity indicators parameter field:
bit A: Continuity indicator
0 continuity check failed
1 continuity check successful
bits H-B spare
3.19 Echo control information (tłumiki echa)
The format of the echo control information parameter field is shown in Figure 20.
87654321
HGF EDCBA
Figure 20/Q.763  Echo control information parameter field
a) bits BA: Outgoing echo control device information indicator
0 0no information
0 1outgoing echo control device not included and not available
1 0outgoing echo control device included
1 1outgoing echo control device not included but available
b) bits DC: Incoming echo control device information indicator
0 0 no information
0 1 incoming echo control device not included and not available
 29 
Załącznik nr 2  Zalecenie Q.763
1 0 incoming echo control device included
1 1 incoming echo control device not included but available
c) bits :Outgoing echo control device request indicator
FE
0 0 no information
0 1 outgoing echo control device activation request
1 0 outgoing echo control device deactivation request (Note)
1 1 spare
NOTE  This value will not be generated by the Echo Control Logic defined in Recommendation Q.115.
d) bits HG: Incoming echo control device request indicator
0 0 no information
0 1 incoming echo control device activation request
1 0 incoming echo control device deactivation request (Note)
1 1 spare
NOTE  This value will not be generated by the Echo Control Logic defined in Recommendation Q.115.
3.20 End of optional parameters
The last optional parameter field of a message is followed by the end of optional parameters octet (see
Subclause 1.8).
3.21 Event information
The format of the event information parameter field is shown in Figure 21.
87654321
HGF EDCBA
Figure 21/Q.763  Event information parameter field
The following codes are used in the event indicator parameter field:
bits GFEDCBA : Event indicator
0 0 0 0 0 0 0 spare
0 0 0 0 0 0 1 ALERTING
0 0 0 0 0 1 0 PROGRESS
0 0 0 0 0 1 1 in-band information or an appropriate pattern is now available
0 0 0 0 1 0 0 call forwarded on busy (national use)
0 0 0 0 1 0 1 call forwarded on no reply (national use)
0 0 0 0 1 1 0 call forwarded unconditional (national use)
bit H: Event presentation restricted indicator (national use)
0 no indication
1 presentation restricted
3.22 Facility indicator
The following codes are used in the facility indicator parameter field:
0 0 0 0 0 0 0 0
spare
0 0 0 0 0 0 0 1 spare
0 0 0 0 0 0 1 0 user-to-user service
3.23 Forward call indicators
The format of the forward call indicators parameter field is shown in Figure 23.
 30 
Załącznik nr 2  Zalecenie Q.763
87654321
1 HGF EDCBA
2 P O N M L K J I
Figure 23/Q.763  Forward call indicators parameter field
The following codes are used in the forward call indicators parameter field:
bit A: National/international call indicator (Note 1)
0 call to be treated as a national call
1 call to be treated as an international call
bits CB: End-to-end method indicator (Note 2)
0 0 no end-to-end method available (only link-by-link method available)
0 1 pass-along method available (national use)
1 0 SCCP method available
1 1 pass-along and SCCP methods available (national use)
bit D: Interworking indicator (Note 2)
0 no interworking encountered (No. 7 signalling all the way)
1 interworking encountered
bit E: End-to-end information indicator (national use) (Note 2)
0 no end-to-end information available
1 end-to-end information available
bit F: ISDN user part indicator (Note 2)
0 ISDN user part not used all the way
1 ISDN user part used all the way
bits HG: ISDN user part preference indicator
0 0 ISDN user part preferred all the way
0 1 ISDN user part not required all the way
1 0 ISDN user part required all the way
1 1 spare
bit I: ISDN access indicator
0 originating access non-ISDN
1 originating access ISDN
bits KJ: SCCP method indicator (Note 2)
0 0 no indication
0 1 connectionless method available (national use)
1 0 connection oriented method available
1 1 connectionless and connection oriented methods available (national use)
bit L: spare
bits P-M: reserved for national use
NOTE 1  Bit A can be set to any value in the country of origin. In the international network this bit is not checked. In the
destination country, calls from the international network will have this bit set to 1.
NOTE 2  Bits B-F and J-K constitute the protocol control indicator.
3.24 Generic digits (national use)
The format of the generic digits parameter field is shown in Figure 24.
 31 
Załącznik nr 2  Zalecenie Q.763
87654321
1 Encoding scheme Type of digits
2 digits
:
:
:
n digits
Figure 24/Q.763  Generic digits parameter
The following codes are used in the subfields of the generic digits parameter:
a) Encoding scheme
0 0 0 BCD even: (even number of digits)
0 0 1 BCD odd: (odd number of digits)
0 1 0 IA5 character
0 1 1 binary coded
b) Type of digits
0 0 0 0 0 reserved for account code
0 0 0 0 1 reserved for authorisation code
0 0 0 1 0 reserved for private networking travelling class mark
0 0 0 1 1 reserved for business communication group identity
c) Digit
Coding in accordance to the coding scheme and type of digits.
3.25 Generic notification indicator
The format of the generic notification indicator parameter field is shown in Figure 25.
87654321
ext. Notification indicator
Figure 25/Q.763  Generic notification indicator parameter field
The following codes are used in the generic notification indicator parameter field:
a) Extension indicator (ext.)
0 information continues in the next octet
1 last octet
b) Notification indicator
0 0 0 0 0 0 0 user suspended
0 0 0 0 0 0 1 user resumed
0 0 0 0 0 1 0 bearer service change
üÅ‚
ôÅ‚
0 0 0 0 0 1 1 discriminator for extension to ASN.1
(used in DSS 1)
żł
encoded component
ôÅ‚
þÅ‚
0 0 0 0 1 0 0 call completion delay
1 0 0 0 0 1 0 conference established
1 0 0 0 0 1 1 conference disconnected
1 0 0 0 1 0 0 other party added
1 0 0 0 1 0 1 isolated
1 0 0 0 1 1 0 reattached
1 0 0 0 1 1 1 other party isolated
1 0 0 1 0 0 0 other party reattached
1 0 0 1 0 0 1 other party split
1 0 0 1 0 1 0 other party disconnected
1 0 0 1 0 1 1 conference floating
 32 
Załącznik nr 2  Zalecenie Q.763
1 1 0 0 0 0 0 call is a waiting call
1 1 0 1 0 0 0 diversion activated (used in DSS 1)
1 1 0 1 0 0 1 call transfer, alerting
1 1 0 1 0 1 0 call transfer, active
1 1 1 1 0 0 1 remote hold
1 1 1 1 0 1 0 remote retrieval
1 1 1 1 0 1 1 call is diverting
3.26 Generic number
The format of the generic number parameter field is shown in Figure 26.
87654321
1 Number qualifier indicator
2 O/E Nature of address indicator
3 NI Numbering plan indicator Address presentation Screening
restricted indicator
indicator
4 2nd address signal 1st address signal
:
:
m Filler (if necessary) nth address signal
Figure 26/Q.763  Generic number parameter field
The following codes are used in the generic number parameter field:
a) Number qualifier indicator
0 0 0 0 0 0 0 0 reserved (dialled digits) (national use)
0 0 0 0 0 0 0 1 additional called number (national use)
0 0 0 0 0 0 1 0 reserved (supplemental user provided calling number  failed network
screening) (national use)
0 0 0 0 0 0 1 1 reserved (supplemental user provided calling number  not screened)
(national use)
0 0 0 0 0 1 0 0 reserved (redirecting terminating number) (national use)
0 0 0 0 0 1 0 1 additional connected number
0 0 0 0 0 1 1 0 additional calling party number
0 0 0 0 0 1 1 1 reserved for additional original called number
0 0 0 0 1 0 0 0 reserved for additional redirecting number
0 0 0 0 1 0 0 1 reserved for additional redirection number
0 0 0 0 1 0 1 0 reserved (used in 1992 version)
b) Odd/even indicator (O/E): as Subclause 3.9 a)
c) Nature of address indicator
0 0 0 0 0 0 0 spare
0 0 0 0 0 0 1 subscriber number (national use)
0 0 0 0 0 1 0 unknown (national use)
0 0 0 0 0 1 1 national (significant) number
0 0 0 0 1 0 0 international number
d) Number incomplete indicator (NI)
0 number complete
1 number incomplete
e) Numbering plan indicator
0 0 0 spare
0 0 1 ISDN (telephony) numbering plan (Recommendation E.164)
0 1 0spare
0 1 1 data numbering plan (Recommendation X.121) (national use)
1 0 0 telex numbering plan (Recommendation F.69) (national use)
 33 
Załącznik nr 2  Zalecenie Q.763
1 0 1 private numbering plan (national use)
1 1 0 reserved for national use
1 1 1 spare
NOTE  For each supplementary service the relevant codes and possible default settings are described in the
supplementary service Recommendations (Recommendation Q.73x).
f) Address presentation restricted indicator
0 0 presentation allowed
0 1 presentation restricted
1 0 address not available
1 1 spare
NOTE  For each supplementary service the relevant codes and possible default settings are described in the
supplementary service Recommendations (Recommendation Q.73x). When the address presentation restricted
indicator indicates address not available, the subfields in items b), c), d), and e) are coded with 0's, and the
screening indicator is set to 11 (network provided).
g) Screening indicator
Only used if the number qualifier indicator is coded 0000 0101 (additional connected number) or 0000
0110 (additional calling party number). This indicator is coded as follows:
0 0 user provided, not verified
0 1 user provided, verified and passed
1 0 user provided, verified and failed
1 1 network provided
NOTE  For each supplementary service the relevant codes and possible default settings are described in the
supplementary service Recommendations (Recommendation Q.73x).
h) Address signal:
0 0 0 0 digit 0
0 0 0 1 digit 1
0 0 1 0 digit 2
0 0 1 1 digit 3
0 1 0 0 digit 4
0 1 0 1 digit 5
0 1 1 0 digit 6
0 1 1 1 digit 7
1 0 0 0 digit 8
1 0 0 1 digit 9
3.28 Information indicators (national use)
The format of the information indicators parameter field is shown in Figure 28.
87654321
1 HGF EDCBA
2 P O N M L K J I
Figure 28/Q.763  Information indicators parameter field
The following codes are used in the information indicators parameter field:
bits BA: Calling party address response indicator
0 0 calling party address not included
0 1 calling party address not available
1 0spare
1 1 calling party address included
bit C: Hold provided indicator
0 hold not provided
1 hold provided
bits ED: spare
 34 
Załącznik nr 2  Zalecenie Q.763
bit F: Calling party's category response indicator
0 calling party's category not included
1 calling party's category included
bit G: Charge information response indicator
0 charge information not included
1 charge information included
bit H: Solicited information indicator
0 solicited
1 unsolicited
3.29 Information request indicators (national use)
The format of the information request indicators parameter field is shown in Figure 29.
87654321
1 HGF EDCBA
2 P O N M L K J I
Figure 29/Q.763  Information request indicators parameter field
The following codes are used in the information request indicators parameter field:
bit A: Calling party address request indicator
0 calling party address not requested
1 calling party address requested
bit B: Holding indicator
0 holding not requested
1 holding requested
bit C: spare
bit D: Calling party's category request indicator
0 calling party's category not requested
1 calling party's category requested
bit E: Charge information request indicator
0 charge information not requested
1 charge information requested
bits GF: spare
bit H: Malicious call identification request indicator (reserved, used in ISUP'88 Blue Book)
0 malicious call identification not requested
1 malicious call identification requested
3.30 Location number
The format of the location number field is shown in Figure 30.
87654321
1 O/E Nature of address indicator
2 INN Numbering plan indicator Address presentation Screening indicator
restricted indicator
3 2nd address signal 1st address signal
:
:
m Filler (if necessary) nth address signal
Figure 30/Q.763  Location number parameter field
 35 
Załącznik nr 2  Zalecenie Q.763
The following codes are used in the subfields of the location number parameter field:
a) Odd/even indicator (O/E): as Subclause 3.9 a).
b) Nature of address indicator
0 0 0 0 0 0 0 spare
0 0 0 0 0 0 1 reserved for subscriber number (national use)
0 0 0 0 0 1 0 reserved for unknown (national use)
0 0 0 0 0 1 1 national (significant) number (national use)
0 0 0 0 1 0 0 international number
c) Internal Network Number indicator (INN)
0 routeing to internal number allowed
1 routeing to internal number not allowed
d) Numbering plan indicator
0 0 0 spare
0 0 1 ISDN (telephony) numbering plan (Recommendation E.164)
0 1 0spare
0 1 1 Data numbering plan (Recommendation X.121) (national use)
1 0 0 Telex numbering plan (Recommendation F.69) (national use)
1 0 1 private numbering plan
1 1 0 reserved for national use
1 1 1 spare
e) Address presentation restricted indicator
0 0 presentation allowed
0 1 presentation restricted
1 0 address not available (national use)
1 1 spare
NOTE  When the address presentation restricted indicator indicates address not available, the subfields in
items a), b), c) and d) are coded with 0's, and the screening indicator is set to 11 (network provided).
f) Screening indicator
0 0 reserved
0 1 user provided, verified and passed
1 0 reserved
1 1 network provided
g) Address signals: as Subclause 3.26 h).
3.31 MCID request indicators
The format of the MCID request indicators parameter field is shown in Figure 31.
87654321
HGFEDCBA
Figure 31/Q.763  MCID request indicators parameter field
The following codes are used in the MCID request indicators parameter field:
bit A: MCID request indicator
0 MCID not requested
1 MCID requested
bit B: Holding indicator (national use)
0 holding not requested
1 holding requested
3.32 MCID response indicators
The format of the MCID response indicators parameter field is shown in Figure 32.
 36 
Załącznik nr 2  Zalecenie Q.763
87654321
HGFEDCBA
Figure 32/Q.763  MCID response indicators parameter field
The following codes are used in the MCID response indicators parameter field:
bit A: MCID response indicator
0 MCID not included
1 MCID included
bit B: Hold provided indicator (national use)
0 holding not provided
1 holding provided
3.33 Message compatibility information
The format of the message compatibility information parameter field is shown in Figure 33.
87654321
Instruction indicator
Figure 33/Q.763  Message compatibility information parameter field
The following codes are used in the subfields of the message compatibility information parameter field:
a) Instruction indicators
The format of the instruction indicators subfield is shown Figure 34.
87654321
1 ext. GFEDCBA
1a ext. More instruction indicators if required
: :
: :
1n 1 More instruction indicators if required
Figure 34/Q.763  Instruction indicators subfield
The following codes are used in the instructions indicators subfield:
bit A: Transit at intermediate exchange indicator
0 transit interpretation
1 end node interpretation
bit B: Release call indicator
0 do not release call
1 release call
bit C: Send notification indicator
0 do not send notification
1 send notification
bit D: Discard message indicator
0 do not discard message (pass on)
1 discard message
bit E: Pass on not possible indicator
0 release call
1 discard information
 37 
Załącznik nr 2  Zalecenie Q.763
bits G F: Broadband/narrowband interworking indicator
0 0 pass on
0 1 discard message
1 0 release call
1 1 reserved, assume 00
b) Extension indicator (ext.): as Subclause 3.25 a).
c) More instruction indicators
The bits will be defined when required.
3.35 Nature of connection indicators
The format of the nature of connection indicators parameter field is shown in Figure 36.
87654321
HGF EDCBA
Figure 36/Q.763  Nature of connection indicators parameter field
The following codes are used in the nature of connection indicators parameter field:
bits BA: Satellite indicator
0 0 no satellite circuit in the connection
0 1 one satellite circuit in the connection
1 0 two satellite circuits in the connection
1 1 spare
bits DC: Continuity check indicator
0 0 continuity check not required
0 1 continuity check required on this circuit
1 0 continuity check performed on a previous circuit
1 1 spare
bit E: Echo control device indicator
0 outgoing echo control device not included
1 outgoing echo control device included
3.39 Original called number
The format of the original called number parameter field is shown in Figure 40.
87654321
1 O/E Nature of address indicator
2 spare Numbering plan indicator Address presentation spare
restricted indicator
3 2nd address signal 1st address signal
:
:
m Filler (if necessary) nth address signal
Figure 40/Q.763  Original called number parameter field
The following codes are used in the subfields of the original called number parameter field:
a) Odd/even indicator (O/E): as Subclause 3.9 a).
b) Nature of address indicator:
0 0 0 0 0 0 0 spare
0 0 0 0 0 0 1 subscriber number (national use)
0 0 0 0 0 1 0 unknown (national use)
0 0 0 0 0 1 1 national (significant) number (national use)
 38 
Załącznik nr 2  Zalecenie Q.763
0 0 0 0 1 0 0 international number
c) Numbering plan indicator: as Subclause 3.9 d).
d) Address presentation restricted indicator: as Subclause 3.10 e).
e) Address signal: as Subclause 3.10 g).
3.41 Parameter compatibility information
The format of the parameter compatibility information parameter field is shown in Figure 41.
87654321
11st upgraded parameter
2 Instruction indicators
:
:
2n-1 nth upgraded parameter
2n Instruction indicators
Figure 41/Q.763  Parameter compatibility information parameter field
The following codes are used in the subfields of the parameter compatibility information parameter field:
a) Nth upgraded parameter name
This field contains the parameter name of the nth upgraded parameter in accordance with Table 5.
b) Instruction indicators
The format of the instruction indicators subfield is shown in Figure 41.1.
87654321
1 ext. G F E D C B A
1a ext. O N M L K J I
: :
: :
1n More instruction indicators if required
Figure 41.1/Q.763  Instruction indicators subfield
The following codes are used in the instructions indicators subfield:
bit A: Transit at intermediate exchange indicator
0 transit interpretation
1 end node interpretation
bit B: Release call indicator
0 do not release call
1 release call
bit C: Send notification indicator
0 do not send notification
1 send notification
bit D: Discard message indicator
0 do not discard message (pass on)
1 discard message
bit E: Discard parameter indicator
0 do not discard parameter (pass on)
1 discard parameter
bits G F: Pass on not possible indicator
0 0 release call
0 1 discard message
1 0 discard parameter
1 1 reserved (interpreted as 00)
c) Extension indicator (ext.): as Subclause 3.25 a).
 39 
Załącznik nr 2  Zalecenie Q.763
d) bits J I: Broadband/narrowband interworking indicator
0 0 pass on
0 1 discard message
1 0 release call
1 1 discard parameter
e) bits O-K: spare
3.47 Redirection number restriction
The format of the redirection number presentation parameter field is shown in Figure 45.
87654321
HGFEDCBA
Figure 45/Q.763  Redirection number restriction parameter field
The following codes are used in the redirection number restriction parameter field:
bits BA: Presentation restricted indicator
0 0 presentation allowed
0 1 presentation restricted
1 0 spare
1 1 spare
bits H-C: spare
3.49 Service activation
The format of the service activation parameter field is shown in Figure 49.
87654321
1 Feature code 1
2 Feature code 2
3 Feature code 3
::
n Feature code n
Figure 49/Q.763  Service activation parameter field
The following feature codes are used in the service activation parameter field:
0 0 0 0 0 0 0 0 spare
0 0 0 0 0 0 0 1 call transfer
3.51 Subsequent number
The format of the subsequent number parameter field is shown in Figure 51.
87654321
1 O/E spare
2 2nd address signal 1st address signal
:
:
m Filler (if necessary) nth address signal
Figure 51/Q.763  Subsequent number parameter field
The following codes are used in the subfields of the subsequent number parameter field:
a) Odd/even indicator (O/E): as Subclause 3.9 a).
b) Address signal: as Subclause 3.9 e).
3.52 Suspend/resume indicators
The format of the suspend/resume indicators parameter field is shown in Figure 52.
 40 
Załącznik nr 2  Zalecenie Q.763
87654321
HGF EDCBA
Figure 52/Q.763  Suspend/resume indicators parameter field
The following codes are used in the suspend/resume indicators parameter field:
bit A: Suspend/resume indicator
0 ISDN subscriber initiated
1 network initiated
3.53 Transit network selection (national use)
The format of the transit network selection parameter field is shown in Figure 53.
87654321
1 O/E Type of network identification Network identification plan
2
: Network identification
n
Figure 53/Q.763  Transit network selection parameter field
The following codes are used in the subfields of the transit network selection parameter field:
a) Odd/even indicator(O/E): as Subclause 3.9 a).
b) Type of network identification
0 0 0 CCITT/ITU-T-standardized identification
0 0 1 spare
0 1 0 national network identification
c) Network identification plan
i) For CCITT/ITU-T-standardized identification
0 0 0 0 unknown
0 0 0 1 spare
0 0 1 0 spare
0 0 1 1 public data network identification code (DNIC), Recommendation X.121
0 1 0 0 spare
0 1 0 1 spare
0 1 1 0 public land Mobile Network Identification Code (MNIC), Recommendation E.212
ii) For national network identification
This information is coded according to national specifications.
d) Network identification
This information is organized according to the network identification plan and the coding principle
given in Subclause 3.9 e) and, if applicable, in Subclause 3.9 f).
3.54 Transmission medium requirement
The format of the transmission medium requirement parameter field is shown in Figure 54.
87654321
Transmission medium requirement (TMR)
Figure 54/Q.763  Transmission medium requirement parameter field
 41 
Załącznik nr 2  Zalecenie Q.763
The following codes are used in the transmission medium requirement parameter field:
0 0 0 0 0 0 0 0
speech
0 0 0 0 0 0 0 1
spare
0 0 0 0 0 0 1 0
64 kbit/s unrestricted
0 0 0 0 0 0 1 1
3.1 kHz audio
0 0 0 0 0 1 0 0
reserved for alternate speech (service 2)/64 kbit/s unrestricted (service 1)
0 0 0 0 0 1 0 1
reserved for alternate 64 kbit/s unrestricted (service 1)/speech (service 2)
0 0 0 0 0 1 1 0
64 kbit/s preferred
0 0 0 0 0 1 1 1
2 × 64 kbit/s unrestricted
0 0 0 0 1 0 0 0
384 kbit/s unrestricted
0 0 0 0 1 0 0 1
1536 kbit/s unrestricted
0 0 0 0 1 0 1 0
1920 kbit/s unrestricted
0 0 0 1 0 0 0 0
3 × 64 kbit/s unrestricted
0 0 0 1 0 0 0 1
4 × 64 kbit/s unrestricted
0 0 0 1 0 0 1 0
5 × 64 kbit/s unrestricted
0 0 0 1 0 0 1 1
spare
0 0 0 1 0 1 0 0
7 × 64 kbit/s unrestricted
0 0 0 1 0 1 0 1
8 × 64 kbit/s unrestricted
0 0 0 1 0 1 1 0
9 × 64 kbit/s unrestricted
0 0 0 1 0 1 1 1
10 × 64 kbit/s unrestricted
0 0 0 1 1 0 0 0
11 × 64 kbit/s unrestricted
0 0 0 1 1 0 0 1
12 × 64 kbit/s unrestricted
0 0 0 1 1 0 1 0
13 × 64 kbit/s unrestricted
0 0 0 1 1 0 1 1
14 × 64 kbit/s unrestricted
0 0 0 1 1 1 0 0
15 × 64 kbit/s unrestricted
0 0 0 1 1 1 0 1
16 × 64 kbit/s unrestricted
0 0 0 1 1 1 1 0
17 × 64 kbit/s unrestricted
0 0 0 1 1 1 1 1
18 × 64 kbit/s unrestricted
0 0 1 0 0 0 0 0
19 × 64 kbit/s unrestricted
0 0 1 0 0 0 0 1
20 × 64 kbit/s unrestricted
0 0 1 0 0 0 1 0
21 × 64 kbit/s unrestricted
0 0 1 0 0 0 1 1
22 × 64 kbit/s unrestricted
0 0 1 0 0 1 0 0
23 × 64 kbit/s unrestricted
0 0 1 0 0 1 0 1
spare
0 0 1 0 0 1 1 0
25 × 64 kbit/s unrestricted
0 0 1 0 0 1 1 1
26 × 64 kbit/s unrestricted
0 0 1 0 1 0 0 0
27 × 64 kbit/s unrestricted
0 0 1 0 1 0 0 1
28 × 64 kbit/s unrestricted
0 0 1 0 1 0 1 0
29 × 64 kbit/s unrestricted
3.55 Transmission medium requirement prime
The format of the transmission medium requirement prime parameter field is shown in Figure 54, except that
the coding rules for optional parameter are applied.
The following codes are used in the transmission medium requirement prime parameter field:
0 0 0 0 0 0 0 0
speech
0 0 0 0 0 0 0 1
spare
0 0 0 0 0 0 1 0
reserved for 64 kbit/s unrestricted
0 0 0 0 0 0 1 1
3.1 kHz audio
0 0 0 0 0 1 0 0
reserved for alternate speech (service 2)/64 kbit/s unrestricted (service 1)
0 0 0 0 0 1 0 1
reserved for alternate 64 kbit/s unrestricted (service 1)/speech (service 2)
0 0 0 0 0 1 1 0
reserved for 64 kbit/s preferred
0 0 0 0 0 1 1 1
reserved for 2 × 64 kbit/s unrestricted
0 0 0 0 1 0 0 0
reserved for 384 kbit/s unrestricted
0 0 0 0 1 0 0 1
reserved for 1536 kbit/s unrestricted
0 0 0 0 1 0 1 0
reserved for 1920 kbit/s unrestricted
3.56 Transmission medium used
The format of the transmission medium used parameter field is shown in Figure 54, except that the coding
rules for optional parameter are applied.
 42 
Załącznik nr 2  Zalecenie Q.763
The codings are identical to codings in Subclause 3.55.
3.57 User service information
The format of the user service information parameter field is shown in Figure 55. This format is the same as
the Bearer capability information element from Recommendation Q.931 and not all capabilities coded here are
supported at this time.
87654321
1 ext. Coding standard Information transfer capability
2 ext. Transfer mode Information transfer rate
2a Rate multiplier
3 ext. Layer ident. User information Layer 1 protocol
4 ext. Layer ident. User information Layer 2 protocol
5 ext. Layer ident. User information Layer 3 protocol
NOTE 1  Octet 2a is required if octet 2 indicates multirate (64 kbit/s base rate); otherwise, it shall not be present.
NOTE 2  Octets 3, 4, 5 or any combination of these octets may be omitted. Octet 3 may be extended as described in
Recommendation Q.931.
Figure 55/Q.763  User service information parameter field
The codes to be used in the subfields of the user service information parameter field is defined in the Bearer
capability information element in Recommendation Q.931.
3.59 User teleservice information
The format of the user teleservice information parameter field is shown in Figure 56. This format is the same
as the High Layer Compatibility information element from Recommendation Q.931 and not all capabilities
coded here are supported at this time.
87654321
1 ext. Coding standard Interpretation Presentation
2 ext. High layer characteristics identification
3 ext. Extended layer characteristics identification
Figure 56/Q.763  User teleservice information parameter field
The codes to be used in the user teleservice information parameter field are defined in the High layer
compatibility information element in Recommendation Q.931.
3.60 User-to-user indicators
The format of the user-to-user indicators parameter field is shown in Figure 57.
87654321
HGFEDCBA
Figure 57/Q.763  User-to-user indicators parameter field
The following codes are used in the user-to-user indicators parameter field:
bit A: Type
0 request
1 response
If bit A equals 0 (request):
bits C B: Service 1
0 0 no information
0 1 spare
1 0 request, not essential
1 1 request, essential
bits E D: Service 2
 43 
Załącznik nr 2  Zalecenie Q.763
0 0 no information
0 1 spare
1 0 request, not essential
1 1 request, essential
bits G F: Service 3
0 0 no information
0 1 spare
1 0 request, not essential
1 1 request, essential
If bit A equals 1 (response):
bits C B: Service 1
0 0 no information
0 1 not provided
1 0 provided
1 1 spare
bits E D: Service 2
0 0 no information
0 1 not provided
1 0 provided
1 1 spare
bits G F: Service 3
0 0 no information
0 1 not provided
1 0 provided
1 1 spare
bit H: Network discard indicator
0 no information
1 user-to-user information discarded by the network
3.61 User-to-user information
The format of the user-to-user information parameter is shown in Figure 58.
87654321
1
:
:
User-to-user information
:
n
Figure 58/Q.763  User-to-user information parameter field
The format of the user-to-user information parameter field is coded identically to the protocol discriminator
plus user information field described in Recommendation Q.931.
3.63 CCSS
The format of the CCSS parameter field is shown in Figure 60.
87654321
HGFEDCBA
Figure 60/Q.763  CCSS parameter field
The following codes are used in the CCSS parameter field:
bit A: CCSS call indicator
 44 
Załącznik nr 2  Zalecenie Q.763
0 no indication
1 CCSS call
bits H-B: spare
3.64 Call transfer number
The format of the call transfer number parameter field is shown in Figure 61.
87654321
1
O/E Nature of address indicator
2
spare Numbering plan indicator Address presentation Screening indicator
restricted indicator
3
2nd address signal 1st address signal
:
:
m
Filler (if necessary) nth address signal
Figure 61/Q.763  Call transfer number parameter field
The following codes are used in the subfields of the call transfer number parameter field:
a) Odd/even indicator (O/E): as Subclause 3.9 a).
b) Nature of address indicator
0 0 0 0 0 0 0 spare
0 0 0 0 0 0 1 subscriber number (national use)
0 0 0 0 0 1 0 unknown (national use)
0 0 0 0 0 1 1 national (significant) number (national use)
0 0 0 0 1 0 0 international number
1 1 1 1 1 1 1 spare
c) Numbering plan indicator
0 0 0 spare
0 0 1 ISDN (Telephony) numbering plan (Recommendation E.164)
0 1 0spare
0 1 1 Data numbering plan (Recommendation X.121) (national use)
1 0 0 Telex numbering plan (Recommendation F.69) (national use)
1 0 1 Private numbering plan (national use)
1 1 0 reserved for national use
1 1 1 spare
d) Address presentation restricted indicator
0 0 presentation allowed
0 1 presentation restricted
1 0spare
1 1 spare
e) Screening indicator
0 0 user provided, not verified
0 1 user provided, verified and passed
1 0 user provided, verified and failed
1 1 network provided
f) Address signal
0 0 0 0 digit 0
0 0 0 1 digit 1
0 0 1 0 digit 2
0 0 1 1 digit 3
0 1 0 0 digit 4
0 1 0 1 digit 5
0 1 1 0 digit 6
 45 
Załącznik nr 2  Zalecenie Q.763
0 1 1 1 digit 7
1 0 0 0 digit 8
1 0 0 1 digit 9
1 0 1 0spare
1 0 1 1 code 11
1 1 0 0 code 12
The most significant address signal is sent first. Subsequent address signals are sent in successive 4-bit
fields.
3.68 Network management controls
The format of the network management controls parameter field is shown in Figure 65.
87654321
HGF EDCBA
Figure 65/Q.763  Network management controls parameter field
The following codes are used in the network management controls parameter field:
bit A: Temporary Alternative Routeing (TAR) indicator
0 no indication
1 TAR controlled call
bits G-B: spare
bit H: Extension indicator: as Subclause 3.25 a).
3.69 Circuit assignment map
The format of the circuit assignment map parameter field is shown in Figure 66.
87654321
1 spare Map type
2 87654321
3 16 15 14 13 12 11 109
4 24 23 22 21 20 19 18 17
5 spare 31 30 29 28 27 26 25
Figure 66/Q.763  Circuit assignment map parameter field
The following codes are used in the circuit assignment map parameter field:
a-1) Map type:
0 0 0 0 0 0 spare
0 0 0 0 0 11544 kbit/s digital path map format (64 kbit/s base rate)
0 0 0 0 1 0 2048 kbit/s digital path map format (64 kbit/s base rate)
a-2) bits 8,7, octet 1: spare
b-1) Map format (octets 2 to 5):
Each bit position on the map (octets 2 to 5) indicates whether the corresponding 64 kbit/s circuit is
used in the N × 64 connection. The bits are coded as follows:
0 64 kbit/s circuit is not used
1 64 kbit/s circuit is used
Octet 5 is not used for 1544 kbit/s digital path map.
b-2) bit 8, octet 5: spare
3.72 Call diversion treatment indicators
The format of the call diversion treatment indicators parameter field is shown in Figure 69.
 46 
Załącznik nr 2  Zalecenie Q.763
87654321
HGF EDCBA
Figure 69/Q.763  Call diversion treatment indicators parameter field
The following codes are used in the call diversion treatment parameter field:
bits BA: Call to be diverted indicator
0 0 no indication
0 1 call diversion allowed
1 0 call diversion not allowed
1 1 spare
bits G-C: spare
bit H: Extension indicator: as Subclause 3.25 a).
3.74 Call offering treatment indicators
The format of the call offering treatment indicators parameter field is shown in Figure 70:
87654321
HGF EDCBA
Figure 70/Q.763  Call offering treatment indicators parameter field
The following codes are used in the call offering treatment parameter field:
bits BA: Call to be offered indicator
0 0 no indication
0 1 call offering not allowed
1 0 call offering allowed
1 1 spare
bits G-C: spare
bit H: Extension indicator: as Subclause 3.25 a).
3.76 Conference treatment indicators
The format of the conference treatment indicators parameter field is shown in Figure 71.
87654321
HGF EDCBA
Figure 71/Q.763  Conference treatment indicators parameter field
The following codes are used in the conference treatment parameter field:
bits BA: Conference acceptance indicator (Note)
0 0 no indication
0 1 accept conference request
1 0 reject conference request
1 1 spare
NOTE  Applicable to the conference and three-party supplementary services.
bits G-C: spare
bit H: Extension indicator: as Subclause 3.25 a).
3.78 UID action indicators
The format of the UID action indicators parameter field is shown in Figure 73.
 47 
Załącznik nr 2  Zalecenie Q.763
87654321
HGF EDCBA
Figure 73/Q.763  UID action indicators parameter field
The following codes are used in the UID action indicators parameter field:
bit A: Through-connection instruction indicator
0 no indication
1 through-connect in both directions
bit B: T9 timer instruction indicator
0 no indication
1 stop or do not start T9 timer
bits G-C: spare
bit H: Extension indicator: as Subclause 3.25 a).
3.79 UID capability indicators
The format of the UID capability indicators parameter field is shown in Figure 74:
87654321
HGF EDCBA
Figure 74/Q.763  UID capability indicators parameter field
The following codes are used in the UID capability indicators parameter field:
bit A: Through-connection indicator
0 no indication
1 through-connection modification possible
bit B: T9 timer indicator
0 no indication
1 stopping of T9 timer possible
bits G-C: spare
bit H: Extension indicator: as Subclause 3.25 a).
3.82 Application transport parameter (APP)
The format of the application transport parameter field is shown in Figure 77.
7 6 5 4 3 2 1
1 ext. Application context identifier
2 ext. spare SN R
I CI
3 ext. SI APM segmentation indicator
4 ext. Segmentation local reference
5a
: 1.1.1. Encapsulated application information
5n
Figure 77/Q.763 - Application transport parameter field
The following codes are used in the application transport parameter field:
a) Extension indicator (ext.): as Subclause 3.25 a).
b) Application context identifier (ACI)
0 0 0 0 0 0 0 Unidentified Context and Error Handling (UCEH) ASE
0 0 0 0 0 0 1 PSS1 ASE (VPN)
0 0 0 0 0 1 0spare
0 0 0 0 0 1 1 Charging ASE
 48 
Załącznik nr 2  Zalecenie Q.763
0 0 0 0 1 0 0 GAT
NOTE - The compatibility mechanism as defined in Q.764 is not applicable to this field.
c) Application transport instruction indicators
bit 1 Release call indicator (RCI)
0 do not release call
1 release call
bit 2 Send notification indicator (SNI)
0 do not send notification
1 send notification
d) APM segmentation indicator
0 0 0 0 0 0 final segment
NOTE - The compatibility mechanism as defined in Q.764 is not applicable to this field.
e) Sequence indicator (SI)
0 subsequent segment to first segment
1 new sequence
f) Segmentation local reference (SLR)
g) Encapsulated application information:
Contains the application specific information.
The format and coding of this field is dependent upon the APM-user application and defined in the
appropriate recommendation. For APM-user applications that wish to provide a service of transparent transport
of information (e.g. the case where existing information elements are defined for the transport of certain
information) as well as having the ability of passing additional network related information within the public
network, then the following guideline is provided:
It is suggested that this field be structured such that the first octet (i.e. first octet of first segment for
long APM-user information) is a pointer to information to be transported transparently. The pointer
value (in binary) gives the number of octets between the pointer itself (included) and the first octet (not
included) of transparent data. The pointer value all zeros is used to indicate that no transparent data is
present. The range of octets between the pointer octet and the first octet of transparent data (to which
the pointer octet points) contains the network related information to be passed between the applications
residing within the public network. The format and coding of both the transparent information and the
network related information is application specific and defined in the appropriate recommendation.
3.83 CCNR possible indicator
The format of the CCNR possible indicator parameter field is shown in Figure 78.
87654321
HGFEDCBA
Figure 78/Q.763 - CCNR possible indicator parameter field
The following codes are used in the CCNR possible indicator parameter field:
bit A: CCNR possible indicator
0 CCNR not possible
1 CCNR possible
bits H-B: spare
3.86 Called directory number (national use)
The format of the called directory number parameter field is shown in Figure 81.
 49 
Załącznik nr 2  Zalecenie Q.763
87654321
1 O/E Nature of address indicator
2 INN Numbering plan indicator spare
3 2nd address signal 1st address signal
:
:
m Filler (if necessary) nth address signal
Figure 81/Q.763 - Called directory number parameter field
The following codes are used in the subfields of the called directory number parameter field:
a) Odd/even indicator (O/E): as Subclause 3.9 a).
b) Nature of address indicator
0000000 spare
0000001 subscriber number (national use)
0000010 unknown (national use)
0000011 national (significant) number (national use)
0000100 reserved
0000101 network-specific number (national use)
c) Numbering plan indicator
000 reserved
001 ISDN (Telephony) numbering plan (Recommendation E.164)
010 spare
011 reserved (national use)
100 reserved (national use)
101 reserved for national use
110 reserved for national use
d) Internal network number indicator (INN)
0 reserved
1 routeing to internal network number not allowed
e) Address signal
0000 digit 0
0001 digit 1
0010 digit 2
0011 digit 3
0100 digit 4
0101 digit 5
0110 digit 6
0111 digit 7
1000 digit 8
1001 digit 9
1010 spare
1011 reserved
1100 reserved
1101 spare
1110 spare
1111 ST
The most significant address signal is sent first. Subsequent address signals are sent in successive 4-bit
fields.
f) Filler: as Subclause 3.9 f).
3.90 Network routeing number (national use)
The format of the network routeing number parameter field is shown in Figure 84.
 50 
Załącznik nr 2  Zalecenie Q.763
87654321
1 O/E Numbering plan indicator Nature of address indicator
2 2nd address signal 1st address signal
:
:
m Filler (if necessary) nth address signal
Figure 84/Q.763 - Network routeing number parameter field
The following codes are used in the subfields of the network routeing number parameter:
a) Odd/even indicator (O/E): as Subclause 3.9 a).
b) Numbering plan indicator
000 spare
001 ISDN (Telephony) numbering plan (Recommendation E.164)
010spare
011 spare
100 spare
101 spare
110 reserved for national use
111 reserved for national use
c) Nature of address indicator
0000 spare
0001 network routeing number in national (significant) number format (national use)
0010 network routeing number in network specific number format (national use)
d) Address signal
0000 digit 0
0001 digit 1
0010 digit 2
0011 digit 3
0100 digit 4
0101 digit 5
0110 digit 6
0111 digit 7
1000 digit 8
1001 digit 9
1010spare
1011 spare
1100 spare
1101 spare
1110spare
1111 spare
e) Filler: as Subclause 3.9 f).
3.96 Redirect capability (national use)
The format of the redirect capability parameter field is shown in Figure 89.
87654321
HGFEDCBA
Figure 89/Q.763 - Redirect capability parameter field
The following codes are used in the redirect capability parameter field:
bits CBA Redirect possible indicator
000 not used
001 redirect possible before ACM
010 redirect possible before ANM
 51 
Załącznik nr 2  Zalecenie Q.763
011 redirect possible at any time during the call
bit H Extension indicator: as Subclause 3.25 a).
3.97 Redirect counter (national use)
The format of the redirect counter parameter field is shown in Figure 90.
87654321
HGFEDCBA
Figure 90/Q.763 - Redirect counter parameter field
The following codes are used in the redirect counter parameter field:
bits EDCBA Redirect counter
binary value of the number of redirections
bits HGF spare
3.98 Redirect status (national use)
The format of the redirect status parameter field is shown in Figure 91.
87654321
HGFEDCBA
Figure 91/Q.763 - Redirect status parameter field
bits BA: Redirect status indicator
00 not used
01 acknowledgment of redirection
10 redirection will not be invoked
11 spare
bits GFEDC: spare
bit H: Extension indicator: as Subclause 3.25 a).
3.101 Number portability forward information (network option)
The format of the number portability forward information parameter field is shown in Figure 94.
87654321
HGFEDCBA
Figure 94/Q.763 - Number portability forward information parameter field
The following codes are used in the number portability forward information parameter field:
a) bits DCBA: Number portability status indicator
0000 no indication
0001 number portability query not done for called number
0010 number portability query done for called number, non-ported called subscriber
0011 number portability query done for called number, ported called subscriber
b) bits GFE: spare
c) bit H: Extension indicator: as Subclause 3.25 a).
 52 


Wyszukiwarka

Podobne podstrony:
Załącznik nr 18 zad z pisow wyraz ó i u poziom I
Załącznik 3 Przykłady ćwiczeń relaksacyjnych przy muzyce
Załącznik Nr
zalacznik nr 2
zalacznik nr 5 do SIWZ

NPOIK załącznik 2
Załącznik nr 1
odpady zalacznik 2
AOS załącznik nr 2 cz 9
Załącznik 3 Indywidualna karta spotkań z doradcą zawodowym
33976641,zalacznik
EATON! Zalaczniki
AOS załącznik nr 4 chemioterapia 28 08 09

więcej podobnych podstron