Lucent Technologies 555-230-220 User Manual
Event Reporting and U-Abort Capabilities
Issue 7 May 1998
3-59
Transfer and Conference Interactions
Call associated information for event reports has the following interactions:
Before a transfer has completed, each part of the call will include information on
the calling number and the called number. For example, if trunk xxxxx calls station
12345, and station 12345 transfers the call to station 23456, before the transfer
operation completes two calls will exist. The first call is the calling party xxxxx
connected to the called party at station 12345. The second call will have the
calling number 12345 connected to the called party 23456. After the transfer
completes, calling number 12345 will no longer be on the call and only one call
will exist with the calling party being trunk xxxxx and the called party station
23456.
the calling number and the called number. For example, if trunk xxxxx calls station
12345, and station 12345 transfers the call to station 23456, before the transfer
operation completes two calls will exist. The first call is the calling party xxxxx
connected to the called party at station 12345. The second call will have the
calling number 12345 connected to the called party 23456. After the transfer
completes, calling number 12345 will no longer be on the call and only one call
will exist with the calling party being trunk xxxxx and the called party station
23456.
If the above scenario were to describe a conference, then number 12345 would
not drop off the call but would remain connected to the other parties. As there can
only be one calling party and one called party, the final value for the caller and the
called will depend on how the calls are merged. Once a conference has been
established it should not be assumed that the calling party would be the same
calling party that was on the original call. It is possible that the calling party could
very well be the party that placed the second call to conference the calls together.
not drop off the call but would remain connected to the other parties. As there can
only be one calling party and one called party, the final value for the caller and the
called will depend on how the calls are merged. Once a conference has been
established it should not be assumed that the calling party would be the same
calling party that was on the original call. It is possible that the calling party could
very well be the party that placed the second call to conference the calls together.
If the application wants the number that the answering station called, it must be
retrieved as the called number in an event report before the merge has
completed. If the second call does not generate the event report until after the
merge has completed, then the application cannot be sure of the meaning of the
called party.
retrieved as the called number in an event report before the merge has
completed. If the second call does not generate the event report until after the
merge has completed, then the application cannot be sure of the meaning of the
called party.
In a conference scenario, incoming PRI calls which contain either II-Digits or
R2-MFC ANI are not guaranteed to contain the IEs after the merge is complete.
R2-MFC ANI are not guaranteed to contain the IEs after the merge is complete.
In transfer and conference scenarios, the UCID reported is the resulting UCID
kept with the call. Consult
kept with the call. Consult
DEFINITY
Enterprise Communications Server Release
6 Administration and Feature Description
, 555-230-522 for further details on
merging Universal CalI IDs.