Cool. I have the source code open now. So far with 3.0 I have been able to do everything I need to do without paging through the source code. As you mentioned, I'll try grabbing a recent trunk and playing around with the latest greatest.
Dave. This email message and any attachments may be confidential and/or privileged to Nortel. If the reader of this message is not the intended recipient, you are hereby notified that any use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to this message or by calling the sender and then destroying all copies of the message and any attachments. -----Original Message----- From: Charles P Wright [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 04, 2008 8:31 AM To: Adams, David (CAR:3P33) Cc: [EMAIL PROTECTED]; Peter Higginson; sipp_users Subject: Re: [Sipp-users] SIPP Conditional Branching with If-Then-Else Variable Testing BTW, I believe special tags he referenced are _uenxp.main (a label to jump to), _unexp.retaddr (can be used with a jump action to return), and _unexp.pausedaddr (the clock tick until we were paused at the time of the trap). I haven't used these in quite a while, but I think they should still work. My "dream" was to embed all error handling in the scenario; but I haven't had time to work more on it. Charles "David Adams" <[EMAIL PROTECTED]> 11/04/2008 08:21 AM To "Peter Higginson" <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>, "sipp_users" <[email protected]> cc Subject Re: [Sipp-users] SIPP Conditional Branching with If-Then-Else Variable Testing Thanks guys! Those are both useful suggestions as well. I'm building a multi-simulator extended 3PCC model with some funky error paths. I think I have a powerful arsenal of techniques now to finish building my scenario error-handling. thanks again, Dave Adams. This email message and any attachments may be confidential and/or privileged to Nortel. If the reader of this message is not the intended recipient, you are hereby notified that any use, disclosure, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to this message or by calling the sender and then destroying all copies of the message and any attachments. From: Peter Higginson [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 04, 2008 4:43 AM To: [EMAIL PROTECTED]; sipp_users Cc: Adams, David (CAR:3P33) Subject: RE: [Sipp-users] SIPP Conditional Branching with If-Then-Else Variable Testing I'm not actively using SIPP since I left Newport Networks but I thought you could add branches to PAUSE statements - I'm sure I used to do that. You could also try NOP (but that was post the version I was using). Peter Date: Tue, 4 Nov 2008 09:00:03 +0100 From: [EMAIL PROTECTED] To: [email protected] CC: [EMAIL PROTECTED] Subject: Re: [Sipp-users] SIPP Conditional Branching with If-Then-Else Variable Testing David Adams wrote: Hi, I'm trying to build error-handling into a scenario with conditional-branching and variable testing. With the latest stable version of SIPP, I know I have the ability to use regexp to populate variables, and then in some actions such as <send> / <receive> I can test a variable and jump to a label after the <send> or <receive> action has been executed. What I'd like to be able to do is setup a variable, then based on whether the variable is set or not, then go to a different place in my scenario file. So far I have not been able to figure how to do this, if it's even possible. SIPP seems to support the "Else" part of the If-Then-Else with the variable testing and next arguments as part of <send> and <receive> operations. 1. Is there a way to do this in SIPP3.x? If not, 2. Could you direct me to the most logical place in the code that I would need to modify to build this feature? Thanks, Dave Adams. Hello Adams, Yes you can build error handling. Personally, I use the next statement of the receive, + regexp. I do not need 'else' There is also a special tag for unexpected message catch + return jump. Please look at conditional testing in the SIP unstable version documentation. The difficult part is to build regexp; remind that the matching is GLOBAL ( multiline) not , by line !! So you must be prepare to match \r\n ! I always put a <action><log> just after my regexp to check them ! There is no good trace for now in that area. Hope that help Francois Example: testing against content of a key <nop> <action> <assignstr assign_to="8" value="[imediaDirection]" /> <test assign_to="9" variable="8" compare="equal" value="1"/> </action> </nop> example RTP param extract <nop next="1" test="9"> </nop> <recv response="200"> <!-- wait response, and extract RTP port --> <action> <!-- get the audio rtp port and IP to send to --> <ereg regexp="IP4 ([0-9]+\.[0-9]+\.[0-9]+\.[0-9]+)" search_in="msg" assign_to="0,10"/> <ereg regexp="m=audio ([0-9]+) RTP" search_in="msg" assign_to="0,11"/> </action> </recv> Get the best wallpapers on the Web - FREE. Click here! ------------------------------------------------------------------------ - 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
