Call Scenarios and Applications
16. Single-Step Conference
In call sequence 1, a service observer is added to the call using
NOTE:
State or national laws may require you to inform the parties on a call that the call is being monitored.
Just prior to the messages shown, the application learned (via domain control on station 3001) that a call with CID 17 has alerted at station 3001 and has been answered. The application knows that the station 3010 wants to service observe any call that arrives at this station.
Call Sequence 1:
Host | ECS | Comment | |||||
|
|
| Domain Control Request |
|
| Get domain control on observer. | |
|
|
|
|
| |||
|
|
| (CRV=15, Domain=station 3010) |
|
| ||
|
|
|
|
|
| ||
|
|
| Domain Control Acknowledgement |
|
|
| |
|
|
|
|
|
| ||
|
|
| (CRV=15) |
|
|
| |
|
|
| Single Step Conference |
|
| Adds observer to call. | |
|
|
| (CRV=15, CID=17, visibility=none) |
|
| ||
|
|
|
|
|
| ||
|
|
| Single Step Conference Acknowledgement |
|
|
| |
|
|
| (CRV=15) |
|
|
| |
|
|
| 3rd Party Drop |
|
| Application learns that observer | |
|
|
|
|
| needs to listen and talk. First it | ||
|
|
| (CRV=15, CID=17) |
|
| drops the observer from call. | |
|
|
| Single Step Conference |
|
| Now it | |
|
|
| (CRV=15, CID=17, visibility=full) |
|
| this time with a talk path. | |
|
|
|
| ||||
|
|
| Single Step Conference Acknowledgement |
|
|
| |
|
|
| (CRV=15) |
|
|
| |
|
|
| Drop Event Report |
|
| Caller drops from the call. | |
|
|
| (CRV=15, CID=17, connected=#####) |
|
| ||
|
|
|
|
|
| ||
|
|
| 3rd Party Drop |
|
| Application drops observer, | |
|
|
| (CRV=15, CID=17) |
|
|
| so that the call will drop. |
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|