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

Add to Favourites
    Download as PDF Print this page Share this page

    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+.

    View all the pages
    Page
    of 600
    Add page 471 to Favourites
    image text
    Enable zoom 
    							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
    Add page 472 to Favourites
    image text
    Enable zoom 
    							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 scenario.
Figure B-25. Call Flow for Incoming Call to Station Forwarded to VDN
DEFINITY ECS
x9800
x3001x2345call_id=67
VDN 405
VDN 5678Vector E
1. Adjunct Routing
2. Wait 4 Seconds
3. Busy
4.
Vector A
1. Collect Digits
2. Adjunct Routing
3. Wait 4 Seconds
4. Route to 0
    Add page 473 to Favourites
    image text
    Enable zoom 
    							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 number=3001,
called number=2345,
domain=VDN 5678)]Call Offered to
VDN 5678
REG [CRV=90, FIE(Invoke,
Inv_id=2, Route,
call_id=67,
calling number=3001, 
called number=2345,
domain=VDN 5678,
user code=1233)]Route Request
(Continued on next page)
    Add page 474 to Favourites
    image text
    Enable zoom 
    							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, FIE(Invoke,
Inv_id=28, Event Report,
call_id=67, party_id=2,
event=connected,
calling number=3001, 
called number=2345,
connected number=9800)]Connected Event Report
(Station 9800 Answers)
FAC [CRV=98, FIE(Invoke,
Inv_id=9, Stop Call
Notification, call_id=67)]Stop Event Reports
for Call over 
Notification Association
FAC [CRV=98, FIE(Return
Result, Inv_id=9)]Event Reporting
for Call Terminated
    Add page 475 to Favourites
    image text
    Enable zoom 
    							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 Flow for Incoming Call to ACD Split Forwarded to Another ACD Split
DEFINITY ECS
ACD Split
Hunt Group Incoming Call
call_id=34
x6005Agent
Extension
Call Forwarding
Active 3456
2000
    Add page 476 to Favourites
    image text
    Enable zoom 
    							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, FIE(Invoke,
Inv_id=28, Event Report,
call_id=34, party_id=2,
event=alerting,
calling number=4159703478,
called number=8095763456,
connected number=2005,
domain= Hunt Group 2000)]Alerting Event Report
(Call Alerts Station
2005)
FAC [CRV=102, FIE(Invoke,
Inv_id=28, Event Report,
call_id=34, party_id=2,
event=connected,
calling number=4159703478,
called number=8095763456,
connected number=2005)]Connected Event Report
(Station 2005 Answers)
FAC [CRV=102, FIE(Invoke,
Inv_id+5, Stop Call Notification,
call_id=34)]  AP Requests to
Stop Receiving
Event Reports for the Call
FAC [CRV=102, FIE(Return
Result, Inv_id=5)]Event Reporting for
Call Terminated
    Add page 477 to Favourites
    image text
    Enable zoom 
    							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 above.
Figure B-27. Call Flow for Incoming Call to Station Redirected to Coverage
DEFINITY ECS
x3569
x6071call_id=16x3580
Coverage
    Add page 478 to Favourites
    image text
    Enable zoom 
    							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 [CRV=87, FIE(Invoke,
Inv_id=4, Event Report,
call_id=16, party_id=3,
event=alerting,
calling number=6071,
called number=3580,
connected number=3569
cause=3/28)]
FAC [CRV=88, FIE(Invoke,
Inv_id=2, Event Report,
call_id=16, party_id=3,
event-alerting,
calling number=6071,
called number=3580,
connected number=3569
cause=3/28)]
FAC [CRV-87, FIE(Invoke,
Inv_id=6, Event Report,
call_id=16, party_id=2,
calling number=6071,
event=connected,
called number=3580,
connected number=3580)]
FAC [CRV=87, FIE(Invoke,
Inv_id=8, Event Report,
call_id=16, party_id=3,
event=drop,
connected number=3569,
cause=normal clearing)]Alerting Event Report
(Call Goes to Coverage,
Station 3569) —
3P Make Call
Association
Alerting Event Report
(Call Goes to Coverage,
Station 3569) —
x3569 Association
Connected Event Report
(Station 3580 Answers
Call)
Drop Event Report
(Coverage 3569 Dropped)—
3P Make Call
Association
(Continued on next page)
    Add page 479 to Favourites
    image text
    Enable zoom 
    							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, cause = normal)]Station 3580
Dropped
Call Terminated
    Add page 480 to Favourites
    image text
    Enable zoom 
    							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 active.
Figure B-28. Incoming Call to Station Sent to Coverage via Send All Calls (SAC)
DEFINITY ECS
x6056
x3568call_id=18x3569
Coverage Send All Calls
Activated
    All Lucent Technologies manuals Comments (0)

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