Michael, You may be able to do something by creating 3 instances of SIPp and third party call control, in which the first instance sends to the session director, and the second and third send to the other IPs.
Charles [EMAIL PROTECTED] wrote on 03/19/2008 09:26:23 AM: > All, > > I have a scenario with the Ubiquity App Server in which by initial > Invite goes to a Ubiquity Session Director IP like 1.1.1.1, but the > rest of the commands/responses need to go to the Ubiquity Service > Host like 2.2.2.2 or 3.3.3.3 (depending on which one they have > selected). Because the way Ubiquity is written, the contact is > always to the Session Director (1.1.1.1) because a Bye process can > be routed to a different Service host. > > So I looking to capture the layer 3 address in the 100 trying and > use this for all other commands and responses. > > Hope this makes sense. > Michael > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Sipp-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/sipp-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
