As a work-a-round, when you do your SUBSCRIBE signal, change the SIP contact header to include a different port, for example 60000. Then initiate another instance of SIPp on that port (60000) that listens for incoming NOTIFY signals and responds 200 "OK".
I've used this before using SIPp 3.0. HTH, Simon On Thu, Sep 25, 2008 at 12:54 AM, Katwala, Kalpesh N (Kalpesh)** CTR ** <[EMAIL PROTECTED]> wrote: > Hi All, > > I am using SIPp3.1 to Register a UE with SUBSCRIBE/NOTIFY. I want SIPp > to generate an automatic 200OK response to the NOTIFY message. I tried > using "-aa" option, however, when I look at the trace - SIPp does not send > out a 200 OK of NOTIFY. > > Do I need to add anything besides the -aa on the command line? > > thx, > Kalpesh. > ------------------------------------------------------------------------- > 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
