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 551
15. User to User Information (UUI) Issue 6 June 1997 B-143 Call Ended call_id=5678 cause=normal Call Ended call_id=9000 cause=normal Call Sequence 2: Incoming Call to Switch ACall Offered call_id=1235 called number=1235678914 domain=VDN1 calling number=CPN/BN Digits Collected by Call Prompting Switch Request Route for CallRoute Request call_id=1235 called number=1235678914 calling number=CPN/BN domain=VDN0 collected digits=001 Host Provides Route Route Select called number=VDN2 UUI=info2 Call Routed...
Page 552
Message Scenarios B-144Issue 6 June 1997 Call Delivered to Agent Alerting call_id=1235 called number=1235678914 calling number=CPN/BN connected number=agentA domain=ACD SplitA party_id=2 UUI=info2 Call Connected to Agent Connected call_id=1235 called number=1235678914 calling number=CPN/BN connected number=agentA party_id=2 Agent Drops Drop call_id=1235 connected number=agentA party_id=2 Call Terminates Call Ended call_id=1235 cause=normal (Continued on next page) Action/OperationHost A — Event...
Page 553
15. User to User Information (UUI) Issue 6 June 1997 B-145 Action/OperationHost A — Event Notification VDN 1Host B — Event Notification VDN 4 Call Sequence 3: Incoming Call to Switch ACall Offered call_id=1236 called number=1235678914 domain=VDN1 calling number=CPN/BN UUI=info0 Switch Request Route for CallRoute Request call_id=1236 called number=1235678914 calling number=CPN/BN domain=VDN0 UUI=info0 Host Provides Route Route Select called number=VDN3 UUI=info3 Call Routed Route End cause=normal Call...
Page 554
Message Scenarios B-146Issue 6 June 1997 VRU is disconnected 3rd Party Drop call_id=9002 party_id=1 UUI=info4 Call Disconnected (Switch B) Drop call_id=1236 connected number=##### party_id=2 UUI=info43rd Drop-ACK Call Ended call_id=9002 cause=normal Call Delivered to Return VDN 11Call Offered call_id=1236 called number=1235678914 domain=VDN11 calling number=CPN/BN UUI=info4 Host Drops Call 3rd Party Drop call_id=1236 party_id=1 UUI=info5 Caller Disconnected 3rd Party Drop-ACK Drop call_id=1236...
Page 555
16. User Scenarios — Connected IE for non-ISDN Trunks Issue 6 June 1997 B-147 16. User Scenarios — Connected IE for non-ISDN Trunks Table B-1 shows the Event Reports provided for a monitored call that is routed over an outgoing non-ISDN trunk. The incoming call also uses a non-ISDN trunk and is directed to a VDN/vector that routes the call to an external number. . Table B-1. Incoming Call Routed to External Destination Example Operation Event Report Incoming Call Call Offered call_id=45 trunk...
Page 556
Message Scenarios B-148Issue 6 June 1997 17. User Scenarios — ASAI-Provided Dial-Ahead Digits This is a simple scenario in which the host provides dial-ahead digits via a Route Select. After the dial-ahead digits are stored by the switch, the digits are collected using call prompting vector commands. The scenario also shows the ASAI Event Reports sent to a monitoring host. Messages Sent by the HostMessages Sent by the Switch Comments Call Offered ER call_id=45, calling number=3156778888, called...
Page 557
17. User Scenarios — ASAI-Provided Dial-Ahead Digits Issue 6 June 1997 B-149 Route Request call_id=45, calling number=3156778888, called number=5678, domain=VDN 61123, user code=(call prompt, collected, digits=23)Switch Requests Another Route Vector Executed (VDN 61123): 1. Collect 2 Digits 2. Adjunct Route 3. Wait 4 secs Route Select call_id=45, called number=69990, user code=(cdp, collected,digits=6789)Host Routes to VDN 69990 Route End cause= normalCall Routed VDN 69990 Executed: 1. Collect 4...
Page 558
Message Scenarios B-150Issue 6 June 1997 18. User Scenarios — ASAI-Requested Digit Collection This is a sample scenario for an incoming ISDN call routed via Adjunct Routing to an external destination. The user has subscribed to receive 4-digit DNIS numbers. As part of the route, the host requests collecting 3 digits from the caller. Messages Sent by the HostMessages Sent by the Switch Comments Call Offered ER call_id=45, calling number=3156778888, called number=5678, domain=VDN 65678Incoming ISDN...
Page 559
18. User Scenarios — ASAI-Requested Digit Collection Issue 6 June 1997 B-151 Messages Sent by the HostMessages Sent by the Switch Comments Entered Digits ER call_id=45, user code=(tone detect, collected, no timer, digits=4*#)Digits Entered Connect ER call_id=45, party_id=2 calling number=3156778888, called number=5678, connected number=#####, cause=network connectCall Answered by Destination Drop ER call_id=45, party_id=1 cause=normal connected number=#####Calling Party Drops Call Ended call_id=45...
Page 560
Message Scenarios B-152Issue 6 June 1997 19. User Scenarios —VDN Return Destination A customer may use the VDN Return Destination feature to provide a more flexible remote access feature together with host-based call security. The remote user/caller does not have to call back into the switch when multiple destinations need to be reached, nor does the caller have to enter his/her identification every time a new destination is desired. For example, a customer can program the following vector that is...