Lucent Technologies DEFINITY Enterprise Communications Server Release 5, CallVisor, ASAI Protocol Reference Instructions Manual

							Codeset 0 Information Elements
Issue 6  June 1997
4-25
Progress Description (byte 4)
Bits
7654321
0000001 call is not end-to-end ISDN. Call prog. inband.
0000010 destination address is non-ISDN
0000011 origination address is non-ISDN
0000100 call has returned to the ISDN
0001000 in-band information now available 
						

							Information Elements
4-26Issue 6  June 1997 
Redirecting Number
The Redirecting Number IE shown in Figure 4-13 identifies the called party 
number from which call redirection/diversion/transfer occurred.
NOTE:
The ASAI specification permits the Redirecting Number IE to be repeated 
within a message. The ECS uses only a single occurrence of this IE across 
the ASAI interface and does not repeat it.
.
The contents of this field are coded as shown in Called Party Number.
Figure 4-13. Redirecting Number8  765 4321
Redirecting number
0  1 1 1 0 1 0 0 Byte     1
Information element identifier
Length of redirecting number contents     2
0/1 Type of number Numbering plan identification     3
ext (Note 1) (Note 1)
0/1 Presentation 0 0  0 Screening 3a*
ext indicator Spare Reserved indicator
1 00 0 Reason
ext Spare for redirection 3b*
0 Number digits
   4
Spare (Note 1) 
						

							Codeset 0 Information Elements
Issue 6  June 1997
4-27
The ECS does not expect an ASAI adjunct to send the optional bytes 3a and 3b; 
these are shown for compatibility with the ASAI specification. If bytes 3a/3b are 
received, they are ignored.
The adjunct should be prepared to parse this IE both with and without optional 
bytes 3a and 3b.
Presentation Indicator and Screening Indicator (octet 3a, bits 6-7 and 1-2): 
Presently the ECS includes the optional octets 3a and 3b so that the Reason for 
Redirection in Octet 3b is available to adjunct applications. The presentation 
indicator is always coded as “0 0” (Presentation Allowed); the Screening Indicator 
is always coded as “0 0” (User provided — not screened). PRI uses these octets 
at a network-user interface.
NOTE:
Reason for redirection (byte 3b, bits 4-1):
These reasons are included for completeness. They are shown for 
compatibility with the ASAI specification. The ECS does not expect optional 
byte 3b in any feature invocations where the Redirecting IE is
present.
Bits
4 3 2 1
0 0 0 1 Call forwarding busy or called DTE busy
0 0 1 0 Call forwarding no reply
1 0 0 1 Called DTE out of order
1 0 1 0 Call forwarding by the called DTE
1 1 1 1 Call forwarding unconditional or systematic call redirection 
						

							Information Elements
4-28Issue 6  June 1997 
Redirection Number
The Redirection Number IE shown in Figure 4-14 identifies the number toward 
which a call redirection/diversion/transfer occurred.
NOTE:
The contents of this IE field are coded as shown in Called Party Number.
Figure 4-14. Redirection Number
The ECS does not expect an ASAI adjunct to send bytes 3a or 3b; these are 
shown for compatibility with the ASAI specification. If bytes 3a/3b are received, 
those bytes are ignored.
NOTE:
Reason for redirection (byte 3b, bits 4-1):
These reasons are included for completeness and are shown for 
compatibility with the ASAI specification. The ECS does not expect optional 
byte 3b in feature invocations where the Redirection IE is present. 8  7 6 5 4321
Redirection number
0  1 1 1 0110Byte1
Information element identifier
Length of redirection number contents 2
0/1 Type of number Numbering plan identification 3
ext (see Note) (see Note)
0/1 Presentation 0 0  0 Screening 3a*
ext indicator Spare Reserved indicator
1 0 0 0 Reason 3b*
ext Spare for redirection
0 Number digits
    4
Spare (see Note) 
Bits
4 3 2 1
0 0 0 1 Call forwarding busy or called DTE busy
0 0 1 0 Call forwarding no reply 
						

							Codeset 0 Information Elements
Issue 6  June 1997
4-29
Restart Indicator
The Restart Indicator IE shown in Figure 4-15 identifies the class of facility to be 
restarted. This information element is always encoded to restart the “interface.”
Figure 4-15.  Restart Indicator Information Element
Class encodings (byte 3)1 0 0 1 Called DTE out of order
1 0 1 0 Call forwarding by the called DTE
1 1 1 1 Call forwarding unconditional or systematic call redirection
8  7654321
Restart Indicator
0  1111001Byte1
Information element identifier
Length of Restart Indicator contents 2
1 0000
Class 3
Ext spare
Bits
3 2 1
1 1 1 All Interfaces 
						

							Information Elements
4-30Issue 6  June 1997 
User to User Information
The User to User Information IE shown in Figure 4-16 conveys information 
between ASAI applications. The ECS carries user to user information 
transparently; it does not interpret or act on user to user information. This IE can 
have a maximum of 32 bytes of user information.
The user to user information element is coded as shown below:
Figure 4-16. User to User Information Element
Protocol Discriminator (Octet 3):87654321
User to User
0 1111110Octet 1
Information element Identifier
Length of User to User contents 2
Protocol discriminator 3
User information 4, etc.
Bits
87654321
0 0 0 0 0 0 0 0 User-specific protocol
00000100 IA5 characters 
						

							Codeset 6 Information Elements
Issue 6  June 1997
4-31
Codeset 6 Information Elements
The codeset 6 information elements (IEs) are Lucent Technologies-specific and 
include the ASAI information elements.
These codeset 6 IEs are:
Call Options
The Call Options IE shown in Figure 4-17 conveys information about options that 
may be used to establish a third party call.
Figure 4-17. Call Options Information ElementCall Options
Conference/Transfer 
Options
Counter
Data Item
Data Bit Map
Domain
Facility Information 
Element (FIE)
FeatureGeneric Billing Data 
Item
Lookahead Interflow
Management Information 
Element (MIE)   
Old Party Identifier
Originating Line Information
Party Identifier
Resource IdentifierResource Status
Service Circuit 
Specific Event
Status
Trunk Identification
Trunk Group/Trunk 
Status
User-Entered Code
Version
8  7654321
Call Options
0  1001011Byte   1
Information element identifier
Length of Call Options contents   2
1
Option  3
Ext
1
Value 4*
Ext 
						

							Information Elements
4-32Issue 6  June 1997 
ASAIBits
Option 
Encodings7 6 5 4 3 2 1 
(Byte 3, bits 70 0 0 0 0 0 0 Reserved
through 1)0 0 0 0 0 0 1 Number of rings before No Answer Event Report
0 0 0 0 0 1 0 Alerting order
0 0 0 0 0 1 1 Priority calling
0 0 0 0 1 0 0 Reserved
0 0 0 0 1 0 1 Reserved
0 0 0 0 1 1 0 Direct agent ACD call
0 0 0 0 1 1 1 Supervisor assist call
0 0 0 1 0 0 0 Reserved
0 0 0 1 0 0 1 Reserved
0 0 0 1 0 1 0 Tone Duration
0 0 0 1 0 1 1 Pause Duration
0 0 0 1 1 0 0 Return Acknowledgement Flag
0 0 0 1 1 1 0 Answering Machine Treatment
Value (Byte 4, 
bits 7 through 1)This field is coded as a binary number and is application-dependent. If 
the Option field = Alerting order, the Value field is coded as follows:
Bits
7 6 5 4 3 2 1
0 0 0 0 0 0 0 Alert calling endpoint first
0 0 0 0 0 0 1 Alert called endpoint first
If the Option field = Answer Machine Treatment, then the Value field is 
coded as follows:
Bits
7 6 5 4 3 2 1
0 0 0 0 0 0 0 Administered Treatment
0 0 0 0 0 0 1 Disconnect/Drop
0 0 0 0 0 1 0 Answer
If the Option field = Number of Rings before No Answer, then the Value 
field contains the binary encoded number of rings.
If the Option field = Tone Duration or Pause Duration, then the Value 
field contains the binary-encoded integer that is multiplied by 0.01 
seconds to compute a duration time or pause time.
If the Option field = Priority, Direct-Agent Call, Return Acknowledgment 
Flag, or Supervisor-Assist, the Value field is omitted. 
						

							Codeset 6 Information Elements
Issue 6  June 1997
4-33
Conference/Transfer Options
The Conference/Transfer IE shown in Figure 4-18 specifies nondefault actions for 
the Third Party Merge capability.
Figure 4-18. Conference/Transfer Options Information Element
Option8  7654321
Conference/Transfer Options
0  1001010Byte1
Information element identifier
Length of Conference/Transfer Options contents 2
1
Option 3
Ext
Bits
7 6 5 4 3 2 1
0 0 0 0 0 0 0 Reserved
0 0 0 0 0 0 1 Controller remains on merged 
call (for example, conference)
0 0 0 0 0 1 0 Controller drops off merged call 
(for example, transfer) 
						

							Information Elements
4-34Issue 6  June 1997 
Counter
The Counter IE shown in Figure 4-19 sends binary-encoded counts of various 
items in response to various query.
Figure 4-19. Counter Information Element
t
8  7654321
Counter
0  1000110Byte 1
Information element identifier
Length of Counter contents  2
1
Type of Counter  3
Ext
0/1
Value 4*
Ext
Type ofBits
Counter7 6 5 4 3 2 1
0 0 0 0 0 0 0 Any
0 0 0 0 0 0 1 Number of available trunks
0 0 0 0 0 1 0 Number of available call classifiers
0 0 0 0 0 1 1 Number of calls in queue
0 0 0 0 1 0 0 Number of logged-in agents
0 0 0 0 1 0 1 Number of available agents