> On 21 January 2014 22:25, <henrik.le...@tieto.com> wrote: >> The SIPp 3PCC mode with the sendCmd and recvCmd can be used to exchange >> out-of-band information between uas and >> uac if the App under test is a SIP Proxy, where the Call-ID is unmodified >> and thus known by both uas and uac SIPp processes. >> But when testing a B2BUA Application, the Call-ID on the uas side of the >> B2BUA is not known on the uac side. >> Are there any known tricks to synchronize these two SIPp processes?
Henrik, I've thought a little more about this, and think there might be a way to make this work. It's possible for the UAC to add a custom header (let's call it P-Correlation-Header) with its Call-ID, which won't be stripped out. Then the UAS side knows both its own Call-ID (from the Call-ID header) and the UAC's Call-ID (by parsing it out of the P-Correlation-Header). It can then do <sendcmd> Call-ID: [$value_from_p_correlation_header] UAS-Call-ID: [call_id] </sendcmd> and the UAC side can parse that to learn the UAS side's Call-ID. Now both the UAC and the UAS know what the other side's Call-ID is, and can do 3PCC as normal. Do you think that would solve your problem? Best, Rob ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
