Hi, Why do you need an ontimeout attribute ? Can't you just put
<label id="1" /> <recv request="BYE" optional="true" next="4"/> <label id="2" /> <recv request="INFO" optional="false" timeout="10000" ontimeout="3" /> ? If this BYE can also be received after the INFO message, an optional="global" element migh be used to make the BYE taken into account and jump to label 4. Or do I miss something ? Regards, Olivier Boulkroune -----Message d'origine----- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de K L Envoyé : mercredi 2 janvier 2008 17:23 À : Charles P Wright Cc : [EMAIL PROTECTED]; [email protected] Objet : Re: [Sipp-users] Strange behaviour on recv+optional+ontimeout On 1/2/08, Charles P Wright <[EMAIL PROTECTED]> wrote: > K L, > > If you jump to the end of the call SIPp marks it as failed automatically > (which I think is probably not the best possible behavior), but you can > easily get around it by doing something like: In my case, I don't jump to the end of the scenario: - If a BYE is received, I jump to the "next" label (4) to send a 200 OK. - If no BYE is received, I jump to the "ontimeout" label (2), to wait for another request (non-optional). So, in both cases, there is an action made, and I do not jump to the end of the scenario. > > <recv request="BYE" timeout="25000" ontimeout="2" next="4" /> > > ... > > <label id="2" /> > <!-- just so we have a scenario element after label 2 --> > <nop /> > <!-- end of scenario --> > > Charles > Regards, K.L. > [EMAIL PROTECTED] wrote on 12/31/2007 09:51:39 AM: > > > Hello, > > > > In a (UAC) scenario, I have the following line, to allow the remote > > UA to send a > > BYE during the call (after the dialog is established): > > > > <recv request="BYE" optional="true" timeout="25000" ontimeout="2" > next="4" /> > > > > Whether a BYE is received or not, I'd like the call to be considered > > as successful. > > If no BYE request is received from the remote UA, the call proceeds > normally. > > The problem is that the call is considered as failed by SIPp ("receive > > timeout on message 10, jumping to label 2"). > > > > Since the recv is marked as "optional", it seems strange to me that SIPp > > considers the jump to label 2 as an error. Is there an option to change > this > > behaviour ? > > > > Regards, > > K.L. > > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > > _______________________________________________ > > Sipp-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/sipp-users > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
