A call is delivered to an agent within a screening split. The screening agent transfers the call using consult transfer to a specialized agent at an individual station.
Example
Connected Party Number |
1234 |
Calling Party Number |
3035551726 |
Called Party Number |
9085557771 |
Switch Data |
|
Trunk Group Id |
|
Call Id |
101 |
Other Call Id |
|
LAI Display Info |
|
VIS Data |
|
Routing ID |
|
Ucid |
|
Uui |
|
Ani II Digits |
|
Redirecting Number |
|
Return Field |
C |
Connected Party Number |
2022 |
Calling Party Number |
3035551726 |
Called Party Number |
9085557771 |
Switch Data |
|
Trunk Group Id |
|
Call Id |
105 |
Other Call Id |
101 |
LAI Display Info |
|
VIS Data |
|
Routing ID |
|
Ucid |
|
Uui |
|
Ani II Digits |
|
Redirecting Number |
|
Return Field |
C |
Note that this CONNECT event for consult transfers to stations is not passed to a monitoring application until the screening agent completes the transfer by pressing the Transfer button a second time.
Connected Party Number |
2022 |
Calling Party Number |
3035551726 |
Called Party Number |
9085557771 |
Switch Data |
|
Trunk Group Id |
|
Call Id |
105 |
Other Call Id |
101 |
LAI Display Info |
|
VIS Data |
|
Routing ID |
|
Ucid |
|
Uui |
|
Ani II Digits |
|
Redirecting Number |
|
Return Field |
E |
Note that for consult transfers to stations as described in this scenario, the second CONNECT event identifies the original call in the Other Call Id field. Note also that this CONNECT event contains ASAI information that pertains to the original call, for example, original ANI and DNIS in the Calling Party Number and Called Party Number fields, respectively. Any LAI display information, Avaya IR system data, or switch data that is associated with the original call is also carried forward.