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
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+.
Tunnel Protocol Procedure Issue 6 June 1997 7-17 Table 7-8. Use of Heartbeat Messages Reconnect Procedure If a client believes it has lost connectivity to the server it may close the TCP connection and establish a new one. If the server receives a Connection Request from a client on a new connection for which it believes there is an existing connection, it closes the existing connection and accepts the new one. When this occurs, the server sends an Error Notification message on the old connection with the cause set to New Connection Made before closing the connection. NOTE: If a client wishes to support two ASAI-Ethernet links, it must have two entries in the brouter table that contains two different link values. In other Client CTI-host, link 3, version 1 DirectionDEFINITY LAN Gateway definity, version 1 ASAI Data (Q.931 Msg.) 8,0,X,X,8,2 ... ASAI Data (Q.931 Msg.) 8,0,X,X,8,2 ... 20 seconds elapse Heartbeat 6,47,0,0 Heartbeat Reply 7,47,0,0 20 seconds elapse Heartbeat 6,48,0,0 10 seconds elapse Error Notification, no HB reply 0,5,0,0 Close (TCP)Close (TCP)
TCP Tunnel Protocol 7-18Issue 6 June 1997 words, a client may open link 3 and link 4 simultaneously, but it may not open link 3 two times simultaneously. Table 7-9. Connecting While a Connection Exists Client CTI-host, link 3, version 1 DirectionDEFINITY LAN Gateway definity, version 1 ASAI Data (Q.931 Msg.) 8,0,X,X,8,2 ... ASAI Data (Q.931 Msg.) 8,0,X,X,8,2 ... Connection Request was received for CTI-host, link3 on a new connection Error Notification, New Connection Made 0,8,0,0 Close (TCP) Close (TCP) Messages are now exchanged on the new TCP connection
Issue 6 June 1997A-1 A The ECS Mapping to Information Elements in Third Party Make Call When an adjunct uses the Third Party Make Call capability to set up a call, the ECS maps the request into a request for one of four internal types of calls: 1. User-Classified call 2. Switch-Classified call 3. Direct-Agent call 4. Supervisor-Assist call The CallVisor ASAI Technical Reference explains the attributes of these types of calls and their uses. Adjunct applications are responsible for requesting call types appropriate for their needs. The Third Party Make Call message layout is a union of all possible IEs that may appear in the request; the rules detailed in this appendix show how the ECS maps the IEs present in a Third Party Make Call capability into a request for a specific call type. Table A-1 and Table A-2 also show how the ECS validates the IEs for each call type. The numbers in the tables correspond to the order in which the ECS software looks for the presence of the information elements and/or validates them. The asterisks in the table indicate information about an IE’s presence or absence. These numbers and asterisks are explained as follows: (1) The presence of the Calling and Called Number IEs are checked for all Third Party Make Call requests. The contents of these IEs may be verified at a later time for some call types. (2a through 2d) The presence of the Supervisor-Assist Call Option, Direct-Agent Call Option, Alert Order Call Options, and Service Circuit IEs determines the
The ECS Mapping to Information Elements in Third Party Make Call A-2Issue 6 June 1997 call type and the validation done on IEs. The order in which the ECS checks (2a) through (2d) is implementation-specific and may change. Adjunct applications should ensure that a legal combination of IEs is present and should not be written in such a way as to use this ordering. (3) Once the call type is determined, these information elements are incompatible with that call type and the ECS will deny a request that contains them. (4) The return acknowledgement option is checked for all call types. (5) through (11) The order in which the ECS validates these IEs within the context of a specific call type. Thus, once a call type is determined, any boxes in the column for that call type, numbered from five upward, are validated in that order for the given call type. * Not only must this IE be present, the ECS uses its presence to determine the call type. If the IE is not present, the ECS interprets the call type to be something different. ** Not only must this IE be absent, the ECS uses its presence to determine the call type. (The ECS uses the presence of this IE to determine if the request is for a type of call other than the one indicated in the column heading.)
Issue 6 June 1997A-3 Table A-1. IEs for User-Classified and Switch-Classified Third Party Make Call Requests Call Type IE User-Classified Switch-Classified (1) Calling Number IE (1) Must be present; denied if not. ...................................... (7) Must be station; denied if not.(1) Must be present; denied if not. ...................................... (11) Must be Split, Hunt, Announce, VDN (only in an EAS environment). Denied if not. (1) Called Number IE (1) Must be present; denied if not. ...................................... Internal — Call Processing will validate. External dest — not validated(1) Must be present; denied if not. ...................................... (10) Internal — denied if not station. External dest — not validated (2a) Supv. Assist Call Option IECannot be present**. Cannot be present**. (2b) Direct-Agent Call Option IECannot be present**. Cannot be present**. (2c) Alert Order Call Options IECannot be present**. (2c) Must be present*. ...................................... (6) Denied if not “dest first.” (2d) Service Circuit Service Circuit IE(2d) Must not be present. Incompatible Option; deny if present.(9) For external dest. Must be present, and must equal classifier. ...................................... Ignored for internal dest. (4) Return ACK Call Option IE(4) Presence is optional. ACK sent when present; ACK not sent when absent.(4) Presence is optional. ACK sent when present; ACK not sent when absent. (Continued on next page)
The ECS Mapping to Information Elements in Third Party Make Call A-4Issue 6 June 1997 Domain IE (6) If present, ECS processes dest. as external. Type must be Trunk, or denied. ...................................... Must omit for internal dest.(8) If present, ECS processes dest. as external. Type must be Trunk, or denied. ...................................... Must omit for internal dest. Number of Rings Call Option IEIgnored (7) Presence is optional. Default = 10 when not present. Deny if out of range (2-15). Priority Call Call Option IE(5) Presence is optional. Priority call when present. Nonpriority call when not present.(5) Presence is optional. Priority call when present. Nonpriority call when not present. Table A-1. IEs for User-Classified and Switch-Classified Third Party Make Call Requests — (Continued) Call Type IE User-Classified Switch-Classified
Issue 6 June 1997A-5 Table A-2. IEs for Direct-Agent and Supervisor-Assist Third Party Make Call Requests Call Type IE Direct-Agent Supervisor-Assist (1) Calling Number IE (1) Must be present; denied if not. ...................................... (6) Must be local station; denied if not.(1) Must be present; denied if not. ...................................... (6) Must be local station; denied if not. (1) Called Number IE (1) Must be present; denied if not. ...................................... (7) Must be local station; denied if not. Incompatible option; deny if present.(1) Must be present; denied if not. ..................................... (7) Must be local station; denied if not. (2a) Supv.-Assist Call Option IEMust not be present**. Incompatible Option; deny if present.(2a) Must be present*. (2b) Direct Agent Call Option IE(2b) Must be present*. (3) Must not be present. Incompatible Option; deny if present. (2c) Alert Order Call Options IE(3) Incompatible Option; deny if present.(3) Must not be present. Incompatible Option; deny if present. (2d) Service Circuit Service Circuit IE(3) Must not be present. Incompatible Option; deny if present.(3) Must not be present. Incompatible Option; deny if present. (4) Return ACK Call Option IE(4) Presence is optional. ACK sent when present; ACK not sent when absent.(4) Presence is optional. ACK sent when present; ACK not sent when absent. Domain IE (5) Must be present, type must be split or skill, and addr must be valid or denied.(5) Must be present, type must be split or skill, and addr must be valid or denied. (Continued on next page)
The ECS Mapping to Information Elements in Third Party Make Call A-6Issue 6 June 1997 Number of Rings Domain IEIgnored if present. Ignored if present. Priority Call Call Option IE(8) Presence is optional. Priority call when present. Non-priority call when not present.(8) Presence is optional. Ignored when present. Supv. Assist always priority call. Table A-2. IEs for Direct-Agent and Supervisor-Assist Third Party Make Call Requests — (Continued) Call Type IE Direct-Agent Supervisor-Assist
Issue 6 June 1997B-1 B Message Scenarios This appendix presents sample scenarios showing the messages exchanged between the ECS and an ASAI adjunct processor (AP). A short description of the scenario and a figure showing the ECS elements (for example, VDNs, ACD splits, or stations) involved in the scenario are also provided with each messaging scenario. Each messaging scenario separates into two columns the ASAI messages exchanged. The first column provides the messages originated or sent by the adjunct processor and the second column provides the messages sent by the ECS. The third column describes the action or event encountered by the scenario. Within each message, the CRV is used to distinguish among active associations maintained by the ECS and the adjunct processor. Figure B-1 details the ASAI message components used in the scenarios presented in this appendix.
Message Scenarios B-2Issue 6 June 1997 Figure B-1. Notation for the Messages in this Appendix The values used for each item within an ASAI message (for example, CRVs, call_ids, party_ids, and extension numbers) are for demonstration purposes only and can change for different applications. However, the item values illustrate how the items are used within a scenario. For example, once a call_id has been assigned a value, the assigned value is used to identify the call until the call terminates or is merged with another call. Q.932 Message TypeCall Reference ValueROSE Component TypeInvoke Identifier Parameters Facility IEOperation Value/ Capability REG [CRV=xx, FIE (Invoke, Inv_id=yy, OV, parameters)]