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

    Download as PDF Print this page Share this page

    Have a look at the manual Lucent Technologies DEFINITY Enterprise Communications Server Release 5, CallVisor, ASAI Protocol Reference Instructions Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.

    Page
    of 600
    							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
    invoke identifier tag 0x02
    invoke identifier length 0x01 0x0 if null invoke-id
    invoke identifier0x?? active invoke-id; omitted 
    if null
    Problem tag 0x?? Problem-specific
    Problem length 0x01
    Problem 0x?? Problem-specific 
    						
    							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 0x91
    component type tag 0xa1 INVOKE component
    component length 0x?? computed length
    component length0x?? long form (length > 127)
    invoke identifier tag 0x02
    invoke identifier length 0x01
    invoke identifier 0x??
    operation value tag 0x02
    operation value length 0x01
    Operation Value = Abort 0xbe
    Q.931 IEs tag 0x40
    Q.931 IEs length 0x?? computed length
    Q.931 IEs length0x?? long form (length > 127)
    The Cause IE0x08 NOTE 1
    Length of IE 0x02
    Ext bit | coding standard | 
    location0x?? cause- and 
    direction-specific
    Ext bit | Class | Value in Class0x?? cause-specific 
    						
    							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
    Locking Shift to Code Set 6 0x96
    Facility IE 0x1c
    Length of Facility 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 identifier length 0x01
    invoke identifier 0x??initiating — odd value
    operation value tag 0x02
    operation value length 0x01
    Operation Value = Route 0xb0
    Q.931 IEs tag 0x40
    Q.931 IEs length 0x?? computed length
    Q.931 IEs length0x?? long form (length > 127)
    Call Identity IE 0x10
    Length of Call Identity 0x02 computed value
    * Call identifier (2 bytes) 0x?? switch-assigned value 
    						
    							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 (#), 0x2a(*)
    User-User IE0x7e User-to-user information
    length of user-user0x?? computed length
    protocol discriminator0x??
    *user information  0x??
    Locking Shift to Code Set 6 0x96
    Originating Line IE0x01
    Length of OLI0x?? computed length
    * II-Digits0x??
    User Code IE0x02 User Entered Data IE
    length of user data0x?? computed length
    type of user data0x85 Call Prompter Data
    collected data indicator0xc0
    * first n-1 user entered digits0x00 | 0x?? ASCII data
    last user entered digit0x80 | 0x?? ASCII data
    The Trunk Identification IE0x0a
    The length of IE0x computed length
    Direction0x80 No Direction
    *Trunk Group Number0x?? binary coded
    *Trunk Group Member Number0x?? binary coded
    The Feature IE 0x48
    The length of the feature IE 0x01
    Feature 0x86
    Flexible billing
    (Continued on next page) 
    						
    							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 Vector Directory Number
    *The 1st to N-1 ASCII digits 0x?? 0x30 through 0x39
    Ext bit | last ASCII digit 0x?? 0xb0 through 0xb9
    Lookahead Interflow IE0x7b PRI Interflow
    length of lookahead interflow0x?? computed length
    Ext bit | Priority Level & Type0x?? 0x80 | data from PRI
    Ext bit | Time Stamp - hours0x?? 0x80 | data from PRI
    Ext bit | Time Stamp - minutes0x?? 0x80 | data from PRI
    Ext bit | Time Stamp - seconds0x?? 0x80 | data from PRI
    *Ext bit | first n-1 ASCII chars0x?? 0x80 | ASCII data from PRI
    Ext bit | last ASCII char0x?? 0x80 | ASCII data from PRI switch Requests Call Route from Adjunct — (continued) 
    						
    							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 identifier length 0x01
    invoke identifier 0x?? even value
    operation value tag 0x02
    operation value length 0x01
    Operation Value = Route Select 0xb7
    Q.931 IEs tag 0x40
    Q.931 IEs length 0x?? computed length
    Q.931 IEs length0x?? long form (length > 127)
    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 (#), 
    0x2a (*)
    (Continued on next page) 
    						
    							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
    *first (n-1) digits 0x?? ASCII 
    0x30-0x39,0x23(#),0x2a(*)
    *last (nth) digit 0x?? ASCII 
    0xb0-0xb9,0xa3(#),0xaa(*)
    User Entered Code IE (Note 2) 0x02 ASAI-requested digit 
    collection
    length of user data 0x?? computed length
    type of user data 0xa0 Tone Detector
    collect data indicator bx100XXXXX Timeout 00000 - 11111
    Number of digits 0x?? 0x81 -0x98
    The Party Identifier IE (Note 3) 0x44 Party on the call the Tone 
    Detector should listen to
    The length of the IE 0x01 or 0x02
    Ext bit | Party ID 0x??
    Ext bit | Party ID (second octet) 0x??
    The Specific Event IE (Note 4) 0x47
    The length of the Specific Event IE 0x01
    Event value = Connect or Drop 0x??
    0x8b(Conn), 0x84(Drop)
    The Domain IE  0x49 present for direct agent call
    The length of the Domain IE 0x?
    The Domain type = ACD Split0x81 ACD split
    * The 1st to N-1 ASCII digits0x?? 0x30 through 0x39
    Ext bit | last ASCII digit0x?? 0xb0 through 0xb9
    The Domain IE 0x49
    The length of the Domain IE 0x?
    (Continued on next page) 
    						
    							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 Adjunct
    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. Byte Description Byte Value Comments
    The Domain type = Trunk Access 
    Code0x89 Trunk Access Code/ARS
    * The 1st to N-1 ASCII digits0x?? 0x30 through 0x39
    Ext bit | last ASCII digit0x?? 0xb0 through 0xb9
    Call Options IE0x4b
    Length of Call Option IE0x01
    Option = direct agent call0x86
    Call Options IE0x4b
    Length of Call Option IE0x01
    Option = priority call0x83 Adjunct Call Routing Selection —(continued) 
    						
    							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 identifier length 0x01
    invoke identifier 0x?? value from request
    error value tag 0x02
    error value length 0x01
    Operation Value 0x?? Operation Value of the 
    denied request
    Q.931 IEs tag 0x40
    Q.931 IEs length 0x?? computed length
    Q.931 IEs length0x?? long form (length > 127)
    Cause IE 0x08
    length of Cause IE 0x02 computed length
    Ext bit | coding standard | location 0x8N or 0xeN N = 0 or 1, 
    direction-dependent
    Cause Value 0x?? cause-dependent 
    						
    							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 
    received a route. 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 0xa1 INVOKE component
    component length 0x?? computed length
    component length0x?? long form (length > 127)
    invoke identifier tag 0x02
    invoke identifier length 0x01
    invoke identifier 0x??initiator — odd value
    operation value tag 0x02
    operation value length 0x01
    Operation Value = Route End 0xb9
    Q.931 IEs tag 0x40
    Q.931 IEs length 0x?? computed length
    Q.931 IEs length0x?? long form (length > 127)
    Cause IE 0x08
    length of Cause IE 0x02 computed length
    Ext bit | coding standard | location 0x81 or 0xe1  switch-to-adjunct
    Cause Value 0x?? cause-dependent 
    						
    All Lucent Technologies manuals Comments (0)

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