Hi Niral, I would recommended using two (2) instances of SIPp on the same machine but using different ports. One instance for the initial REGISTER / 200 OK signaling using port 5060, and a second instance, known as a SIPp listener, for receiving the unsolicited NOTIFY's on port 5069 (for example).
In the initial REGISTER signal simply hardcode port 5069 in the contact header. HTH, Simon On Jan 12, 2008 2:13 AM, Niral Sheth <[EMAIL PROTECTED]> wrote: > I would like to know how I could get sipp client to send an OK to a an > unsolicited Notify after a register/ok sequence. > > The sequence is: > > SIPp client sends register > receives ok > > After this I typed in <recv request = "NOTIFY"/> > send OK > > This Notify uses different call ID etc. Is there a way to get the sipp client > to respond to the notify with an OK in this scenario? > > Appreciate the help > > > > ____________________________________________________________________________________ > Never miss a thing. Make Yahoo your home page. > http://www.yahoo.com/r/hs > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Sipp-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/sipp-users > ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
