Message type: SETUP
Significance: global
Direction: both

Information element

Reference (subclause)

Direction

Type

Length

Protocol discriminator

4.2

Both

M

1

Call reference

4.3

Both

M

2-*

Message type

4.4

Both

M

1

Sending complete

4.5

Both

O (Note 1)

1

Repeat indicator

4.5

Both

O (Note 2)

1

Bearer capability

4.5

Both

M (Note 3)

4-12

Channel identification

4.5

Both

O (Note 4)

2-*

Progress indicator

4.5

Both

O (Note 5)

2-4

Network specific facilities

4.5

Both

O (Note 6)

2-*

Display

4.5

n ® u

O (Note 7)

(Note 8)

Keypad facility

4.5

u ® n

O (Note 9)

2-34

Signal

4.5

n ® u

O (Note 10)

2-3

Calling party number

4.5

Both

O (Note 11)

2-*

Calling party subaddress

4.5

Both

O (Note 12)

2-23

Called party number

4.5

Both

O (Note 13)

2-*

Called party subaddress

4.5

Both

O (Note 14)

2-23

Transit network selection

4.5

u ® n

O (Note 15)

2-*

Repeat indicator

4.5

Both

O (Note 16)

1

Low layer compatibility

4.5

Both

O (Note 17)

2-18

High layer compatibility

4.5

Both

O (Note 18)

2-5

NOTES

1. Included if the user or the network optionally indicates that all information necessary for call establishment is included in the SETUP message.

2. The Repeat indicator information element is included immediately before the first Bearer capability information element when the bearer capability negotiation procedure is used (see Annex L).

3. May be repeated if the bearer capability negotiation procedure is used (see Annex L). For bearer capability negotiation, two Bearer capability information elements may be included in descending order of priority, i.e., highest priority first. Although support of multiple Bearer capability information elements may not be supported on all networks, on networks that do support it, and through suiTable subscription arrangements, two Bearer capability information elements may be included (see 5.11). When they are not preceded by a Repeat indicator information element, they are included in ascending order of priority.

4. Mandatory in the network-to-user direction. Included in the user-to-network direction when a user wants to indicate a channel. If not included, its absence is interpreted as "any channel acceptable".

5. Included in the event of interworking or in connection with the provision of in-band information/patterns.

6. Included by the calling user or the network to indicate network specific facilities information (see Annex E).

7. Included if the network provides information that can be presented to the user.

8. The minimum length is 2 octets; the maximum length is network dependent and is either 34 or 82 octets.

9. Either the Called party number or the Keypad facility information element is included by the user to convey called party number information to the network. The Keypad facility information element may also be included by the user to convey other call establishment information to the network.

10. Included if the network optionally provides additional information describing tones.

11. May be included by the calling user or the network to identify the calling user. Not included in the network-to-user direction for basic call control, but may be included for some supplementary services.

12. Included in the user-to-network direction when the calling user wants to indicate the calling party subaddress. Not included in the network-to-user direction for basic call control, but may be included for some supplementary services.

13. Either the Called party number or the Keypad facility information element is included by the user to convey called party number information to the network. The Called party number information element is included by the network when called party number information is to be conveyed to the user.

14. Included in the user-to-network direction when the calling user wants to indicate the called party subaddress. Included in the network-to-user direction if the calling user included a Called party subaddress information element in the SETUP message.

15. Included by the calling user to select a particular transit network (see Annex C).

16. Included when two or more Low layer compatibility information elements are included for low layer compatibility negotiation.

17. Included in the user-to-network direction when the calling user wants to pass low layer compatibility information to the called user. Included in the network-to-user direction if the calling user included a Low layer compatibility information element in the SETUP message. Two, three or four information elements may be included in descending order of priority, i.e. highest priority first, if the low layer compatibility negotiation procedures are used (see Annex J).

18. Included in the user-to-network direction when the calling user wants to pass high layer compatibility information to the called user. Included in the network-to-user direction if the calling user included a High layer compatibility information element in the SETUP message. Although support of multiple High layer compatibility information elements may not be supported on all networks, on networks that do support it, and through suiTable subscription arrangements, two High layer compatibility information elements may be included (see 5.12). When they are not preceded by a Repeat indicator information element, they are included in ascending order of priority.