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
    							Call Control Capability Group
    Issue 6  June 1997
    5-57
    Acknowledgment of Third Party 
    Take Control Request
    (Continued on next page) 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 0xa2 RETURN RESULT component
    component length 0x?? computed length
    component length0x?? long form (length > 127)
    invoke identifier tag 0x02
    invoke identifier length 0x01
    invoke identifier 0x?? value from request
    Sequence Tag 0x30 Q.932 sequence tag
    Sequence Length 0x?? computed length
    Sequence Length0x?? long form (length > 127)
    operation value tag 0x02
    operation value length 0x01
    Operation Value = Third Party 
    Take Control0xb6
    Q.931 IEs tag 0x40
    Q.931 IEs length 0x?? computed length
    Q.931 IEs length0x?? long form (length > 127)
    * The Connected Number IE 0x0c
    * Length of IE  0x?
    * Ext bit | Type | Numbering plan 0x80
    * * Address digits 0x??,  0x30 thru 0x39, 0x23 (#), 0x2a (*)
    Locking Shift to Code Set 6 0x96
    * The Party Identifier IE 0x44 Up to six party IDs 
    						
    							Byte Level Messages
    5-58Issue 6  June 1997 
    NOTES:
    There must be the same number of Party ID IEs as there are Connected Number IEs.
    The Nth Party ID IE corresponds to the Nth Connected Number IE (and thereby 
    associates an extension with that party).
    To preserve a 1:1 correspondence, if the type/address for a party is unknown, a 
    Connected Number IE is present for that party, but the length byte is coded as zero 
    (and no bytes follow).Acknowledgment of Third Party Take Control Request — (continued)
    Byte Description Byte Value Comments
    Length of the IE  0x01 or 0x02
    Ext bit | Party ID 0x??
    Ext bit | Party ID (second byte)0x?? 
    						
    							Call Control Capability Group
    Issue 6  June 1997
    5-59
    Acknowledgment of Third Party Merge Request 
    (Continued on next page) 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 0xa2 RETURN RESULT component
    component length 0x?? computed length
    component length0x?? long form (length > 127)
    invoke identifier tag 0x02
    invoke identifier length 0x01
    invoke identifier 0x?? value from request
    Sequence Tag 0x30 Q.932 sequence tag
    Sequence Length 0x?? computed length
    Sequence Length0x?? long form (length > 127)
    operation value tag 0x02
    operation value length 0x01
    Operation Value = 3rd Party Merge 0x89
    Q.931 IEs tag 0x40
    Q.931 IEs length 0x?? computed length
    Q.931 IEs length0x?? long form (length > 127)
    * The Connected Number IE 0x0c
    * Length of IE  0x?
    * Ext bit | Type | Numbering plan 0x80
    * * Address digits 0x??,  0x30 thru 0x39, 0x23 (#), 0x2a (*)
    Call Identity IE 0x10 New Call Identifier for merged call
    Length of Call Identity 0x02 computed value
    * Call identifier (2 bytes) 0x?? switch-assigned value
    Locking Shift to Code Set 6 0x96 
    						
    							Byte Level Messages
    5-60Issue 6  June 1997 
    NOTES:
    There must be the same number of Party ID IEs, Old Party ID IEs, and Connected 
    Number IEs.
    The Nth Party ID IE and the Nth Old Party ID IE correspond to the Nth Connected 
    Number IE (and thereby associate an extension with that party).
    To preserve a 1:1 correspondence, if the type/address for a party is unknown, a 
    Connected Number IE is present for that party, but the length byte is coded as zero 
    (and no bytes follow).Acknowledgment of Third Party Merge Request — (continued)
    Byte Description Byte Value Comments
    * Old Party Identifier IE 0x17 Up to six old party IDs
    * Length of the IE 0x02 or 0x03
    * From Call 0x?? 0x80 or 0xc0
    * Ext bit | Party ID 0x??
    * Ext bit | Party ID (second byte)0x??
    * The Party Identifier IE 0x44
    * Length of the IE  0x02 or 0x03
    * Ext bit | Party ID 0x??
    * Ext bit | Party ID (second byte)0x?? 
    						
    							Call Control Capability Group
    Issue 6  June 1997
    5-61
    Call Control: Acknowledgment (No Parameters) 
    Association Continues 
    The switch uses the following message to acknowledge the following requests:
    nThird Party Selective Drop Request
    nThird Party Selective Hold Request
    nThird Party Reconnect Request
    nThird Party Listen Disconnect Request 
    nThird Party Listen Reconnect Request
    nSend DTMF Request
    nRedirect Call
    .
    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 0xa2 RETURN RESULT component
    component length 0x?? computed length
    component length0x?? long form (length > 127)
    invoke identifier tag 0x02
    invoke identifier length 0x01
    invoke identifier 0x?? value from request 
    						
    							Byte Level Messages
    5-62Issue 6  June 1997 
    Call Control: Request is Denied — Association
    Continues
    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 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 | 
    location0x81 or 0xe1 switch-to-adjunct
    Cause Value 0x?? cause-dependent 
    						
    							Call Control Capability Group
    Issue 6  June 1997
    5-63
    Call Control: 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.
    See “RELease COMplete Messages Sent by the switch and the Adjunct.”
    Call Control: 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.
    Call Control: Acknowledgment — Association
    Terminates
    The switch uses the following message to acknowledge the following requests:
    nThird Party Relinquish Control Request
    nThird Party Clear Call Request
    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 0xa2 RETURN RESULT component
    component length 0x?? computed length
    component length0x?? long form (length > 127)
    invoke identifier tag 0x02
    invoke identifier length 0x01
    invoke identifier 0x?? value from request 
    						
    							Byte Level Messages
    5-64Issue 6  June 1997 
    Call Control: 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 | 
    location0x81 or 0xe1
    Cause Value 0x?? cause-dependent 
    						
    							Call Control Capability Group
    Issue 6  June 1997
    5-65
    Call Control: Internal switch Audit 
    Finds Stale Call Control CRV
    NOTE:
    “Stale” in this context means that while conducting an internal switch audit, 
    the switch has discovered a call control association with no corresponding 
    call and terminates the 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 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 = Abort 0xbe
    Q.931 IEs tag 0x40
    Q.931 IEs length 0x?? computed length
    Q.931 IEs length0x?? long form (length > 127)
    The Cause IE 0x08
    Length of IE 0x02
    Ext bit | coding standard | location 0xe1 switch Audit Cause
    Ext bit | Class | Value in Class 0xd7 switch Audit Cause 
    						
    							Byte Level Messages
    5-66Issue 6  June 1997 
    Third Party Call Ended —
    Association Terminates
    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?? even value
    operation value tag 0x02
    operation value length 0x01
    Operation Value = 3P Call Ended 0xbb
    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
    Call Identity IE 0x10
    Length of Call Identity 0x02 computed value
    * Call identifier (2 bytes) 0x?? switch-assigned value 
    						
    All Lucent Technologies manuals Comments (0)

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