Hi mr King, Assuming you want to register and than you want to listen for calls, there is a simple way to do this: - start a register scenario on sipPort X, rtpPort Y - start a scenario that is listening for Invites and so on, using the same sipPort X, rtpPort Y.
That is it. Regards, Costin Radu On 21.iunie.2011 01:00, William King wrote: > I seem to be running into a problem where either the sipp scenario is a > client(in which case any new INVITE does not map to a known call) or a > server(which prevents sending the registration credentials). > > Is there a known solution? > > ------------------------------------------------------------------------------ > EditLive Enterprise is the world's most technically advanced content > authoring tool. Experience the power of Track Changes, Inline Image > Editing and ensure content is compliant with Accessibility Checking. > http://p.sf.net/sfu/ephox-dev2dev > _______________________________________________ > Sipp-users mailing list > Sipp-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/sipp-users ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
