Question: In a Multiparty call setup test scenario, what is the significance of assigning different transaction identifiers to calls (e.g., Call A-B, Call A-C, Call A-D, Call A-E)?
Option 1: To ensure each call's signaling is uniquely identifiable across the network, preventing potential call mix-ups.
Option 2: Solely for logging purposes, to simplify post-test analysis of call sequences.
Option 3: To dictate the order in which calls are established during the multiparty setup process.
Option 4: For billing differentiation among the various legs of the multiparty call.
Explanation: Assigning different transaction identifiers to each call (e.g., Call A-B, Call A-C) is crucial for ensuring that each call's signaling messages are uniquely identifiable. This uniqueness prevents potential errors or mix-ups in handling calls across the network, especially in complex multiparty scenarios where multiple simultaneous calls are involved.