Call Scenarios and Applications
Call Coverage to Station — Station Monitoring
Caller | Coverage |
| User |
|
| Adjunct | User |
Phone | Phone |
| Phone | Switch |
| Terminal | |
|
| Processor | |||||
B | C |
| A |
|
|
| A |
|
|
|
|
|
| Application |
|
|
|
|
|
|
| Monitors Station |
|
|
|
|
|
| 3rd Party Domain Control |
| |
|
|
|
| Control granted | (domain=A) |
| |
|
|
|
|
|
| ||
|
|
| Call alerts | 3rd Party Domain |
| ||
|
|
|
|
|
| Caller information | |
|
|
| phone |
|
|
| |
|
|
|
|
|
| delivered to data | |
|
|
|
|
| Alerting Event Report (A) | ||
|
|
|
|
| screen | ||
|
|
| User doesn’t |
|
|
| |
|
|
|
|
|
|
| |
| Coverage |
| answer; call |
|
|
|
|
| goes to coverage |
|
|
|
| ||
| alerts |
|
|
| Update data screen | ||
|
|
|
| Alerting Event Report (C) | |||
|
|
|
|
| with new station | ||
|
|
|
|
|
|
| |
| Coverage Answers | Connected Event Report (C) |
| ||||
|
|
|
|
| |||
Coverage and |
|
|
|
|
|
| |
caller talk |
|
|
|
|
|
| |
|
|
| User answers | Connected Event Report (A) | Update data screen | ||
|
|
|
| ||||
| User, coverage, |
|
|
|
|
| |
| and customer |
|
|
|
|
|
|
| talk |
|
|
|
|
|
|
| Coverage disconnects |
| Dropped Event Report (C) | Update data screen | |||
|
|
|
|
| |||
| User and caller |
|
|
|
|
| |
| talk |
|
|
|
|
|
|
Caller disconnects |
|
|
| Dropped Event Report (B) |
| ||
|
|
|
|
|
| ||
|
|
| User disconnects | Dropped Event Report (A) | Update data screen | ||
|
|
|
|
| |||
|
|
|
|
|
|
| |
A call to a monitored station goes to coverage after alerting the station. Since the coverage point is another station, the monitored station (original destination) maintains a simulated bridged appearance for the call. The monitored station answers the call after the coverage station has answered the call.
Issue 7 March 1998
