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 461
7. Domain (Station) Control Associations Issue 6 June 1997 B-53 Messages Sent by the Adjunct ProcessorMessages Sent by the Switch Comments FAC [CRV=100, FIE(Invoke, Inv_id=6, Event Report, call_id=65, party_id=1 event=hold, connected number=4568)]Hold Event Report (Station 4568 Places Call on Hold) — x4568 Association FAC [CRV=100, FIE(Invoke, Inv_id=8, Event Report, call_id=12, party_id=2, event=connected, calling number=4569, called number=4568, connected number=4568)]Connected Event Report (4568...
Page 462
Message Scenarios B-54Issue 6 June 1997 Domain (Station) Control — Third Party Merge This scenario shows the call flow for a Third Party Merge capability. Station 4567, after disconnecting from the active call (call_id=45), reconnects to the held call and transfers the call (call_id=78) to station 4569 (see Figure B-21). This scenario is a continuation of the scenario shown in Figure B-19. Figure B-21. Call Flow for Third_Party_Merge over a Domain Control DEFINITY ECS Connected —> Dropped External...
Page 463
7. Domain (Station) Control Associations Issue 6 June 1997 B-55 Messages Sent by the Adjunct ProcessorMessages Sent by the Switch Comments FAC [CRV=101, FIE(Invoke, Inv_id=7, 3P Merge, call_id=34, call_id=78, conf/transf flag=transfer)]AP Requests Transfer of Held Call to Station 4569 FAC [CRV=101, FIE(Return Result, Inv_id=7, 3P Merge, call_id=34, party_id=1, party_id=2, party_id=3, old_party_id=other call 1 old_party_id=other call 2 old_party_id=reslt call 3 connected number=4590, connected...
Page 464
Message Scenarios B-56Issue 6 June 1997 Value Queries for Calls at Domain Control Stations This scenario shows the Call, Party_id, and Station Status Value_Queries for stations 4567, 4568, and 4569 (see Figure B-22). This scenario is a continuation of the previous scenario. Figure B-22. Calls Present at Domain Controlled Stations 4567, 4568, and 4569 DEFINITY ECS Stations x4568 External Endpoint x4569 x4590 External EndpointHeld call_id=65 Connected call_id=12 Connected call_id=34 x4567 External...
Page 465
7. Domain (Station) Control Associations Issue 6 June 1997 B-57 Messages Sent by the Adjunct ProcessorMessages Sent by the Switch Comments FAC [CRV=87, FIE(Invoke, Inv_id=1, Value Query, item=Calls Query, domain=extension 4567)]AP Requests the Status of Calls at Station 4567 REL COMP [CRV=87, FIE Return Result, Inv_id=1)]No Calls Present at Station 4567 REG [CRV=86, FIE(Invoke, Inv_id=1, Value Query, item=Calls Query, domain= extension 4568)]AP Requests the Status of Calls at Station 4568 REL COMP...
Page 466
Message Scenarios B-58Issue 6 June 1997 Messages Sent by the Adjunct ProcessorMessages Sent by the Switch Comments REG [CRV=54, FIE(Invoke, Inv_id=1, Value Query, item=Calls Query, domain= extension 4569)]AP Requests the Status of Calls at Station 4569 REL COMP [CRV=54, FIE (Return Result, Inv_id=1, Value Query, call_id=34, party_id=3, call_state=connected)]One Call Present at Station 4569 REG [CRV=55, FIE(Invoke, Inv_id=1, Value Query, item=Party_id, call_id=34)]AP Requests the Parties Connected to...
Page 467
7. Domain (Station) Control Associations Issue 6 June 1997 B-59 Domain Control — Call Disconnects This scenario shows several call drops and/or disconnects for Domain Control stations (see Figure B-23). The call at station 4569 is dropped via a Third_Party_Selective_Drop request issued by the Domain Control association for station 4569. The held call at station 4568 is dropped by the held endpoint. The active call at station 4568 is dropped via a Third_Party_Selective_Drop request issued over a Call...
Page 468
Message Scenarios B-60Issue 6 June 1997 Messages Sent by the Adjunct ProcessorMessages Sent by the Switch Comments FAC [CRV=99, FIE(Invoke, Inv_id=11, 3P Selective Drop, call_id=34)]AP Requests to Drop Station 4569 from Call — x4569Association FAC [CRV=99, FIE(Return Result, Inv_id=11)]Station 4569 Dropped from Call — x4569 Association FAC [CRV=100, FIE(Invoke, Inv_id=4, Event Report, call_id=65,party_id=2, event=drop, connected number=#####, cause=normal clearing)]Drop Event Report (Caller...
Page 469
8. Call Redirection Issue 6 June 1997 B-61 8. Call Redirection This section presents several scenarios for call redirection (for example, Coverage, Call Forwarding, Send All Calls or ASAI Redirect Alerting Call). Incoming Call to Station Forwards to Another Station This scenario shows the call flow for a call from station 3568 to station 3569 (see Figure B-24). Station 3569 has call forwarding active to station 6055. Station 6055 answers the call. Assume that Third Party Domain (Station) Control is...
Page 470
Message Scenarios B-62Issue 6 June 1997 Messages Sent by the Adjunct ProcessorMessages Sent by the Switch Comments REG [CRV=79, FIE(Invoke, Inv_id=1, Request Feature, feature=Activate Call Forwarding, redirecting number=3569, redirection number=6055)]AP Requests to to Activate Call Forwarding for Station 3569 REL COMP[CRV=79, FIE(Return Result, Inv_id=1)]Call Forwarding Activated FAC [CRV=86, FIE(Invoke, Inv_id=3, 3P Auto Dial, called number=3569)]AP Requests Auto Dial Call to Station 3569 — x3568...