Call Scenarios and Applications

4.Converse Vector Command Interactions

External Call to a VDN that has a Converse Step that is Interrupted

This scenario presents the call flow for an incoming ISDN PRI call for VDN 7000 that has a Converse vector command that can be interrupted (see Figure A-10). The call comes into the VDN and gets queued to two splits, Split 6500 and Split 3400. The converse vector command then sends the call to the VRU (Split 1234) while maintaining the call’s position in the other queues. When an agent in Split 6500 becomes available, the call leaves the VRU and is delivered to the agent. This “transfer” happens regardless of whether or not the caller has completed the VRU interaction.

Note that the Alerting Event Report sent when the call alerts the VRU port contains a cause value — CS3/23 (call remains in queue). This cause value informs the application that this is a converse split and that the call will not lose its place in any other splits that it has been queued to.

VDN 7000 has Event Notification active and each port on the VRU has Domain Control active.

 

 

DEFINITY ECS

Agent

 

 

 

Extension

Incoming Call

VDN 7000

Vector Q

 

call_id=50

 

 

 

 

 

 

1. Queue to Main

ACD

 

 

Split 6500

 

 

2. Queue to Main

Split

 

 

Split 3400

6500

 

 

3. Converse on

x6534

 

 

Split 1234

 

 

ACD

 

ACD

VRU

Split

 

Split

Port

1234

 

3400

5431

 

 

 

Figure A-10. Call Flow for a Converse Step that can be Interrupted

Issue 7 March 1998 A-47

Page 427
Image 427
Lucent Technologies 555-230-220 manual Converse Vector Command Interactions