/mcpResult Expected Behavior Scenario Pre-Condition S.No. Call is established between A and B Two address objects are created, one for A and one for B. All the appropriate call related events are delivered to both the addresses. Calls between addresses with same DN in different device but different partitions should go through. A and B are two addresses in the same cluster with same DN and different partitions (P1, P2) and in same cluster. A calls B. CSS of A has B’s partition in it first. 1 Call is established between A and B. Two address objects are created, one for A and one for B. All the appropriate call related events are delivered to both the addresses. Calls between addresses with same DN in same device but different partitions should go through. A and B are two addresses with same DN in same device but different partitions (P1, P2) and in same cluster. A calls B. CSSof A has B’s partition in it first. 2 C is successfully able to unpark the call from park DN. JTAPI should allow C to unpark the call from park DN. A calls B. B parks the call. C unparks the call from a park DN which is same as C’s DN. A, B, and C are three different addresses with different DN. (P1, P2, P3). A park DN is configured with same DN as C and different partition (P4). 3 A is able to call B. B should be able to park the call at the park DN. C should be able to pick up the call. JTAPI should allow C to unpark the call from park DN. A calls B, B parks call at park DN. C unparks the call. A, B, and C are three different addresses having the same DN and different partitions (P1, P2, P3). Apark DN is configured with same DN but belonging to a different partition (P4) 4 JTAPI maintains the address objects based on partition info and DN. Three address objects are returned each corresponding to A, B and C. JTAPI calls getPartitionAddress(DN of A). A, B, and C are three different addresses with same DN and different partitions (P1, P2, and P3) 5 Partition strings of the addresses are returned correctly. Application calls getPartition() on the address objects of A and B. A and B are addresses with same DN but belong to different partitions (P1, P2). 6 Address objects for A and B are created successfully. Lines A and B will be opened, but since they have different DN, user need not specify the partition info. DN alone is sufficient to open the lines, but users can also give partition info and both modes of opening lines will be supported by JTAPI. JTAPI supports old API to open lines when DN is different. There will be no change in behavior. A and B are two different addresses (different DNs) belonging to different partitions. A and B are in the control list of the same user. Provider open is completed and the lines are opened. 7 Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 1342 Message Sequence Charts Message Sequence Charts