Chapter 5

The Layer 3 Signaling Protocol

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Table of Contents
Purpose .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..3
ISDN’s User Signaling Layer 3 .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..4
A Direct Line to the ISDN Order Desk .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..6
What Dialog is for .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..8
Message Groups - For Call Control .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 10
Call Establishment Messages . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 12
Call Information Phase Messages .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 14
Call Clearing Messages . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 16
Miscellaneous Messages .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 18
Global Call Control . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 20
What is Globally Controlled? .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 22
Restart Procedures .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 24
Message Dialog Zones .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 26
Basic Message Construction .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 28
Element Construction / Parsing .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 30
Call Message Header Format . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 32
Call Reference Value Variations . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 34
Information Element Variations .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 36
Changing Code Sets with the Shift Elements .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 38
List of Current Elements .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 40
Description of Elements - Single Octet .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 42
Description of Elements - Variable Length .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 43
Description of Elements - Variable Length (cont.) . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 44
Description of Elements - Variable Length (cont.) . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 45
Compatibility Checking .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 46
Call States on the User Side .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 48
Call States on the Network Side .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 50
Setting up a Simple Call .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 52
Building a Setup Message .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 54
Faults in Setup .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 56
Faults After Call Proceeding .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 58
Cause codes . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 60
Overlap Sending .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 64
User - User Services .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 66
Non-call Associated Signaling .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 68
The Non-call Associated Service . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 70
The Real Service .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 72
Flow Control .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 74
Clearing the Temporary Connection .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 76
Circuit-mode Summary . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 78
Notes: . .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. 80

 1998 - Robert Blackshaw Page 5 - 1

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

This page intentionally left blank

Page 5 - 2  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Purpose

The purpose of this chapter is to first show how the Layer 3 signaling messages are formatted, and
second to illustrate how the circuit-mode subset of messages is used to establish B-Channels.

Brief descriptions of the messages and elements are given simply to explain their purpose. For full
descriptions of the messages and elements see Recommendation Q.931.

The Layer 3 signaling protocol is a large and complex protocol, difficult to cover in its entirety in
time-line diagrams. However, we will attempt to show as complete a usage as possible.

This chapter will also cover the two remaining portions of the signaling protocol of
Recommendation Q.931. The first of these protocols provides for user-to-user information transfer
over a temporary signaling connection. From the user’s viewpoint, this transfer takes place over
the D-Channel. How the network gets it from one end tothe other is up to the network operator.

The second protocol is for global control of the interface. It basically provides a mechanism for
getting the whole interface, or individual channels, out of any lockup conditions that might arise.

 1998 - Robert Blackshaw Page 5 - 3

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

ISDN’s User Signaling Layer 3

The final piece of the user’s access to the ISDN switch machine intelligence is the Layer 3 protocol
of the D-Channel. Layers 1 and 2 have provided us with D-Channel sharing and data-link functions
respectively. The Layer 3 protocol gives us the syntax and semantics for a useful dialogue.

It is worth reiterating that this D-Channel is a common channel for user-to-network signaling. It is
equitably shared among the terminals connected at one user-network interface and is always
available.

Layer 3 uses a message based protocol, this simply means that the user-network dialogue consists
of the exchange of messages selected from a total set that provides the context for call control.

This Layer 3 protocol is a very powerful protocol, rich in messages and parameters that permit
practically all conceivable dialogue interchanges for any type of call control.

It is also a dynamic protocol in the sense that it has ample room for expanding to meet new ISDN
requirements. It also has the ability of selecting other protocols at this layer.

It is by no means a simple protocol. However, this will only affect the implementers of ISDN
terminal devices, and not end-users. Implementation of Layer 3 (and Layers 1 and 2 as well) will
be done in the end terminal devices. It is then merely a function of how user-friendly the user-to-
terminal interface is implemented.

Page 5 - 4  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

ISDN’s User Signaling Layer 3

Uses a Common Channel for Signaling

Uses a Message Based Protocol

A Powerful Protocol

A Dynamic Protocol

 1998 - Robert Blackshaw Page 5 - 5

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

A Direct Line to the ISDN Order Desk

It is not illogical to think of the Layer 3 protocol as a direct line to the ISDN network operator’s
order desk. The difference is that ISDN instantly delivers whatever you order.

Of course, like anything that is ordered by a customer, ISDN can only deliver what is stocked, i.e.,
a service that the ISDN network operator offers.

This is why ISDN is able to offer all services over a single access line to the network. Regardless
of the network implementation, either as a single all-digital network, or as separate circuit-
switched, packet-switched, broadband, etc. networks behind the ISDN switch, the user only sees
that all services come across a single interface.

The Layer 3 (Q.931) messages flow between the terminal and the network, setting up the type of
connection that the user requires. There is a new definition in ISDN on what constitutes a call. A
B-Channel and a D-Channel pair and a reference number compose an ISDN call. All the Layer 3
messages have to do with a single call and not with the user-to-network interface (except for the
restart message). The user-to-network interface may have multiple calls outstanding on a single
interface. In addition to the B- and D-Channel pair, you will see that for each call you must supply
a call reference number, thus there are three elements to this single call. This concept will help in
understanding some of the messages.

Page 5 - 6  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

A Direct Line to the Order Desk

User ISDN
B-channel(s)

Call
Needs

D-channel

Call
Management

= Msgs to network

= Msgs from network

 1998 - Robert Blackshaw Page 5 - 7

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

What Dialog is for

Let us take a few moments to discover just what it is that all of these messages and elements are
supposed to do for us. After all, isn’t the present system adequate - just pick up the phone, press a
few buttons, and you have a connection - what could be better? This is admittedly a quick, simple
and effective method - but rather limited.

In ISDN with the passive bus wiring arrangements we discussed earlier, we have more than simply
voice telephones, or personal computers, or facsimile machines at the end of a single pair of wires,
i.e., one number for each device, and you generally know which you are calling. Now all three
devices are quite likely to be at the end of the same pair of wires.

In the initial state, the ISDN switch is waiting at the end of the D-channel for us to give it some
instructions (send a message). Naturally, it will still wish to know the number we are calling - that
at least does not change. But remember, we now have two channels available and so the ISDN
switch needs to know which one it should use or whether we will let it make the choice.

Because there may be several devices connected at the number we are calling we should specify
which device we are calling. If we know its sub-address we can specify that number, but if there is
no sub-address, or we don’t happen to know the number, we need to specify some details regarding
which device type should take the call. This uses some message elements for what is called
compatibility checking.

The basic message exchange amounts to sending the ISDN switch all of the above information,
either in a single message or broken down into smaller messages. Once the switch knows that it
has all the information it asks us to wait a moment while it sets up our call. To do this the switch
coverts our message(s) into SS#7 messages and sends them off to the remote switch machine. This
switch then translates the SS#7 messages back into our format and sends them over the D-channel
to the called user. When an appropriate terminal device responds, the process reverses until we get
a message back to indicate that either a phone is ringing, or that a facsimile machine has answered.
At this point B-channels get cut through at either end and the connection is made.

More complex than before but also much more powerful.

Page 5 - 8  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

What Dialog is for

B1 ?
Term B2 ISDN
D

Initial State

B1 B1
Term B2 ISDN ISDN B2 Term
D D

SS7 SS7

Call Established

 1998 - Robert Blackshaw Page 5 - 9

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Message Groups - For Call Control

Recommendation Q.931 divides the Layer 3 call control messages into four broad groups.
The first group is the call establishment set of message; messages concerned with setting up all the
possible call or connection types available in ISDN.

The second group is the call information phase set of messages; messages concerned with such
things as user-to-user exchanges over the D-Channel during a B-Channel based call.

The third group is the call clearing set of messages; quite simply, messages concerned with taking
down existing calls.

The fourth, and final, group is the miscellaneous, or utility, set of messages; messages that have to
do with the exchange of information between user and network that do not directly set-up or clear
calls.

The next few pages will describe individual messages, by group and in alphabetical order. They
are not used in this sequence in actual practice; however, we will cover the procedural aspects of
using the messages later in this section.

Page 5 - 10  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Message Groups - For Call Control

Call Establishment

Call Information Phase

Call Clearing

Miscellaneous (Utility)

 1998 - Robert Blackshaw Page 5 - 11

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Call Establishment Messages

In order to get a general idea of the function of each message used in call establishment, we will
cover each one with a brief description. Note that the messages are in alphabetical order and not in
the order in which they are used.

Alerting: This message is sent from the called terminal equipment to indicate that the equipment
is alerting a human user. The network forwards this message to the calling user. In a passive bus
wiring arrangement, more than one terminal device may respond. You can see ISDN’s telephony
origins in the name of this message.

Call Proceeding: This message is sent by the network to the calling user in response to a setup
message to indicate that the network has sufficient information to proceed with the call setup. At
this point, the network will not accept any further called number information from the calling user.

Connect: This message is sent by the called terminal to the network when either a human user has
accepted the call, i.e., picked up the handset of a telephone, or by automatic answering terminals
in place of the alerting message.

Connect Acknowledge:Either the network or the user sends this message in response to a Connect
message. When sent by the network, it also serves to indicate which terminal device has been
awarded the call.

Progress: Either the network or an NT2, e.g. a PABX, sends this message to indicate that there is
some information available on the assigned B-Channel, i.e., an audible tone or announcement. The
progress message does not cause a state change.

Setup: The calling terminal sends this message to the network to initiate call setup. In ISDN, there
are two methods of sending the called number; the overlap sending mode where only a few or no
called number digits are included in the setup message, and the en-bloc sending mode where all
the called number digits are included in the setup message. This message usually specifies the type
of call and the protocols used at each layer.

Setup Acknowledge: The network or the called user sends this message to indicate reception of
the setup message and to also indicate that more called number information is required, i.e., used
in the overlap sending mode.

The numerics in the figure opposite are the code-points of the messages. Note that the first three
bits (8 - 6) separate the four message sets. All of these call establishment messages are also
included in ANSI-T1.607.

Page 5 - 12  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Call Establishment Messages

Alerting 000 00001

Call Proceeding 000 00010
Connect 000 00111
Connect Acknowledge 000 01111
Progress 000 00011
Setup 000 00101
Setup Acknowledge 000 01101

 1998 - Robert Blackshaw Page 5 - 13

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Call Information Phase Messages

This group of messages is the set that may be used during the information phase, i.e., sent while
the call is in the active, or connected state. Again, the order is alphabetical.

Resume: The user sends this message to the network in order to resume a suspended call. Since
more than one call may be suspended at an interface, suspension should be requested with an
associated call identity element. This element is a random number chosen by the user and, if
included in the suspend message, must be included in the resume message.

Resume Acknowledge: The network sends this message to the user issuing the resume message
to indicate that the call is returned to the active state and also which B-Channel it is using.

Resume Reject: The network sends this message to the requesting user to indicate that the
suspended call cannot be resumed, either due to an incorrect call identity element number, or
because the remote user has disconnected.

Suspend: A user in the active state sends this message to request that the network suspend the call
in progress and free the associated B-Channel. As noted above, a call identity element is usually
included.

Suspend Acknowledge: The network sends this message in response to a suspend message when
the network has successfully suspended the active call.

Suspend Reject: This message is sent by the network in response to a Suspend message when
some condition exists that prevents the network from suspending the call as requested.

User Information: The Recommendation used to include this message in this set. It now has been
relegated to the Supplementary Services category and is covered in Recommendation Q.957. It is
used by either the calling or called user to send out-of-band signaling information to the other user.
According to the latest Q.931 the User-user information element may be included in ALERTING,
CONNECT, DISCONNECT, PROGRESS, RELEASE, RELEASE COMPLETE, and SETUP
messages when sent over a temporary signaling connection (see later pages in this chapter).

Note: Suspend and Resume behave much as a network provided hold feature, except that they also
free the B-Channel. Their primary use is for either moving a terminal from one location to another
on the same bus, or for moving from one terminal to another terminal on the same bus. Apparently,
ANSI T1 felt that this is not a useful feature and neither of the suspend or resume messages, all six,
are included in T1-607.

The numerics in the figure opposite are the code-points of the messages. Note that the first three
bits (8 - 6) separate the four message sets. None of these messages are included in ANSI-T1.607.

Page 5 - 14  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Call Information Phase Messages

Resume 001 00110

Resume Acknowledge 001 01110
Resume Reject 001 00010
Suspend 001 00101
Suspend Acknowledge 001 01101
Suspend Reject 001 00001
User Information 001 00000

 1998 - Robert Blackshaw Page 5 - 15

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Call Clearing Messages

There are only three messages in the call clearing phase, which is quite logical since it should not
take a lot of protocol action just to clear a call.

Disconnect: This message is sent by either user to the network to indicate that they wish to clear
the active call. No actual releasing of either the B-Channel, the D-Channel, or the call reference is
done at this time. If the network sends this message to the user(s) it does indicate that the end-to-
end connection is cleared.

Release: This message is sent by either the user or network to indicate that the sender has
disconnected from the channel and intends to release the channel and the call reference. It further
indicates that the receiver of the message should release the channel and the call reference after
sending the release complete message.

Release Complete: This message is always sent by the network in response to a release message.
It should be sent by the user(s) in response to a release message for purposes of protocol symmetry.
It indicates that the sender has released the channel and the call reference, the channel is available
for reuse, and the receiving equipment should now release the call reference.

The numerics in the figure opposite are the code-points of the messages. Note that the first three
bits (8 - 6) separate the four message sets. All of these messages are also included in ANSI-T1.607.

Page 5 - 16  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Call Clearing Messages

Disconnect 010 00101

Release 010 01101
Release Complete 010 11010

 1998 - Robert Blackshaw Page 5 - 17

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Miscellaneous Messages

The final set of messages in the circuit-mode group may be used during various phases of the call.
Congestion Control: Either the user or the network would send this message to indicate
establishment or termination of flow control on user information messages. This is similar in
operation to the XON - XOFF or RR and RNR types of flow control. It has been deleted from
Q.931 call control and moved to the temporary signaling set.

Information: Either the user or the network sends this message to provide additional information.
This information may be related to call establishment, i.e., in either overlap sending or overlap
receiving mode, or to supply miscellaneous call-related information.

Notify: Either the user or the network sends this message to indicate information that pertains to
that call, e.g., to tell the non-requesting user that the call has been suspended.

Status: Either the user or the network sends this message in response to a status enquiry message,
or at any time to report certain error conditions.

Status Enquiry: This message is sent by the user or the network to solicit a status message in
response. It is mandatory that receivers of a status enquiry send a status message in response. This
is typically used when in doubt as to the state of the peer Layer 3 protocol entity.

The numerics in the figure opposite are the code-points of the messages. Note that the first three
bits (8 - 6) separate the four message sets. With the exception of the message (Congestion Control)
in italic type, these messages are also included in ANSI-T1.607.

Page 5 - 18  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Miscellaneous Messages

Congestion Control 011 11001

Information 011 11011
Notify 011 01110
Status 011 11101
Status Enquiry 011 10101

 1998 - Robert Blackshaw Page 5 - 19

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Global Call Control

A global call is not a call that circumnavigates the globe, but rather a means of globally controlling
the user-network interface. An ISDN user-network interface has, at a minimum, the capability of
having two or three calls in progress (if we count the D-Channel) and possibly up to 60 calls if we
consider a quasi-associated D-Channel for the primary rate. Some means had to be provided to
cover situations where the protocol state machines at either side of the interface get out of sync, or
lock up. Global call control provides this feature.

There are only three messages associated with global call control (as shown opposite) and a single
different element - the restart indicator element - in addition to other elements already covered.

There are also only three states for the global state machine at the user side:

REST 0 - A null state, i.e., neither a restart request nor a restart acknowledge in progress.

REST 1 - A restart request has been sent by the user, but no response has been received.

REST 2 - A restart request has been received from the network side, but no response has
been made.

The network states are the same except the word network replaces the word user in the above
definitions.

Page 5 - 20  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Global Call Control

Messages Reference (Q.931)

Restart 3.4.1
Restart Acknowledge 3.4.2
Status 3.4.3

Only one different element - the Restart Indication element.

Three states:
Rest 0
Rest 1
Rest 2

 1998 - Robert Blackshaw Page 5 - 21

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

What is Globally Controlled?

In the global call control procedures, individual calls can be restarted, individual interfaces can be
restarted, and multiple interfaces can be restarted.

Restarting is simply a means of releasing all call information (e.g., call reference, channel
assignment) and driving the protocol state machines to a known state (i.e., the null state).

The key to this flexibility is in the restart indication element.

With this element, the initiator can request restart of a single call by indicating the channel that it
occupies.

The initiator may also restart an individual interface, in situations where non-associated signaling
is used by indicating the interface in question.

The initiator can also restart all interfaces, meaning every interface controlled by the non-
associated D-Channel.

Page 5 - 22  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

What is Globally Controlled?

One call (or channel)

One interface
All interfaces if non-associated signaling is present

Clears the channel(s)

Clears the interface

Clears call references

 1998 - Robert Blackshaw Page 5 - 23

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Restart Procedures

The restart procedures are quite simple, if drastic.

In the upper figure, the user has initiated restart procedures for a single channel (call). This requires
that the channel identification element be included in the restart message along with the restart
indication element. The network takes the required actions and sends a restart acknowledge
message with the same elements.

In the lower figure, the network has requested a complete interface restart by sending a restart
message with only the restart indication element. The channel identification element would only
be required if this were a primary rate interface with non-associated signaling and the interface was
one other than the one with the D-Channel. The user responds with a restart acknowledge and then
restarts the interface.

Page 5 - 24  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Restart Procedures

User Network
Restart [channel ID, restart ind.]

Restart [channel ID, restart ind.]

User Network
Restart [restart ind.]

Restart [restart ind.]

 1998 - Robert Blackshaw Page 5 - 25

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Message Dialog Zones

The designers of the Layer 3 message based protocol defined certain zones of the signaling dialog
in order to assign specific elements a zone of significance or action.

In the figure, a typical call is shown as the caller (the user on the left), the network, and the called
user on the right.

The zones of interaction are: zone A between the calling user and the network, zone B between the
network and the called user, and zone C within the network.

Q.931 defines messages as having significance in these zones in terms of local, access, dual, or
global significance. The truth table is:

• local significance = A or B

• access significance = A and B

• dual significance = A and C or C and B

• global significance = A and B and C

using the terms and and or in the Boolean sense.

You will find that Q.931 defines all messages in the set in one of these four terms of significance.
This relates all messages to the parties upon which they have an effect. This concept of local and
global significance has also been incorporated into the ISDN Protocol Reference model for NT2s
and for switches, but not for terminal devices (TEs). The significance of this is simply that the
PABXs (NT2s) and the switches would need to know what messages, or portions thereof, must be
passed on and what is dealt with strictly by the receiving PABX or switch machine. Note that some
messages, while marked as being of local significance, also may carry information of global
significance.

Page 5 - 26  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Message Dialog Zones

A C B

Calling Called
Network
User User

Local Significance = A or B
Access Significance = A and B
Dual Significance = A and C or C and B
Global Significance = A and B and C

 1998 - Robert Blackshaw Page 5 - 27

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Basic Message Construction

ISDN Layer 3 messages have a prescribed format, consisting of the header followed by such
elements as apply. This may differ from the OSI concepts of which you are familiar. Usually, at
any layer, the Protocol Data Unit (PDU) consists of a header followed by information, i.e., the data
from the layer above. For ISDN it may be useful to think of the Layer 3 messages as being an
expanded set of X.25 packet level procedures call connect/disconnect messages. In X.25, the call
request, etc. packets also have a prescribed content.

Following the Layer 3 header, there are two basic types of elements: multi-octet elements and
single octet elements. Both types have identifiers and parameters; however, the multi-octet
elements also have lengths specified. This length refers to the number of octets spanned by the
following parameters. In addition, some single octet elements only have identifiers where there are
no parameters.

What is accomplished in the message construction is that first you select an appropriate message
type, e.g., a setup message. The next step is to select the mandatory and optional elements that
make up that particular message. For example, a setup message needs a called party number
element. It must also have a bearer capability element to inform the network of the type of call,
e.g., voice, data, video, etc. It must also select a B-Channel using a channel identification element.
It may contain lower layer and higher layer compatibility elements if compatibility checking is to
be in effect at the called end. Compatibility checking is a process that supplies the called
terminal(s) with sufficient information that permits the terminal to determine if the incoming call
is of a type that the terminal can handle.

This is a complex and powerful protocol, capable of conveying large amounts of information
between the user and the network. We will cover the header construction and element formats in
later pages.

The Red Book version of Q.931 stated that message elements must be in ascending binary
sequence, according to the element identifier value. The network would ignore any elements that
were out of sequence. Q.931 now states that the network may process out of sequence elements if
it wishes to do so. It seems as if they once thought that the switch software was incapable of base
+ displacement programming and only operated with table lookup techniques. However, it is
probably best to obey this rule in order to be universal.

Page 5 - 28  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Basic Message Construction

MESSAGE
MULTI-OCTET ELEMENT
HEADER
IDENTIFIER

LENGTH
ELEMENT

ELEMENT PARAMETERS

ELEMENT

ELEMENT

ELEMENT SINGLE-OCTET ELEMENT

IDENT PARAM
ELEMENT

 1998 - Robert Blackshaw Page 5 - 29

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Element Construction / Parsing

Element construction and parsing is an important feature of the multi-octet element you need to
understand in order to comprehend what follows.

Many of the elements used in ISDN’s Layer 3 signaling protocol can have optional parameters.
Also, since many of the optional parameters can lead to multiple octets in their own right, they
needed a means of incorporating an indication of the length of each parameter in the protocol. For
example, when you look at the actual message formats in the Annexes, you will see that the octets
are numbered 3, 3a, 3b, etc. This indicates that the parameter contained in octet 3 may sometimes
extend one or two more octets. For parsing an element mere knowledge of the element length is
not sufficient. One also needs to know if individual octets are extended as well.

This method is the generally accepted use of the high-order bit of each octet as an extension
indicator. Thus, Q.931 devotes the high order bit of each element’s parameter octet to indicating if
this is the final octet of that specific parameter or if there is more to follow. If this bit is a binary
zero, it indicates more to follow. If it is a binary one, it indicates that this is the final parameter octet
of that specific element.

ISDN is an evolutionary architecture rather than simply a new type of network. As the ITU-T
introduced Broadband ISDN and other enhancements, the Layer 3 protocol was enhanced, in fact
they wrote a complete Recommendation (Q.2931) for B-ISDN signaling. This chosen technique,
of individual element extension, will make this a reasonably painless process for those who
incorporate the concept into their product offerings from the beginning.

Page 5 - 30  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Element Construction / Parsing

Element Component # 1

Element Component # 2

Element Component # 3

Element Component # 4

0 Component Parameter # 1

0 Component Parameter # 2

1 Component Parameter # 3

 1998 - Robert Blackshaw Page 5 - 31

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Call Message Header Format

The message header format is shown on the facing page. In this figure, the bits shown as zeroes
are unused and should be set to zero. In OSI, there was considerable discussion during the late
seventies regarding protocol identification within the layers. ISDN has elected to use such
identification and the first octet of the header serves this function. The assignment of the protocol
discriminator octet is as follows:

0000 0000
through reserved for use with user-user information.
0000 0011

0000 0111 reserved

0000 1000 indicates I.451 / Q.931

0001 0000
through reserved for other network layer, i.e., X.25
0011 1111

0100 0000
through reserved for national use
0100 1111

0101 0000
through reserved for other network layer, i.e., X.25
1111 1110

all other values reserved.

The call reference length value in octet 2 refers to the length of the call reference value that follows
in octets 3 and 3a (covered on the next page).

Finally, in octet 4 is the identification of the message type. Bit 8 is reserved for possible use as an
extension bit, leaving 128 possible message types identifiable. However, the all ones pattern, value
128, is used as an escape indication, leaving 127 possible message types. The header is then
followed by whatever elements are pertinent to the specific message type. Bits 7 & 6 identify the
message groups, while bits 1 - 5 distinguish the messages within each group. Q.931 covers the
respective bit assignments. In the earlier discussion of message types, the numerics shown in the
figures (what Q.931 refers to as code-points) are the binary values that are used in octet 4.

Page 5 - 32  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Call Message Header Format

8 7 6 5 4 3 2 1

Protocol Discriminator Octet 1

0 0 0 0 Call Ref. Length Octet 2

Call Reference Value Octet 3, 3a

0 Message Type Octet 4

Information

Elements

as required

 1998 - Robert Blackshaw Page 5 - 33

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Call Reference Value Variations

From the header description, it was seen that the call reference value could be from one to three
octets in length. Before describing the three variants, it might be well to define the purpose of the
call reference value.

With ISDN, there are at least two end-to-end information channels available at each interface, i.e.,
2B+D. It follows that an ISDN terminal, identified to the network by a single interface, could be
signaling for more than one call. Since the network only knows of this terminal by a single address,
we need some means of relating signaling information on a per-call basis. The call reference value
is this means.

The call reference value is of local significance at the interface only, i.e., it is not conveyed end-
to-end. At a minimum, the basic rate interface must support a value of one octet (octet 3) and the
primary rate interface a value of two octets (octets 3 and 3a). A dummy call reference value, where
octet 3 is omitted and a length value of all zeroes is placed in octet 2 is for use with
Recommendation Q.932 on Supplementary Services.

Bit 8 (F) of the octet 3 is a flag bit. This flag bit indicates the direction of signaling messages. When
the flag is zero, the message is sent from the originator of the call reference value. When the flag
is one, the message is sent to the originator of the call reference value.

Since the actual call reference value is an arbitrarily selected value, the flag bit avoids any
confusion should the user and the network happen to select the same value when referring to two
separate calls.

ANSI-T1.607 follows these same rules.

Page 5 - 34  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Call Reference Value Variations

8 7 6 5 4 3 2 1

Dummy 0 0 0 0 0 0 0 0 Octet 2

8 7 6 5 4 3 2 1

0 0 0 0 0 0 0 1 Octet 2
Single
F Call reference value (7bits) Octet 3

8 7 6 5 4 3 2 1

0 0 0 0 0 0 1 0 Octet 2

Double F Call reference value Octet 3

(15 bits) Octet 3a

8 7 6 5 4 3 2 1

Protocol Discriminator Octet 1

0 0 0 0 Call Ref. Length Octet 2

Call Reference Value Octet 3, 3a

0 Message Type Octet 4

Information

Elements

as required

 1998 - Robert Blackshaw Page 5 - 35

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Information Element Variations

There are two basic types of information elements: the single octet type and the variable length
type. To identify these basic types, the eighth bit of the first octet is set to a one for the single octet
type and is set to a zero for the variable length type.

To slightly complicate the issue, the single octet type also has two types, or rather sub-types. Type
1 is for an element that also carries some information content, e.g., parameters. Type 2 is for an
element that does not require any information content. Fortunately, the bit pattern 010 in bits 7 - 5
identifies all type 2 elements.

The Recommendation states that all unused bits in positions 4 - 1 for type 1 should be set to zeroes.
However, it also states that in order to not create a terminal device that would become obsolete
when they add extensions to the Recommendation, you should not reject an element simply
because any unused bits in positions 4 - 1 of a type 1 element are other than zero. In short, don’t
even bother to examine these bits for now. Since the 010 pattern in bits 7 - 5 is indicative of a type
2 element we may have 7 type 1 elements and 16 type 2 elements for a total of 23 single octet
elements.

In the variable length variant, the length specified in the second octet of the element is that of the
subsequent octets, i.e., from the third octet up to the last octet.

Remember that variable length elements use the bit 8 extension mechanism to indicate the position
of the last octet. As noted earlier this provides for the cases where certain parameter octets may or
may not be present and ensures correct parsing of the elements.

The Recommendation also states that a variable element may be present, but empty of parameters.
It further states that an element may be absent. Treat both cases the same. The example is a setup
message that contains an empty called number element, or does not contain that element. This case
is perfectly legitimate in the so-called overlap sending method of signaling.

Some networks use variable length subscriber numbers, while others use fixed length subscriber
numbers. North America uses the fixed length numbering plan while in Europe subscriber numbers
are predominantly of the variable length.

To accommodate both methods, we may signal the called number in two ways: the overlap method
(one or two digits at a time) or the en-bloc method (the complete number is included in the initial
setup message). With overlap sending, subsequent digits of the called number are sent in
information messages. Even certain North American implementations use the overlap sending
method since it is less demanding upon the TE.

ANSI-T1.607 follows these same rules.

Page 5 - 36  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Information Element Variations

8 7 6 5 4 3 2 1

1 Identifier Content Single Octet Type 1

8 7 6 5 4 3 2 1

1 Identifier Single Octet Type 2

8 7 6 5 4 3 2 1

0 Identifier

Length of Contents Variable Length

Contents (variable length)

8 7 6 5 4 3 2 1

Protocol Discriminator Octet 1

0 0 0 0 Call Ref. Length Octet 2

Call Reference Value Octet 3, 3a

0 Message Type Octet 4

Information

Elements

as required

 1998 - Robert Blackshaw Page 5 - 37

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Changing Code Sets with the Shift Elements

We claimed at the beginning that this signaling protocol is a dynamic and powerful protocol. We
have already seen that there can be up to 127 different message types. We have also seen that for
a single octet element there may be up to 23 elements defined (see page 5 - 38), and for a variable
length element there may be up to 128 elements defined (7 bits used).

If that does not prove adequate to ISDN’s life span, one of the single octet elements is a shift
element which permits leaving the Q.931 list, or code-set, and going to another code-set, i.e., either
extensions to the Q.931 Recommendation or another Recommendation.

This functions on a temporary basis, i.e., just for the next element in the message, or on a
permanent basis, i.e., it applies to all subsequent elements within that message. The rules state that
one may only shift to a higher numbered code-set, the implication is that for a permanent shift it is
not legal to return to the Q.931 code-set later in the message. However, please note that a locking
shift is only in effect for the message that contains the shift element. All subsequent messages
begin in codeset 0, i.e., Q.931. Bit 4 is the non-locking, locking indicator. Setting this bit to a binary
one indicates the temporary shift and binary zero indicates the permanent shift.

Code-sets 5 and 6 are not usable across national boundaries, code-set 6 is not even usable between
different network territories here in the U. S., for obvious reasons. Should you accidentally send
either code-set 5 or 6 elements across a national boundary they will be ignored, and thus
ineffective. ANSI T1 has declared that code-set 5 is reserved for ANSI T1.607, 608, and future
ANSI Standards. Unless Canada and Mexico follow the ANSI-T1 Standards it will require a
gateway or some bilateral agreement to get outside of the United States in any direction.

Since it is marked for private use, code-set 7 elements would be ignored by any public network
unless some agreement has been reached between the private network and the public network.

Since only four sets are identified, there remains room for another four sets for future expansion.
Code-set 0 (Q.931) is always the initially active (default) code-set for implementations following
the ITU-T Recommendations.

Page 5 - 38  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Changing Code Sets with Shift

8 7 6 5 4 3 2 1

1 0 0 1 1 n n n

Non-locking or next element shift

8 7 6 5 4 3 2 1

1 0 0 1 0 n n n

Locking or semi-permanent shift

Codesets (nnn)

0 0 0 = Q.931/I.451

1 0 1 = National Use (e.g., ANSI)

1 1 0 = Local Network Use

1 1 1 = User Specific

All others reserved

 1998 - Robert Blackshaw Page 5 - 39

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

List of Current Elements

The facing page shows a table of the existing elements used with circuit-mode operation, current
with the Blue Book version of Q.931.

The single octet elements, identified by the binary one in bit position eight are listed above the line.
The variable length elements are listed below the line and identified by the binary zero in bit
position eight. Bits shown are numbered 8 - 1 from left to right.

As can be seen, there are a number of elements available for requesting connection types (bearer
capability), etc. from the network. We will discuss each element’s purpose in the subsequent pages.

The rightmost column shows the maximum length possible for most of the elements. A setup
message for en-bloc sending could exceed the maximum length available in the LAP-D frame, and
so Study Group 11 defined a segmentation procedure during the recent study period.

In the Max # octets column, the abbreviation nd signifies that the length of the element is network
dependent and that no specific size is set by the Recommendation.

The note refers to the use of the escape for extension element that is restricted to codesets 5, 6, and
7, i.e., the national network, local network, and user specific sets respectively. In these cases, a
multi-octet element format is used with the escape for extension code (1111111) in octet 1, a length
field in octet 2, the codeset information element identifier in octet 3, and further information that
the element may require in subsequent octets. The use of bit 8 for extension is followed as in the
Q.931 coding formats.

ANSI T1.607 does not use or support elements whose Element Description is printed in italic type
in the facing table. ANSI T1.607 has two additional elements not in the Blue Book version of
Q.931 and these are printed in all italic type at the bottom of the table on the facing page. We do
have a report that indicates that ITU-T has added these two elements to Recommendation Q.932.

Note that there are new elements for the new packet-mode (with Q.931 call control). These
elements are covered in Chapter 9.

Legend:

ID Code = Identification of the element in binary

Element Description = Name of the element

Max # Octets = The maximum length of the element in octets

Page 5 - 40  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

List of Current Elements

Max #
ID Code Element Description Octets
1000xxxx Reserved 1
1001xxxx Shift 1
10100000 More data 1
10100001 Sending Complete 1
1011xxxx Congestion Level 1
1101xxxx Repeat Indicator 1
00000000 Segmented Message 4
00000100 Bearer Capability 12
00001000 Cause 32
00010000 Call Identity 10
00010100 Call State 3
00011000 Channel Identification nd
00011110 Progress Indicator nd
00100000 Network Specific Facilities nd
00100111 Notification Indicator 3
00101000 Display 34/82
00101001 Date / time 8
00101100 Keypad Facility 34
00110100 Signal 3
01101100 Calling Party Number nd
01101101 Calling Party Subaddress 23
01110000 Called Party Number nd
01110001 Called Party Subaddress 23
01111000 Transit Network Selection nd
01111001 Restart Indicator 3
01111100 Low Layer Compatibility 18
01111101 High Layer Compatibility 5
01111110 User - User 35/131
01111111 Escape (for extension) Note
00001100 Connected Number 2-19
00001101 Connected Subaddress 2-23

 1998 - Robert Blackshaw Page 5 - 41

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Description of Elements - Single Octet

In order to help understand their purpose, the following reasonably brief descriptions of the circuit-
mode elements are given. First, the single octet elements:

Shift: A single octet element that provides the capability to shift the protocol into another codeset
than Q.931. It operates in non-locking mode, i.e., only the next element is from the new codeset;
and in locking mode, i.e., all subsequent elements are from the new codeset until another shift
element occurs.

More Data: A single octet element used when sending user information messages to indicate that
the complete data is contained in more than one message.

Sending Complete: A single octet element used to indicate that the sender has forwarded all of the
called number digits.

Congestion Level: A single octet element used to indicate the current status of the sender, i.e.,
receiver ready or receiver not ready.

Repeat Indicator: Some elements are permitted to be repeated within a message. This element
indicates the number of repetitions.

Page 5 - 42  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Description of Elements - Variable Length

The next few pages will cover the variable length elements as briefly as possible. Note that all
circuit-mode elements are detailed in Q.931.

Bearer Capability: A large variable length element that indicates all of the possible values of the
bearer service being requested or provided. It defines the following parameters:

- coding standard (ITU-T, ISO/IEC, National, Network)

- information transfer capability (speech, digital, audio, digital with tones, video)
- transfer mode (circuit or packet)
- information transfer rate (64, 2X64, 384, 1536,1920 kbit/s, multirate)
- structure (8kHz integrity, service data unit integrity, unstructured *
- configuration (point-to-point, all others reserved)
- establishment (demand, all others reserved)
- symmetry (bidirectional symmetric, all others reserved)
- user information Layer 1 protocol (V.110, G.711, G.721, H.221, V.120, X.31, etc.)
- synchronous / asynchronous
- negotiation (in-band or out-of-band for V.110)
- user rate (75 bit/s to 56 kbit/s)
- intermediate rate (for rate adaptation, 8, 16, or 32 kbit/s)
- network independent clock (required / not required for both xmit and recv)
- flow control (required / not required for both xmit and recv)
- rate adaptation header (included / not included - V.120)
- multiframe establishment support in data link (V.120)
- mode of operation (bit transparent / protocol sensitive - V.120)
- logical link identifier negotiation (default or full negotiation - V.120)
- assignor / assignee (V.120)
- in-band / out-of-band negotiation (temp sig conn or LLI 0 - V.120)
- number of stop bits (1, 1.5, 2)
- number of data bits (5, 7, 8)
- parity (odd, even, none, forced to 0, forced to 1)
- duplex mode (half, full)
- modem type (V.21 to V.32, plus National or User specified)
- user information Layer 2 protocol (Q.921, X.25)
- user information Layer 3 protocol (Q.931, X.25)
* No longer part of the BC element, but set according to the transfer mode.

Call Identity: A variable length element that is used to carry a user provided identification number for
suspended calls. With multiple calls possible on even a basic rate interface, some means of tagging
suspended calls is needed.
Call State: A variable length element used to indicate the state of the sender’s Q.931 protocol state machine
in status messages. The actual state of the machine is given according to the definitions of Q.931 for either
user states, network states, or global states.

 1998 - Robert Blackshaw Page 5 - 43

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Description of Elements - Variable Length (cont.)

Called Party Number: A variable length element used to convey the called party’s ISDN (or other
numbering plan) number. Type of number, numbering plan, and number digits are covered.

Called Party Subaddress: A variable length element used to convey the called party’s terminal
subaddress. This is up to 20 octets of subaddress, either user specified or an X.213 NSAP.

Calling Party Number: A variable length element used to convey the calling party’s ISDN (or
other numbering plan) number. Type of number, numbering plan, and number digits are covered.
Also covers whether presentation is allowed/not allowed and what screening has been done.

Calling Party Subaddress: A variable length element used to convey the calling party’s terminal
subaddress. This is up to 20 octets of subaddress, either user specified or an X.213 NSAP.

Cause: A variable length element that is used to indicate call-progress codes (these may also be
called call non-progress codes). These cause codes may be the codes defined in Q.931, X.25, or
X.21.

Channel Identification: A variable length element used to indicate:

- which interface (implicitly or explicitly defined)

- basic interface or other, e.g., primary rate
- indicated channel is preferred / is exclusive
- D-channel (yes or no)
- information channel selection (no channel, B1, B2, or any channel)
- interface identifier (a number assigned by the network)
- coding standard (ITU-T, national, network, reserved)
- number or map (channel is identified by number or a bit map)
- channel type (B, H0, H11, or H12)
- channel number (in binary equivalent of the time slot)
- slot map (used when bit map identification is specified)

Display: A variable length element used to send information to the user that is displayable. This
assumes that there is some display capability in the user’s terminal equipment. Either 34 or 82
octets may be sent, depending on the network.
Date / time: A fixed length element that provides the date and time to the user.
High Layer Compatibility: A variable length element used to define the calling terminal’s Layer
4 to 7 protocols. Note that it does not specify the protocols layer by layer, but rather in terms of
overall standards, e.g., Teletex, MHS, OSI applications, etc. No negotiation is described for this
element.
Keypad Facility: A variable length element used to convey IA5 characters entered by the terminal
keypad, typically in the case of overlap sending.

Page 5 - 44  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Description of Elements - Variable Length (cont.)

Low Layer Compatibility: A large variable length element used to define the calling terminal’s
Layer 1 to 3 protocols, or used by the called terminal to negotiate Layer 1 to 3 protocols. This
element is practically a duplicate of the bearer capability element. The reason for its inclusion is
that in some cases of international calling the bearer capability may be altered, but the network will
not touch this element.

Network Specific Facilities: A variable length element used to request provision of certain
facilities that are unique to a network. It identifies whether the network is national or international
and identifies it either with the Carrier Identification Code (CIC) or the Data Network
Identification Code (X.121 DNIC).

Notification Indicator: A variable length element used to inform the user of information pertinent
to the call, i.e., call suspended, call resumed, bearer capability change.

Progress Indicator: A variable length element that is used for the same purpose as the progress
message, i.e., in-band tones and announcements, where a state change is needed.

Segmented Message: A variable length element used to indicate the presence of a segmented
message, i.e., one that spans two or more Layer 2 frames.

Signal: A variable length element used to inform the user’s terminal equipment which tone signal
it should generate, e.g., dial-tone, busy-tone, ringing-tone, etc.

Transit Network Selection: A variable length element used to select the desired transit network(s)
for a given call.

Restart Indicator: A three-octet element used to indicate whether a channel or the whole interface
is to be restarted.

User-User: A variable length element used to convey out-of-band (not on the B-Channel)
information between users.

Escape: A variable length element used to allow extension of the codeset. Note that this is not the
same as shift, which moves to another codeset.

 1998 - Robert Blackshaw Page 5 - 45

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Compatibility Checking

Compatibility checking is an important part of ISDN. We have seen that the premises wiring
schemes permit up to eight terminal devices on a single NT1.

The eight terminal devices need not all be digital telephones, in fact they will most likely be
different types of ISDN capable devices. Consider the case where this bus serves a work cell for a
single employee in an organization. There would be a digital telephone, most likely a personal
computer, and possibly a facsimile machine.

When someone calls this employee, the network will present the setup message, initiated by the
calling party, on the line addressed by the ISDN number, i.e., it is broadcast to any and all devices
on that bus. The calling user could select a specific device by means of the called party subaddress
element, assuming the caller knew all of the subaddresses. Since the network only carries
subaddress information between users but has no direct knowledge of these subaddresses; it is
unlikely that they will be published in directories. Few users will want to maintain large directories
of every subaddress they might ever use.

The calling user includes three elements in the original setup message (bearer, low layer, and high
layer elements) that describe the type of call. The calling user may also set a bit in the low layer
element indicating willingness to negotiate.

When this setup message is presented to the called number, all terminal devices connected on the
bus examine it. The digital telephone will ignore it, as will the personal computer. The Group 4
Fax machine will accept the call, and noting the negotiation possibilities, will include a low layer
element in its connect message suggesting Group 4 Fax at the highest data rate available in that
class.

Compatibility checking is described in detail in Annex B of Q.931 and the negotiation procedures
are described in Annex M of Q.931. This feature makes the use of the short passive bus scheme
viable as a single work cell feed from ISDN.

Note that although the bearer capability element is primarily for the user to request some bearer
service, it is also passed to the called user. The called user must check this element in addition to
the low layer capability element. The reason for this is that even if both elements start out with the
same parameters, the bearer capability could change, e.g., a voice call starts in Europe indicating
A-law speech and ends in North America indicating µ-law speech. If the terminal attempts to
connect using A-law, it won’t be an intelligible call because the North American gateway has
already performed the conversion between the two speech encodings.

Page 5 - 46  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Compatibility Checking

Network

Setup msg. with

Calling Bearer, Low Layer Called
User & High Layer User
elements

G4 Fax Digital Phone,

Pers. Comp.,
G4 Fax

Connect msg.
G4 Fax with Low Layer G4 Fax
element

 1998 - Robert Blackshaw Page 5 - 47

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Call States on the User Side

It is worthwhile going over the protocol machine call states for the user side of the interface as an
aid in understanding message sequences.

State U0: The null state where no call exists.

State U1: The call initiated state, meaning that the user has sent a setup message and is
awaiting a reply from the network.

State U2: The overlap sending state, meaning that the user has initiated a call with a setup
message that did not contain all of the called number information, and has received a setup
acknowledge message from the network.

State U3: The outgoing call proceeding state, meaning that the calling user has received a call
proceeding message from the network and is awaiting some indication from the called end.

State U4: The call delivered state, meaning that the calling user has received an indication that
the call has reached the called end, i.e., an alerting message.

State U6: The call present state, meaning that a called user has received a setup message from
the network but has not yet responded to that message.

State U7: The call received state, meaning that a called user’s terminal(s) has responded to a
setup message with an alerting message, but no human user has yet answered the incoming call.

State U8: The connect request state, meaning that a human user has answered the call, the
terminal has sent a connect message to the network but has not yet been awarded the call, i.e., a
connect acknowledge message has not been received.

State U9: The incoming call proceeding state, meaning that the user has sent a call proceeding
message to the network indicating that all information necessary for call establishment has been
received. In this case, the user is most likely a PABX or a private network.

State U10: The active state, meaning that all necessary Q.931 protocol exchanges have been
successfully completed and the users are, or may, exchange information.

State U11: The disconnect request state, meaning that the user has requested clearing of the call
with a disconnect message and is awaiting a response. Note that neither the B- or D-Channel
association, nor the call reference number has been released at this point.

State U12: The disconnect indication state, meaning that the user has received a disconnect
message from the network, indicating that the network has disconnected the end-to-end
connection, if one was in place.

Page 5 - 48  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Call States on the User Side (cont.)

State U15: The suspend request state, meaning that the user has requested suspension of the
call with a suspend message and is awaiting a response.

State U17: The resume request state, meaning that the user has requested resumption of a
suspended call with a resume message and is awaiting a response.

State U19: The release request state, meaning that the user has responded to a disconnect
message with a release message (or has sent a release message for other reasons) and is awaiting a
response. Note that at this time the user has released the
B-Channel.

State U25: The overlap receiving state, meaning that the user has acknowledged an incoming
setup message with a setup acknowledge message and is awaiting further called number
information. Again, this user is likely a PABX or private network.

Setup sent Setup rec’d

U1 U0 U6
Setup
Ack Setup rec’d
Call rec’d
Proc Rls U25
rec’d U2 Ack Call Alert sent
rec’d Proc
Setup sent
Ack
sent
U19
U3 U9 U7

Alert Rls Conn sent

rec’d sent

U4 U11 U12 U8

Disc Disc
Conn rec’d sent
rec’d Conn Ack rec’d

Susp req U10 Res ack

U15 U17
Res req

 1998 - Robert Blackshaw Page 5 - 49

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Call States on the Network Side

The call states on the network side of the interface mirror those of the user side with one addition.
State N0: This is the null state, meaning that no call exists with respect to this interface.

State N1: This is the call initiated state, meaning that the network has received a setup
message from the user but has not yet responded.

State N2: The overlap sending state, meaning that the network has sent a setup acknowledge
message to the calling user and is awaiting further information.

State N3: The outgoing call proceeding state, meaning that the network has sent a call
proceeding message to the calling user and is proceeding with the call set up.

State N4: The call delivered state, meaning that the network has received an alerting message
from the called user and has forwarded it to the calling user.

State N6: The call present state, meaning that the network has sent a setup message to the
called user but has not yet received a response.

State N7: The call received state, meaning that the network has received an alerting message
from the called user but has not received an answer.

State N8: The connect request state, meaning that the network has received a connect
message(s) from the called user but has not yet awarded the call, i.e., has yet to send the connect
acknowledge message.

State N9: The incoming call proceeding state, meaning that the network has received a call
proceeding message from the called user indicating that the user has the necessary called number
information.

State N10: The active state exists at the calling user interface when the network has sent a
connect message to the calling user. It exists at the called user interface when the network has
awarded the call, i.e., sent a connect acknowledge message.

State N11: The disconnect request state, meaning that the network has received a disconnect
message from the user.

State N12: The disconnect indication state meaning that the network has disconnected the end-
to-end connection and has sent a disconnect message to the user.

Note that the network has one more state (N22) than the user and that State N10 is different from
the user State U10 depending upon which interface is in question, i.e., calling or called. Also note
that the words incoming and outgoing are applied to all descriptions as seen from the user side of
the interface.

Page 5 - 50  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Call States on the Network Side (cont.)

State N15: The suspend request state, meaning that the network has received a suspend
message from the user but has not yet responded.

State N17: The resume request state, meaning that the network has received a resume message
from the user but has not yet responded.

State N19: The release request state, meaning that the network has sent a release message to
the user and is awaiting a response.

State N22: The call abort state, meaning that the network is in process of clearing an incoming
call at the called user interface for a point-multipoint (passive bus) configuration before the call
was awarded to any user.

State N25 The overlap receiving state, meaning that the network has received a setup
acknowledge message from the called user and may now send additional call information.

Setup rec’d Setup sent

N1 N0 N6
Setup
Ack sent Setup Ack rec’d
Call Call
Proc Rls
N2 Ack N25 Proc
sent rec’d
rec’d

Call
N19 Proc
N3 rec’d N9

Alert Rls Alert rec’d

sent sent
N22
N7
N4 N11 N12

Disc Disc Conn rec’d

Conn rec’d sent
sent
Conn Ack sent
N8
Susp req N10 Res ack

N15 N17
Res req

 1998 - Robert Blackshaw Page 5 - 51

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Setting up a Simple Call

Now that we have covered the circuit-mode messages and their elements, we are ready to use them.
In this first step, we will set up a simple voice circuit between two users. Please note that before
we can use these procedures, there must be a data-link connection established between the two user
interfaces and the network.

The calling user picks up the telephone and keys in the called number (we are assuming en-bloc
sending here). The telephone set sends a setup message with appropriate elements to the network.
The network forwards the setup message using the ISDN User Part of Signaling System No. 7
(SS#7), and sends a call proceeding message to the calling user’s set. At the called user interface
a reconstructed setup message is sent to the called user.

At the called user interface, we are assuming a passive bus with three telephone sets. The setup
message would have been broadcast; thus all three sets will respond with alerting messages and
start ringing their bells. The network only forwards the first alerting message toward the calling
user. This would cause ringing tone to be produced by the caller’s set.

A human responds by picking up the handset of set # 1 and it sends a connect message to the
network. This connect message is forwarded to the calling user, causing cut through of the
B-Channel and the call enters the active state. Meanwhile, the called user-network interface must
get the other two telephone sets back into the null state, which it does by sending release messages,
with cause code # 26 non-selected user clearing, to both sets.

Note that the network always responds to a connect message with a connect acknowledge message.
It is optional (but recommended) that the calling user’s set will respond as shown in this diagram.

At some point in time, the purpose of the call is completed, and the called user hangs up. The set
sends a disconnect message to the network. The network forwards a release indication via SS#7. It
also sends a release message to the called set and disconnects from the B-Channel. This set
disconnects from the channel and returns a release complete to the network then releases the call
reference number. When the network receives this message, it finally releases the call reference
number.

At the calling end, the SS#7 release indication causes a release message to be sent to the calling
user and the B-Channel to be disconnected. The calling user’s set releases the B-channel and sends
a release complete message to the network, then it releases the call reference. Upon receipt of this
release complete message, the network also releases the call reference.

Page 5 - 52  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Setting up a Simple Call

Calling User Network Called User

Setup
Call Proc Setup
Alerting1
Alerting Alerting2
Alerting3

Connect1
Connect Connect Ack1
Connect Ack Release2
Release3

Disconnect
Release Release
Release Comp Release Comp

 1998 - Robert Blackshaw Page 5 - 53

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Building a Setup Message

Murphy’s Law has not been repealed! Even simple calls can go wrong. Recommendation Q.931
has many examples. In order to illustrate what can go wrong, we will first examine just what the
terminal device had to do in order to establish even the simple call on the previous page.

Ignoring the initial actions of providing dial-tone once a human user lifted the handset, and then
accumulating the dialing digits, we will go directly to the setup message.

The left-hand figure describes the content of a setup message; the right-hand figure shows the
actual bit pattern for the fields we have chosen.

The first four octets (the header) are mandatory, so we must put the protocol discriminator in octet
1. Octet 2 has bits 8 - 5 set to zeroes (unused) according to Q.931, and bits 4 - 1 give the length of
the call reference. In this instance, we have chosen the simple single octet format, and the bit
pattern 0001001 is our random number choice. Bit 8 is set to zero, indicating that we are the ones
who set this number. Finally, the bit pattern 00000101 is the identifier of a setup message. Bits 8 -
6 are shaded here just to note the fact that all establishment messages have zeroes in these bit
positions.

The next five octets are the bearer capability element identified by 0000100 in bits 7 - 1 of the first
octet. Bit 8 as a zero indicates a variable length element. The next octet gives the length of the
remaining parameter octets, namely three. Octet 3 has bit 8 set to one to indicate that this is the
only octet of this parameter. Bits 7 - 6 indicate the ITU-T coding standard, and bits 5 - 1 indicate
speech mode. In octet 4, bits 7 - 6 indicate circuit-mode and bits 5 - 1 indicate 64 kbit/s. Octet 5
bits 7 - 6 indicate the Layer 1 protocol, and bits 5 - 1 indicate G.711 µ-law speech. In this case
octets 6 and 7 may be omitted.

The long 13 octet element is the called party number element, identified by the 1110000 bit pattern
in bits 7 - 1. The length is next in octet 2, in this case 11 octets of parameters. Octet 3 indicates a
national number in bits 7 - 5, and that it is an ISDN number in bits 4 - 1. Octets 4 to 13 are the actual
number in IA#5 characters, in this case 4105551212, or (410) 555-1212 in a recognizable form.
Here, bit 8 is not used as an extension indicator and is set to zero.

The last element we have chosen is the low layer compatibility element, shown in the last 5 octets.
Octets 1 and 2 give the element identification and length as before. Octet 3 indicates the ITU-T
standard in bits 6 & 7 (00) and speech in bits 1 - 5 (00000). Octet 4 indicates a transfer mode of
circuit in bits 6 & 7 (00) and a rate of 64 kbit/s in bits 1 - 5 (00001). Octet 5 indicates the user
information layer 1 protocol to be µ-law PCM.

Page 5 - 54  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Building a Setup Message

8 7 6 5 4 3 2 1
0 0 0 0 1 0 0 0 1
Information Element ?
0 0 0 0 0 0 0 1 2
Protocol discriminator m 0 0 0 0 1 0 0 1 3
Call reference m 0 0 0 0 0 1 0 1 4
Message type m 0 0 0 0 0 1 0 0 1
Sending complete 0 0 0 0 0 0 1 1 2
Repeat indicator 1 0 0 0 0 0 0 0 3
Bearer capability x 1 0 0 1 0 0 0 0 4
Channel identification 1 0 1 0 0 0 1 0 5
Facility 0 1 1 1 0 0 0 0 1
Progress indicator 0 0 0 0 1 0 1 1 2
Ntwk specific facilities 1 0 1 0 0 0 0 1 3
Display 0 0 1 1 0 1 0 0 4
Keypad facility 0 0 1 1 0 0 0 1 5
Signal 0 0 1 1 0 0 0 0 6
Switchhook 0 0 1 1 0 1 0 1 7
Feature activation 0 0 1 1 0 1 0 1 8
Feature indication 0 0 1 1 0 1 0 1 9
Calling party number 0 0 1 1 0 0 0 1 10
Calling party subaddr 0 0 1 1 0 0 1 0 11
Called party number x 0 0 1 1 0 0 0 1 12
Called party subaddr 0 0 1 1 0 0 1 0 13
Transit network select 0 1 1 1 1 1 0 0 1
Low layer compatibility x 0 0 0 0 0 0 1 1 2
High layer compatibility 1 0 0 0 0 0 0 0 3
User-user 1 0 0 1 0 0 0 0 4
1 0 1 0 0 0 1 0 5

 1998 - Robert Blackshaw Page 5 - 55

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Faults in Setup

Rather than attempt time-line diagrams for this part, we will use descriptive lists, since several
things can go wrong with a setup message.

A setup message that specifies a specific B-Channel (our example on the previous page did not)
with the exclusive option set will receive a release complete message from the network with cause
code # 44 Requested circuit/channel unavailable if that channel is in use.

A setup message that is sent when all B-Channels are in use will receive a release complete
message from the network with cause code # 34 No circuit/channel available.

A setup message with elements out of sequence might have the out of sequence element ignored.
This is optional for networks according to the Recommendation. If the element is a vital one (called
party number) the network will probably respond with setup acknowledge in place of call
proceeding, i.e., it would assume overlap sending mode.

A setup message with duplicated elements (ones that are not allowed to be duplicated) would get
no indication from the network as it would simply act upon the first of the duplicated elements and
ignore the rest.

A setup message with missing mandatory elements will receive a status message from the network
with cause code # 96 Mandatory information element is missing. Depending upon the capabilities
of the terminal, it might be necessary to clear the call.

A setup message with invalid content in any element will receive a release complete from the
network with cause code # 100 Invalid information element contents.

A setup message with unrecognized elements might receive nothing from the network, and the
network need only act on those elements that it recognizes. It is hoped that most networks will
return a status message with cause code # 99 Information element non-existent or not implemented.

Note that in most cases, the SDL charts attempt to illustrate the proper behavior.

Page 5 - 56  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Faults in Setup

Fault in Setup Network Action

B-Channel Unavailable Release Complete, cause # 44
No channels available Release Complete, cause # 34

Elements out of seq. May ignore those elements

Element duplicated Act on 1st one only

Missing mandatory elem, Status with cause # 96

Invalid content Release Complete, cause # 100

Unrecognized element Ignore or Status with cause # 99

 1998 - Robert Blackshaw Page 5 - 57

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Faults After Call Proceeding

Faults in setup messages are relatively simple compared to other situations that could arise. Take
the simple case of the human user having second thoughts after the network has initiated the call
and returned a call proceeding message.

By this time, the network has forwarded the setup message (contents) via SS#7 and action is
already taking place at the distant end of the call. Depending upon how far this activity has gotten
the network must forward a network originated disconnect indication via SS#7 with the appropriate
cause code. In this case, the only one that seems to apply is # 31 Normal, unspecified.

If the setup message has already been sent to the called user, any terminals that have responded
must be set back to the null state with one of the call clearing messages, e.g., Release according to
§ 5.3.2 (e) of Q.931.

The important aspect of all of this is that we remember that ISDN telephones or other terminal
devices are protocol state machines and they must be driven to the correct state. The older analog
telephone had only two states - on-hook or off-hook.

Actually, many of the problem states covered in Q.931 appear to be programming error states.
Presumably, once any terminal device is ready for market, such errors should be unlikely to occur,
except for those responsive to human input.

Page 5 - 58  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Faults After Call Proceeding

Calling User Network Called User

Setup
Call Proc Setup
Alerting1
Disconnect Alerting2
Alerting3
Release
Release1
Rel. Comp.
Release2
Release3

 1998 - Robert Blackshaw Page 5 - 59

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Cause codes

Cause codes are provided in Cause Information Elements to provide the user with call progress
information, although it might really be called non-progress information. Note in the following two
tables that the codes are broken into a Class and a Value. The following classes are identified in
Recommendation Q.850:

000 Normal event

001 Normal event

010 Resource unavailable

011 Service or option not available

100 Service or option not implemented

101 Invalid message, e.g., parameter out of range

110 Protocol error, e.g., unknown message

111 Interworking

Note that values of 128 and above are not used, if your terminal reports such a value there is a
problem with the terminal.

Page 5 - 60  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Cause codes
Class Value # Cause Diagnostic
000 0001 1 Unassigned number
000 0010 2 No route to transit network Transit Network ID
000 0011 3 No route to destination
000 0100 4 Send special information tone
000 0101 5 Misdialled trunk prefix (National use)
000 0110 6 Channel unacceptable
000 0111 7 Call awarded - estab chan
000 1000 8 Preemption
000 1001 9 Preemption - cct reserved
001 0000 16 Normal clearing
001 0001 17 User busy
001 0010 18 No user responding
001 0011 19 No user responding
001 0101 21 Call rejected User supplied
001 0110 22 Number changed
001 1010 26 Non sel. user clearing
001 1011 27 Destination out of service
001 1100 28 Invalid number format
001 1101 29 Facility rejected
001 1110 30 Response to Status Enquiry
001 1111 31 Normal, unspecified
010 0010 34 No cct/chan available
010 0011 35 Call queued
010 0110 38 Network out of order
010 0111 39 Frame PVC out of service
010 1000 40 Frame PVC operational
010 1001 41 Temporary failure
010 1010 42 Switch congestion
010 1011 43 Access info discarded Type of info discarded
010 1100 44 Req. cct/chan not available
010 1110 46 Precedence call blocked
010 1111 47 Resource unavailable
011 0001 49 QoS unavailable
011 0010 50 Requested fac. not subscribed
011 0100 52 Outgoing calls barred

 1998 - Robert Blackshaw Page 5 - 61

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

This page intentionally left blank

Page 5 - 62  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Cause codes
Class Value # Cause Diagnostic
011 0101 53 Outgoing calls barred (CUG)
011 0110 54 Incoming calls barred
011 0111 55 Incoming calls barred (CUG)
011 1001 57 Bearer capab. not authorized
011 1010 58 Bearer capab. not available
011 1110 62 Inconsistent information
011 1111 63 Service not available
100 0001 65 Bearer capab. not implemented
100 0010 66 Channel type not implemented
100 0101 69 Req. facility not implemented
100 0110 70 Only rest. digital capab. avail. (National use)
100 1111 79 Serv./opt. not implemented
101 0001 81 Invalid call reference value
101 0010 82 Iden channel does not exist Channel ID
101 0011 83 Call and ID do not match
101 0100 84 Call ID is in use
101 0101 85 No call suspended
101 0110 86 Call with this ID is cleared Clearing cause
101 0111 87 Not a member of CUG
101 1000 88 Incompatible destinantion Incompatible parameter
101 1010 90 Non existent CUG
101 1011 91 Invalid transit network select (National use)
101 1111 95 Invalid message
110 0000 96 Mandatory element missing Information element ID
110 0001 97 Message type non existent Message type
110 0010 98 Message incomp./non existent. Message type
110 0011 99 Info. element non existent Information element ID
110 0100 100 Invalid element contents Information element ID
110 0101 101 Msg. incomp. with call state Message type
110 0110 102 Recovery timer expired Timer number
110 0111 103 Parameter non existent (National use)
110 1110 110 Msg discarded/bad parameter
110 1111 111 Protocol error
111 1111 127 Interworking

 1998 - Robert Blackshaw Page 5 - 63

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Overlap Sending

In the previous example of setting up a simple call, en-bloc sending was assumed, i.e., all the called
number digits were included in the setup message. In this example we will show how overlap
sending differs from en-bloc sending.

The major difference in the two methods occurs in the call initiation at the calling user side. There
is a mode called overlap receiving, but this is for other purposes.*

As the diagram shows, the calling user sends a setup message toward the network. This setup
message may contain:

a) no called number information

b) incomplete called number information

c) called number information that the network does not know is complete

In case a) the network will return dial-tone if required, return a setup acknowledge message with
progress indicator # 8 in-band information or appropriate pattern is now available. In cases b) &
c), the network returns a setup acknowledge and awaits further called number information. The
calling user sends the called number information in one or more Information messages. The
number information must be in a called party number element or in keypad elements, but the two
elements are mutually exclusive, i.e., do it one way or the other, but do not mix elements. The final
information element should contain a sending complete indication (either a # or the sending
complete element), however, it is not mandatory.

When the network has determined that sufficient called number information is available, it sends
a call proceeding message to the calling user. The network will then forward a setup message
toward the called user. The balance of the process remains the same as before.

* The overlap receiving mode would be unlikely to occur at a simple called user interface, since
the complete ISDN network number only points to a T reference point. Therefore, the network
would, by definition, have the complete number before it could send a setup message to a called
user of this type. However, if the called user was an ISPBX, and DDI was in force, the network
could initiate the incoming call with a setup message, await a setup acknowledge message from the
ISPBX, and then forward the DDI digits. Similarly, in the case of interworking with a private
network, the ISDN network treats the private network as a rather large user. In this case, the initial
called number information points to the private network and then further called number
information addresses the private user attached to the private network.

ISPBX Integrated Services Private Branch Exchange (ISDN PBX)

DDI Direct Dialing Inward

Page 5 - 64  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Overlap Sending

Calling User Network Called User

Setup
Setup Ack
Info
Info
Call Proc Setup
Alerting1
Alerting Alerting2
Alerting3

Connect1
Connect Connect Ack1
Connect Ack Release2
Release3

Disconnect
Release Release
Release Comp Release Comp

 1998 - Robert Blackshaw Page 5 - 65

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

User - User Services

ISDN’s separate signaling channel, although to all respects terminating at the first switch, does
offer a user-to-user signaling capability unknown before ISDN. This capability would presumably
make use of Signaling System No. 7 (SS#7), but the network operator need not use SS#7 and might
simply forward such user information over a packet-switched network.

User - user services are designed to allow the passage of small amounts of user information in the
call setup message or during the active phase of a call. This user information travels over the D-
channel between the user and the network. A useful service for such things as password logon to
user devices, etc.

Recommendation I.257.1 defines three services which all require an associated call.

The services that I.257.1 provides are:

Service # 1 - Transfer of user-to-user information during the setup and clearing phases
of a call, with the user information embedded in the call control messages, i.e., using the user
information element.

Service # 2 - Transfer of user-to-user information during the setup phase of a call, but
independently of the call control messages. This implies use of the user information message.
I.257.1 states that user messages allow transmission of up to 128 octets per message.

Service # 3 - Transfer of user-to-user information during the active phase of a call, but
independently of the call control messages. Appears the same as service # 2, except for the call
phase, and has the same size limits.

Page 5 - 66  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

User - User Services

User A User B
Setup - OK if embedded
Active - No
Clearing - OK if embedded

Service # 1

User A User B
Setup - OK if separate
Active - No
Clearing - No

Service # 2

User A User B
Setup - No
Active - OK if separate
Clearing - No

Service # 3

 1998 - Robert Blackshaw Page 5 - 67

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Non-call Associated Signaling

Non-call associated signaling is essentially a facility which allows users to inter-communicate

without the necessity of having a call set up on a B-Channel. The service provides for up to 255
octets of user information per message, and is envisioned as one in which the number of messages
will be small. Some network operators may limit the number of messages that may be exchanged.

The non-call associated signaling service has always been under discussion for ISDN. However,
some administrations have steadfastly held out against offering such a service. It would seem that
this is still the case, but perhaps we may see this service offered by some network operators,
especially ones that do not have a separate packet-switched network against which it would
compete.

Page 5 - 68  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Non-call Associated Signaling

B B
User B ISDN ISDN B User
D D

SS#7

Pkt-sw.

 1998 - Robert Blackshaw Page 5 - 69

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

The Non-call Associated Service

A non-call associated signaling service is described in I.257.1, Q.87.1 and Q.87.2, Q.931 § 7.2
describes the procedures for the service.

Call setup is nearly identical to a circuit-mode call, with the following changes:

• the setup message identifies a temporary signaling connection on SAPI-0

• the bearer capability element indicates;

- unrestricted digital information as the transfer capability

- packet-mode as the transfer mode

- user information Layer 2 protocol as Q.921

- user information Layer 3 protocol as Q.931

• the channel identification element indicates;

- exclusive in the preferred / exclusive field

- D-Channel in the D-Channel indicator field

- no channel in the channel selection field

If the network finds the service unavailable or not authorized, the network may respond with a
release or release complete message with one of the following cause codes:

• #57 bearer capability not authorized

• #58 bearer capability not presently available

• #63 service or option not available, unspecified

• #65 bearer service not implemented

Do not despair, these are only the reasons why we can’t get the service. As soon as some network
operators gain experience with ISDN and SS#7, it will be offered if the regulators have the wisdom
to allow it.

Page 5 - 70  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

The Non-call Associated Service

User A Network User B

Setup

Release/
Rel Comp

 1998 - Robert Blackshaw Page 5 - 71

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

The Real Service

Given all the foregoing ways in which the network may refuse the service, the Q.931 §7.2 also
provides ways in which the service can be provided.

Assuming the user has done all the correct things in the setup message regarding bearer capability
and channel selection elements, the network may simply forward the setup message to the called
user.

The called user accepts the temporary signalling connection by sending a connect message to the
network. Once the network responds with a connect acknowledge message, the called user may
begin sending user information messages toward the calling user.

When the network sends the connect message to the calling user, the calling user may also begin
sending user information messages toward the called user.

Once this temporary signaling connection is established, both users may send information between
themselves by means of the user information message. A user information message contains a call
reference, a protocol discriminator, and the user-to user information element defined in Q.931
§3.3.13 (and also in Annex C). The users may also include the more data indication element if
required to indicate that the complete message block is contained in more than one user
information message. The network does not police the more data indicator.

Page 5 - 72  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

The Real Service

User A Network User B

Setup

Setup
Connect

Connect
User Info
User Info

 1998 - Robert Blackshaw Page 5 - 73

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Flow Control

If user information messages arrive at either user or the network too quickly to be processed, either
user or the network may employ congestion control (ISDN’s name for flow control).

Flow control is done with a congestion control message containing a congestion level element. If
you remember, this is an XON / XOFF type of flow control. When any user or the network receives
a congestion control message indicating receiver not ready, it must stop sending user information
messages.

Flow is restarted by the party who initially stopped the flow by sending a congestion control
message, indicating receiver ready, at which point user information messages may once again be
transmitted.

The figure only shows that the network stopped forwarding user information messages in response
to the first congestion control message. In practice, most networks will forward the congestion
control message immediately to the remote end and stop the user information messages at the
source.

Also note that this flow control is “half-duplex”. By stopping the flow from User B, User A does
not stop the flow from A to B.

Page 5 - 74  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Flow Control

User A Network User B

Setup

Setup
Connect

Connect
User Info
User Info
Con Cont
User Info
User Info
Con Cont

 1998 - Robert Blackshaw Page 5 - 75

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Clearing the Temporary Connection

In this case, clearing of the temporary signalling connection is slightly different than in the circuit-
mode case in that the disconnect message is not used.

The connection may be cleared by either of the users or by the network simply by sending a release
message. The proper response is the release complete message.

This is quite logical, since the disconnect message is designed for use when there is a B-Channel
involved in the call. Since, in this case, there is no call*, the disconnect message is not required.

* This is true in the ISDN sense because a call involves the B & D-Channels and a call
reference. In this case there is no B-Channel involved, thus it is not a call but a temporary signaling
connection.

Page 5 - 76  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Clearing the Temporary Connection

User A Network User B

Setup

Setup
Connect

Connect
User Info
User Info
Con Cont
User Info
User Info
Con Cont

Release

Release
Rel Comp

Rel Comp

 1998 - Robert Blackshaw Page 5 - 77

ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Circuit-mode Summary

We have covered some aspects of circuit-mode operation in ISDN. Recommendation Q.931

devotes all of §5 to this mode of operation, but not necessarily in the most straightforward manner.

The diagrams opposite illustrate just what we attempted to cover in this chapter. The upper diagram
represents the area of operation for the Q.931 protocol, i.e., it operates at Layer 3 and Layer 3 only.
As we saw in chapters 2 and 3 there are two or three other protocols operating below Q.931, but
this Layer 3 protocol only regards them as some black-box which provides a service. In fact the
bottom diagram show only the BRI protocols although Q.931 operates over both BRI and PRI.

The lower diagram shows all the ISDN protocols operating at Layers 1 to 3 as well as some other
protocols operating in the higher layers (4 to 7), but they are not the subject of any ISDN
Recommendations or standards.

Perhaps the best method of tracking the circuit-mode operation through this section is to use the
detailed SDL diagrams in Q.931. Begin with the null state diagram and follow a single message
occurrence to the next state. Find the detailed SDL for that state and proceed in a similar fashion
down a single path to the next state. Continue this for a complete call, e.g., from null to active to
cleared (back to null) and do this for all possible paths and you will find that it eventually becomes
clear.

With the information in this chapter, you should be able to find your way through all call states and
determine what events cause which change. Because there are many other items yet to cover, we
felt that further explanation was not warranted.

Page 5 - 78  1998 - Robert Blackshaw

Chapter 5 - The Layer 3 Signaling Protocol ISDN Training Course

Circuit Mode Summary

TE

ET

Layer 3 Signaling Messages Layer 3

ITU-T Q.931 ITU-T Q.931
or or
ANSI T1.607 ANSI T1.607

NT

TE
The Signaling Layer

Higher
Layers

ET

Layer 3 Signaling Messages Layer 3

ITU-T Q.931 ITU-T Q.931
or or
ANSI T1.607 ANSI T1.607

Layer 2 Layer 2
ITU-T Q.921 LAP-D ITU-T Q.921
or or
ANSI T1.602 ANSI T1.602
NT
B-Channel(s)
Layer 1 D-Channel
ITU-T I.430 Q-Channel ANSI T1.601
or ANSI ANSI Embedded Oper. Channel
ANSI T1.605 S-Channel(s) T1.605 T1.601 CRC + other functions

All Layers from 1 to 7

 1998 - Robert Blackshaw Page 5 - 79
ISDN Training Course Chapter 5 - The Layer 3 Signaling Protocol

Notes:

Page 5 - 80  1998 - Robert Blackshaw