SIPp should be able to receive and process the message from a different port. I would use a combination of packet capture and -trace_msg to make sure the packet arrives at SIPp.
Charles "Romain Gautier" <[EMAIL PROTECTED]> wrote on 09/24/2008 04:37:54 AM: > Hi, > > I am trying to use SIPp as an UAC, using a scenario. > My problem is that SIPp does not seem to recognize the SIP > responses. Indeed the 180 trying is not taken into account by SIPp. > The remote part use a different port in order to send its response, > is it a problem? Is there any turn-around? > > SIPp(5060) Remote > INVITE (port 5060) ------------------------> port 5060 > port 5060 <------------------------ TRYING from port > XXXX (dynamic port) > > > Thank you for your answer. > Cordially > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Sipp-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/sipp-users ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
