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 411
1. Initialization Issue 6 June 1997 B-3 1. Initialization This section presents a sample ASAI initialization procedure. The adjunct processor initializes the link and requests Event Notification for VDN 5678 and ACD split 3456. This sample initialization procedure is referred to by some of the scenarios presented in subsequent sections. Messages Sent by the Adjunct ProcessorMessages Sent by the ECS Comments REST (CRV=global, Restart Indicator=all interfaces)Restart ASAI Interface REST ACK...
Page 412
Message Scenarios B-4Issue 6 June 1997 2. Notification Associations This section illustrates the Event Reports provided by calls entering different notification domains. Figure B-2 shows the Vector Directory Numbers (VDNs), vectors, ACD splits, and agent extensions used for the message scenarios presented in this section. VDNs 5678, 5690, and 7656 point to vectors A, B, and C, respectively. Only the most relevant vector commands (that is, Adjunct Routing and Queue to Main) are shown. ACD splits...
Page 413
2. Notification Associations Issue 6 June 1997 B-5 External Call to VDN Routed to ACD Split This scenario shows the call flow for an incoming ISDN PRI call to VDN 5678 that is routed via the Adjunct Routing vector command to ACD Split 3456 (Figure B-3). The agent at extension 4534 answers the call. Event Notification for VDN 5678 and ACD Split 3456 is active as presented in the initialization scenario. The ASAI messages generated by the Adjunct Routing vector command are shown also. Figure B-3. Call...
Page 414
Message Scenarios B-6Issue 6 June 1997 Messages Sent by the Adjunct ProcessorMessages Sent by the ECS Comments FAC [CRV=98, FIE(Invoke, Inv_id=2, Event Report, call_id=37, event=call offered, calling number=2015666379, called number=9085765678, domain=VDN 5678)]Call Offered to VDN 5678 REG [CRV=93, FIE(Invoke, Inv_id=4, Route, call_id=37, calling number=2015666379, called number=9085765678, user code=11569037, domain=VDN 5678)]Route Request FAC [CRV=93, FIE(Invoke, Inv_id=7, Route Select, called...
Page 415
2. Notification Associations Issue 6 June 1997 B-7 FAC [CRV=102, FIE(Invoke, Inv_id=14, Event Report, call_id=37, party_id=2, event=alerting, calling number=2015666379, called number=9085765678, connected number=4534, domain=ACD Split 3456)]Alerting Event Report (Call Delivered to Agent 4534) FAC [CRV=102, FIE(Invoke, Inv_id=16, Event Report, call_id=37, party_id=2, event=connected, calling number=2015666379, called number=9085765678, connected number=4534)]Connected Event Report (Call Connected to...
Page 416
Message Scenarios B-8Issue 6 June 1997 External Call to Monitored VDN Routed to Non-Monitored VDN This scenario shows the call flow for an incoming ISDN PRI call to VDN 5678 that is routed via the Adjunct Routing vector command to VDN 5690 (Figure B-4). The call queues to two ACD splits, ACD split 3459 and 3460. The agent at extension 4566 and logged into ACD split 3460 answers the call. Event Notification for VDN 5678 is active as presented in the initialization scenario. The ASAI messages...
Page 417
2. Notification Associations Issue 6 June 1997 B-9 Messages Sent by the Adjunct ProcessorMessages Sent by the ECS Comments FAC [CRV=98,FIE(Invoke, Inv_id=2, Event Report, call_id=58 event=call offered, calling number=2015663569, called number=9085765678 domain=VDN 5678)]Call Offered to VDN Event Report REG [CRV=93, FIE(Invoke, Inv_id=4, Route, call_id=58, calling number=2015663569, called number=9085765678, user code=34569058, domain=VDN 5678)]Route Request FAC [CRV=93, FIE(Invoke, Inv_id=3, Route...
Page 418
Message Scenarios B-10Issue 6 June 1997 Messages Sent by the Adjunct ProcessorMessages Sent by the ECS Comments FAC [CRV=98, FIE(Invoke, Inv_id=12, Event Report, call_id=58, party_id=2, event=alerting, calling number=2015663569, called number=9085765678, connected number=4566, domain= ACD Split 3460)]Alerting Event Report (Call Delivered to Agent 4566) FAC [CRV=98, FIE(Invoke, Inv_id=14, Event Report, call_id=58, party_id=2, event=connected, calling number=2015663569, called number=9085765678,...
Page 419
2. Notification Associations Issue 6 June 1997 B-11 External Call to VDN Routed to Monitored VDN This scenario shows the call flow for an incoming ISDN PRI call to VDN 5678 that is routed via the Adjunct Routing vector command to VDN 7656 (Figure B-5). VDN 7656 is monitored by a different adjunct not shown in these scenarios. Event Notification from VDN 5678 is active as presented in the initialization scenario. The ASAI messages generated by the Adjunct Routing vector command are shown also. Figure...
Page 420
Message Scenarios B-12Issue 6 June 1997 Messages Sent by the Adjunct ProcessorMessages Sent by the ECS Comments FAC [CRV=98, FIE(Invoke, Inv_id=2, Event Report, call_id=39, event=call offered, calling number=6157856399, called number=9089575678, domain=VDN 5678)]Call Offered to VDN 5678 REG [CRV=93, FIE(Invoke, Inv_id=2, Route, call_id=39, calling number=2015766399, called number=2015765678, user code=00569039, domain=VDN 5678)]Route Request FAC [CRV=93, FIE(Invoke, Inv_id=3, Route Select, called...