Actually a re-think... I see the command line option (sorry), but the "repeat" option does indeed cause a reset of the CSeq.
Can I hear the general feeling on the usefulness of the repeat mechanism clearing the current state? I think it is more useful for a repeat to not reset CSeq and other SIP specification information (branch, tags etc) so that the feature is more useful? Kind regards /Glyn -----Opprinnelig melding----- Fra: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] vegne av Glyn Parker Sendt: 9. mai 2007 13:00 Til: Sipp-Users (E-post) Emne: [Sipp-users] CSEQ Hei, Further to my investigations on using SIPp as a generic script engine against multiple servers. In order to simulate a full client I would want to create two scripts (for example). one for REGISTERs and one for INVITEs. The register script would want to be very simple and generic so that it can be used to emulate any client credentials and reused for any register attempt. For this authentication needs to be passed on the command line (see my previous post with a fix). So the script would only contain the following... REGISTER --> 401 <-- optional REGISTER --> (with dynamic credentials) 200OK <-- I would then run the script every 30 seconds or so (simulating the client perfectly). Ok so whats the catch? Each time a script is ran the SIPp process starts CSeq at 1. This is not very practical when keeping scripts generic and simple (read maintainable) so I propose initially to pass a CSeq start at the command line. Perhaps a better and future idea is for the SIPp application to set environment variables with "the last CSeq used in the script" or some other mechanism to communicate with the scripts from / to the outside world. Just to clarify what I am trying to do... A unix shell script which controls the monitoring of x number of sip servers by emulating x clients against them and making simple calls to ensure the servers are properly providing service. This is a secure production SIP environment so there is no way to avoid periodic REGISTER messages. Having a script which holds a call for 10 minutes with embedded REGISTER messages at an interval of 25 seconds would be huge and very difficult to maintain. The cseq must not reset each register because on a non forking platform (like this one) it assumes a new client and blocks it. This is quite normal on some production VoIP systems. I think this would be a good addition to SIPp functionality and I will provide a patch shortly if someone has not already done such a change? Best and Kindest regards. /Glyn ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
