McDewey

External Call Control You should assume that all devices in the following use cases are obsereved, unless explicilty stated otherwise in the use case description. The first few use cases go through the full event series for the basic call setup. After the first three or four, the use cases leave this part out, as it is standard for most of the use cases. If you do not see the basic call event series at the beginning of a use case, you can assume that it was intended to have happened successfully before the first event in the use case. The last column in the use cases, that specifies the call info for a various stage of the use case, will initially have the full method invocation to retrieve the call information, for example CiscoCall.getModifiedCallingParty(). After the first three or four uses cases, only the method name is specified, such as .getModifiedCallingParty(). You can assume that this is to be prefixed with CiscoCall unless explicitly stated otherwise, such as for the CiscoCallChangeEvs. Use Cases for BasicCall Basic Call Initiated From JTAPI / Phone Configuration Phone A, B are in cluster devices. Procedure: Application invokes connect() at A to call B, or physical phone for A dials the number for B. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 929 Message Sequence Charts External Call Control