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

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

Here you can view all the pages of manual Lucent Technologies DEFINITY Enterprise Communications Server Release 5, CallVisor, ASAI Protocol Reference Instructions Manual. The Lucent Technologies manuals for Communications System are available online for free. You can easily download all the documents as PDF.

Page 291

Notification Capability Group
Issue 6  June 1997
5-107
Notification: Endpoint Rejects an
Invalid/Protocol Violation FIE — Terminates
Association
Byte Description Byte Value Comments
Protocol Discriminator 0x08 BRI
CRV Length 0x01 or 0x02
First CRV Byte 0x?
Second CRV Byte0x?
Message Type 0x5a RELease COMplete
Locking Shift to Code Set 6 0x96
Facility IE 0x1c
Length of Facility IE 0x?? computed length
Q.932 Supplementary Service 0x91
component type tag 0xa4 REJECT
component length 0x?? computed length...

Page 292

Byte Level Messages
5-108Issue 6  June 1997 
Notification: Endpoint Aborts an Association
NOTE:
The switch always supplies a cause value when it aborts an association; the adjunct 
may optionally supply a cause value. Byte Description Byte Value Comments
Protocol Discriminator 0x08 BRI
CRV Length 0x01 or 0x02
First CRV Byte 0x?
Second CRV Byte0x?
Message Type 0x5a RELease COMplete
Locking Shift to Code Set 6 0x96
Facility IE 0x1c
Length of Facility IE 0x?? computed length
Q.932 Supplementary Service...

Page 293

Routing Capability Group
Issue 6  June 1997
5-109
Routing Capability Group
Routing: REGister Messages Sent by the switch
 A REGister message initiates an association on a CRV. All REGister messages 
have the Protocol Discriminator and the CRV followed by a REG type = 0x64.
Call Route Request
(Continued on next page) Byte Description Byte Value Comments
Protocol Discriminator 0x08 BRI
CRV Length 0x01 or 0x02
First CRV Byte 0x? assigned value
Second CRV Byte0x? assigned value
Message Type 0x64 REGister...

Page 294

Byte Level Messages
5-110Issue 6  June 1997 
switch Requests Call Route from Adjunct — (continued)
Byte Description Byte Value Comments
Calling Party Number0x6c
Length of Calling Party IE0x? computed length
Address Type & numbering Plan 
ID0x?? See Chapter 4
* Address digits0x??, 0x30 through 0x39, 0x23 (#), 0x2a (*)
Called Party Number IE 0x70
Length of Called Party Number 0x? computed length
Address Type & Numbering Plan 0x?? See Chapter 4
* ASCII Address digits 0x??, 0x30 through 0x39, 0x23 (#),...

Page 295

Routing Capability Group
Issue 6  June 1997
5-111
NOTE:
The Calling Number IE and the Trunk Identification IE are mutually exclusive. One or 
the other will be present.
Routing: FACility Messages Sent by the Adjunct
A FACility message is used to initiate an action with an existing association. All 
FACility messages have the Protocol Discriminator and the CRV followed by a 
FAC type = 0x62. Byte Description Byte Value Comments
The Domain IE 0x49
The length of the Domain IE 0x?
The Domain type = VDN 0x8c...

Page 296

Byte Level Messages
5-112Issue 6  June 1997 
Call Route Selection
Byte Description Byte Value Comments
Protocol Discriminator 0x08 BRI
CRV Length 0x01 or 0x02
First CRV Byte 0x?
Second CRV Byte0x?
Message Type 0x62 FACility
Locking Shift to Code Set 6 0x96
Facility IE 0x1c
Length of Facility IE 0x?? computed length
Q.932 Supplementary Service 0x91
component type tag 0xa1 INVOKE component
component length 0x?? computed length
component length0x?? long form (length > 127)
invoke identifier tag 0x02
invoke...

Page 297

Routing Capability Group
Issue 6  June 1997
5-113
Adjunct Call Routing Selection —(continued)
Byte Description Byte Value Comments
User-User IE0x7e User-to-user information
length of user-user0x?? computed length
protocol discriminator0x??
*user information0x??
Locking Shift to Code Set 6
(Note 1)0x96
User Entered Code IE (Note 2) 0x02 ASAI-provided digits
length of User Entered IE 0x?? computed length
type of user data 0x91 customer database provided
collect data indicator 0xc0 collected indication...

Page 298

Byte Level Messages
5-114Issue 6  June 1997 
NOTES:
This locking shift must be present if any of the optional IEs following it are  present; 
otherwise, it must be absent.
The ASAI application may either “collect digits” or “supply digits,” but not both. Thus, 
only one User Entered Code IE is permitted in the message.
Not currently used (ignored).
The Specific Event IE is present only when the application includes the User Code IE 
to “collect digits.”
Routing: RELease COMplete Messages Sent by
the...

Page 299

Routing Capability Group
Issue 6  June 1997
5-115
Routing: Request is Denied — Association
Terminated
Byte Description Byte Value Comments
Protocol Discriminator 0x08 BRI
CRV Length 0x01 or 0x02
First CRV Byte 0x?
Second CRV Byte0x?
Message Type 0x5a RELease COMplete
Locking Shift to Code Set 6 0x96
Facility IE 0x1c
Length of Facility 0x?? computed length
Q.932 Supplementary Service 0x91
component type tag 0xa3 return error
component length 0x?? computed length
invoke identifier tag 0x02
invoke...

Page 300

Byte Level Messages
5-116Issue 6  June 1997 
Routing: Endpoint Aborts an Association
Routing: RELease COMplete Messages Sent by
the switch
A RELease COMplete message terminates an association on an existing CRV. All 
RELease COMplete messages have the Protocol Discriminator and the CRV 
followed by a REL COM type = 0x5a.
End Adjunct Routing
The optional cause, when present, is cause #102 (Recovery on Timer Expiry). 
This is sent when Vector Processing continues for a call without the switch having...
Start reading Lucent Technologies DEFINITY Enterprise Communications Server Release 5, CallVisor, ASAI Protocol Reference Instructions Manual

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

All Lucent Technologies manuals