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

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

    Page
    of 600
    							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 Connects to
    Alerting Call) —
    x4568 Association
    FAC [CRV=99, FIE(Invoke,
    Inv_id=10, Event Report,
    call_id=12, party_id=2,
    event=connected,
    calling number=4569,
    called number=4568,
    connected number=4568)]Connected Event Report
    (4568 Connects to
    Alerting Call) —
    x4569 Association
    FAC [CRV=100, FIE(Invoke,
    Inv_id=10, Event Report,
    other_call_id=77,
    resulting_call_id=12,
    event=call transferred,
    calling number=4569,
    called number=4568,
    old party_id=resulting call 1, 
    old party_id=resulting call 2,
    old party_id=oldcall1,
    party_id=1, party_id=2,
    connected number=4568,
    connected number=#####)]Call Transferred
    Event Report
    (x4569 Transfers Call
    to x4568) —
    x4568 Association
    FAC [CRV=99, FIE(Invoke,
    Inv_id=4, Event Report,
    other_call_id=77,
    resulting_call_id=12,
    event=call transferred,
    calling number=4569,
    called number=4568,
    old party_id=resulting call 1, 
    old party_id=resulting call 2,
    old party_id=oldcall1,
    party_id=1, party_id=2,
    connected number=4568,
    connected number=#####)]Call Transferred
    Event Report
    (x4569 Transfers Call
    to x4568) —
    x4569 Association 
    						
    							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 Endpoint
    x4590x4567Stations
                call_id=45
    Connected
    call_id=34
    Controlled Stations — Call State Transitions
    x 4567
    call_id=45 — Connected —> Dropped
    call_id=78 — Held —> Connected —> Held —> Merged with call_id=34
    x 4569
    call_id=34 — Alerting —> Connected Endpoint Unknown
    Held —> Transferred to 4569
    call_id=78
    x4569
    call_id=34 — New Call —> Transferred to x4569 
    						
    							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 number=#####,
    connected number=4569)]Call Transferred
    — x4567 Association
    FAC [CRV=99, FIE(Invoke,
    Inv_id=8, Event Report,
    other_call_id=78,
    resulting_call_id=34,
    event=call transferred,
    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 number=#####,
    connected number=4569,
    calling number=4567,
    called number=4569)]Call Transferred
    Event Report
    (Station 4567 Transfer
    Completed) —
    x4569 Association
    FAC [CRV=99, FIE(Invoke,
    Inv_id=10, Event Report,
    call_id=34, party_id=3,
    event=connected,
    calling number =4590,
    called number=4569,
    connected number=4569)]Connected Event Report 
    (Station 4569 Connects to 
    Transferred Call) — x4569 
    Association 
    						
    							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 Endpoint 
    						
    							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 [CRV=86, FIE
    Return Result, Inv_id=1,
    Value Query,
    call_id=12, call_id=65,
    party_id=1, party_id=1,
    call_state=connected,
    call_state=held)]Two Calls Present
    at Station 4568
    REG [CRV=86, FIE(Invoke,
    Inv_id=1, Value Query,
    item=Party_id,
    call_id=12)]AP Requests the
    Parties Connected
    to Call 12
    REL COMP [CRV=86, FIE
    (Return Result, Inv_id=1,
    Value Query,
    party_id=1, party_id=2,
    connected number=4568,
    connected number=#####)]Two Parties
    Connected to Call
    (Party 2 is a
    Trunk)
    (Continued on next page) 
    						
    							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 Call 34
    REL COMP [CRV=55, FIE
    (Return Result, Inv_id=1,
    Value Query,
    party_id=1, party_id=2,
    party_id=3,
    connected number=4590,
    connected number=#####,
    connected number=4569)]Three Parties
    Connected to Call
    (Party 2 is a
    Trunk)
    FAC [CRV=75, FIE(Invoke,
    Inv_id=1,Value Query,
    domain=Station 4569)]
    REL COMP [CRV=75, 
    (Return Result, Inv_id=1,
    Value Query,
    domain=talk state idle)]AP Request Station
    Status for Station
    4569
    Station Active
    on a Call 
    						
    							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 Control association. 
    This scenario is a continuation of the previous scenario.
    Figure B-23. Call Flow for Call Disconnects
    DEFINITY ECS
        Stations
    x4568
    External Endpoint
    x4569
    x4590 External EndpointCall Dropped
    call_id=65
    Call Dropped
    call_id=12
    Endpoint Dropped
    call_id=34
    x4567 External Endpoint 
    						
    							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 Disconnects) 
    — x4568 Association
    FAC [CRV=100, FIE(Invoke,
    Inv_id=6, Event Report,
    call_id=65, party_id=1
    event=drop,
    connected number=4568,
    cause=normal clearing)]Drop Event Report
    (Call Terminates) —
    x3468 Association
    REG [CRV=85, FIE(Invoke,
    Inv_id=1, 3P Take Control,
    call_id=12)]AP Requests to Take
    Control of Call 12
    FAC [CRV=85, FIE(Return
    Result, Inv_id=1,
    3P Take Control,
    party_id=1, party_id=2,
    connected number=4568,
    connected number=#####)]3P Take Control
    Granted
    FAC [CRV=85, FIE(Invoke,
    Inv_id=3, 3P Selective Drop,
    party_id=1)]AP Requests to
    Drop x4568
    FAC [CRV=85, FIE(Return
    Result, Inv_id=3)]Station 4568 Dropped —
    3P Association
    FAC [CRV=100, FIE(Invoke,
    Inv_id=12, Event Report,
    call_id=12, party_id=1,
    event=drop,
    connected number=4568,
    cause=normal clearing)]Drop Event Report
    (Station 4568 Drops) —
    x4658 Association
    REL COMP [CRV=85, FIE(Invoke,
    Inv_id=2, Call Ended,
    call_id=12)]Call Terminates —
    3P Association 
    						
    							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 active for stations 3568 and 
    3569 as shown in the Send All Calls scenario above.
    Figure B-24. Call Flow for Incoming Call to Station with Call Forwarding to 
    Another Station
    DEFINITY ECS
    x6055
    x3569x3568call_id=17
    Call Forwarding
    Active 
    						
    							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 Association
    FAC [CRV=86, FIE(Invoke,
    Inv_id=2, Event Report,
    call_id=17, party_id=1,
    event=call initiated)]Call Initiated Event
    Report (Station 3568
    Forced Off-Hook) —
    x3568 Association
    FAC [CRV=86, FIE(Invoke,
    Inv_id=2, Event Report,
    call_id=17, party_id=1,
    event=call originated,
    connected number=3568, calling 
    number=3568,
    called number=3569)]
    FAC [CRV=86, FIE(Invoke,
    Inv_id=4, Event Report,
    call_id=17, party_id=2,
    event=alerting,
    calling number=3568,
    called number=3569,
    connected number=6055
    cause=325)]Alerting Event Report
    (Call Delivered to
    Station 6055) —
    x3568 Association
    FAC [CRV=86, FIE(Invoke,
    Inv_id=6, Event Report,
    call_id=17, party_id=2,
    event=connected,
    calling number=3568,
    called number=3569,
    connected number=6055)]Connected Event Report
    (Station 6055 Answers
    Forwarded Call) —
    x3568 Association
    FAC [CRV=86, FIE(Invoke,
    Inv_id=8, Event Report,
    call_id=17, party_id=1,
    event=drop,
    connected number=3568,
    cause=normal clearing)]Drop Event Report
    (Station 3568 Disconnects
    from Call) —
    x3568 Association
    (Continued on next page) 
    						
    All Lucent Technologies manuals Comments (0)

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