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 471

8. Call Redirection
Issue 6 June 1997
B-63
REG [CRV=79, FIE(Invoke,
Inv_id=1, Request Feature,
feature=Cancel Call
Forwarding,
redirecting number=3569)]AP Cancels Call
Forwarding for
Station 3569
REL COMP[CRV=79, FIE(Return
Result, Inv_id=1)]Call Forwarding
Cancelled
Messages Sent by the 
Adjunct ProcessorMessages Sent
by the Switch Comments 

Page 472

Message Scenarios
B-64Issue 6 June 1997 
Incoming Call to Station Forwards to VDN
This scenario shows the call flow for a call from station 3001 to station 2345 that 
has call forwarding active to VDN 405 (see Figure B-25). VDN 405 routes the call, 
via the Adjunct Routing vector command, to VDN 5678. VDN 5678 routes the call, 
via the Adjunct Routing vector command, to extension 9800. 
VDN 405 is not monitored by the adjunct. VDN 5678 has Event Notification active 
as presented in the initialization...

Page 473

8. Call Redirection
Issue 6 June 1997
B-65
Messages Sent by the 
Adjunct ProcessorMessages Sent
by the Switch Comments
REG [CRV=32, FIE(Invoke,
Inv_id=4, Route,
call_id=67,
calling number=3001, 
called number=2345,
domain=VDN 405)]Route Request
FAC [CRV=32, FIE(Invoke,
Inv_id=3, Route Select,
called number=5678)]Route to VDN
5678
REL COMP [CRV=32, FIE(Invoke,
Inv_id=6, Route End,
cause=normal)]Call Routed
FAC [CRV=98, FIE(Invoke,
Inv_id=24, Event Report,
call_id=67,
event=call offered,
calling...

Page 474

Message Scenarios
B-66Issue 6 June 1997 
 
Messages Sent by the 
Adjunct ProcessorMessages Sent
by the Switch Comments
FAC [CRV=90, FIE(Invoke,
Inv_id=3, Route Select,
called number=9800)]Route to Station
9800
REL COMP [CRV=90, FIE(Invoke,
Inv_id=4, Route End,
cause=normal)]Call Routed
FAC [CRV=98, FIE(Invoke,
Inv_id=26, Event Report,
call_id=67, party_id=2,
event=alerting,
calling number=3001, 
called number=2345,
connected number=9800)]Alerting Event Report
(Call Alerts Station
9800)
FAC [CRV=98,...

Page 475

8. Call Redirection
Issue 6 June 1997
B-67
Incoming Call to ACD Split Forwards to Hunt 
Group
This scenario shows the call flow for an incoming ISDN PRI call to ACD split 3456 
(see Figure B-26). ACD split 3456 has call forwarding active to hunt group 2000. 
Member 2005 of the hunt group 2000 receives the call.
ACD split 3456 has Event Notification active as presented in the initialization 
scenario. The adjunct processor does not have Event Notification active for Hunt 
Group 2000. 
Figure B-26. Call...

Page 476

Message Scenarios
B-68Issue 6 June 1997 
Messages Sent by the 
Adjunct ProcessorMessages Sent
by the Switch Comments
FAC [CRV=102, FIE(Invoke,
Inv_id=24, Event Report,
call_id=34,
event=call offered,
calling number=4159703478,
called number=8095763456,
domain=ACD Split 3456)]Call Offered to
ACD Split 3456
FAC [CRV=102, FIE(Invoke,
Inv_id=26, Event Report,
call_id=34, event=queued,
called number=8095763456,
calls in queue=1,
domain=Hunt Group 2000)]Call Queues to
to Hunt Group 2000
FAC [CRV=102,...

Page 477

8. Call Redirection
Issue 6 June 1997
B-69
Call to Station Goes to Coverage Station
This scenario shows the call flow for a call from station 6071 to station 3580 (see 
Figure B-27). After three rings, the call alerts the coverage station (extension 
3569). The principal station (3580) answers the call (using its simulated bridged 
appearance) after it has alerted the coverage station.
Assume that Third Party Domain (Station) Control is active for station 3569 as 
shown in the Send All Calls scenario...

Page 478

Message Scenarios
B-70Issue 6 June 1997 
Messages Sent by the 
Adjunct ProcessorMessages Sent
by the Switch Comments
REG [CRV=87, FIE(Invoke,
Inv_id=1, 3P Make Call,
called number=3580,
calling number=6071)]AP Requests Make Call
from Station 6071 to
Station 3580
FAC [CRV=87, FIE(Invoke,
Inv_id=2, Event Report,
call_id=16, party_id=2,
event=alerting,
calling number=6071,
called number=3580,
connected number=3580)]Alerting Event Report
(Call Delivered to
Station 3580) —
3P Make Call
Association
FAC...

Page 479

8. Call Redirection
Issue 6 June 1997
B-71
Messages Sent by the 
Adjunct ProcessorMessages Sent
by the Switch Comments
FAC [CRV=88, FIE(Invoke,
Inv_id=4, Event Report,
call_id=16,
event=call redirected)]Call Redirected Event
Report (Principal 3580
Picked Up the Call) —
x3569 Association
FAC [CRV=87, FIE(Invoke,
Inv_id=3, 3P Selective Drop,
party_id=2)]AP Requests to
Drop Station 3580
from Call
FAC [CRV=87, FIE(Return
Result, Inv_id=3)]
REL COMP [CRV=87, FIE(Invoke,
Inv_id=10, Call Ended,
call_id=16,...

Page 480

Message Scenarios
B-72Issue 6 June 1997 
Incoming Call to Station Sent to Coverage with
Send All Calls (SAC)
This scenario shows the call flow for a call from station 3568 to station 3569 (see 
Figure B-28). After alerting at station 3569, the user at station 3569 activates 
Send All Calls (SAC) and redirects the call to coverage (station 6056). Station 
3569 maintains a simulated bridged appearance for the call, but does not connect 
to the call.
Stations 3568 and 3569 have Domain (Station) Control...
Start reading Lucent Technologies DEFINITY Enterprise Communications Server Release 5, CallVisor, ASAI Protocol Reference Instructions Manual

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

All Lucent Technologies manuals