On 1/2/08, Charles P Wright <[EMAIL PROTECTED]> wrote:
> I don't think SIPp should automatically fail the call. Based on the
> statistics file, do you know what the failure reason is listed as?
If I start one call, I get those errors reported in the CSV statistics file:
FailedCall(P): 1
FailedCall(C): 1
FailedCallRejected(P): 1
FailedCallRejected(C): 1
All other "failed call" counters are set to zero.
>
> The error log message is actually a warning, as long as you don't jump to
> the end, the call should not be terminated. Are there any other messages
> in the error log file after this one?
To make the things clear (sorry if my explanations weren't clear
enough), the call is not actually terminated, it continues as
expected, but is marked as failed in the statistics.
Here is the full content of the error log:
"sipp: The following events occured:
2008-01-02 19:50:02:864 1199299802.864035: Call-Id:
[EMAIL PROTECTED], receive timeout on message 10, jumping to label 2.
2008-01-02 19:50:32:898 1199299832.898937: Call-Id:
[EMAIL PROTECTED], receive timeout on message 10, jumping to label 2.
2008-01-02 19:51:02:927 1199299862.927862: Call-Id:
[EMAIL PROTECTED], receive timeout on message 10, jumping to label
2."
>
> Charles
>
Regards,
K.L.
> "K L" <[EMAIL PROTECTED]> wrote on 01/02/2008 11:22:46 AM:
>
> > 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
