Re: [Sipp-users] SIPp errors during load test

[Prashanth D. <Pra...@en...>]

Hi Pavel,

There are 2 systems(VMs) involved, client and server. Client is where I have SIPp running pushing calls to server @ 5060.
Yes, I believe my scenario is using single IP for both local and remote address. I have not seen more than 45 calls at a given time for my scenario.

I believe this issue to be somehow related to server receiving the calls. Ie SIPp's socket write fails due to remote end. How can I prove this ?
Until now, all these error occur during night.

For time being I have changed below items

* Switched to mono socket(-t t1) from multi socket(-t tn)
* enabled 'trace_calldebug'

Additional Info: 
I have second set of test environment(with 2 different VMs for client and server) where same scenario works fine w/o any issue.

Regards
Prashanth


Date: Tue, 24 Nov 2015 13:52:06 +0100
From: sindelka <sin...@tt...>
Subject: Re: [Sipp-users] SIPp errors during load test
To: sip...@li...
Message-ID: <565...@tt...>
Content-Type: text/plain; charset="windows-1252"

Hello Prashanth,

how many individual IP addresses are involved in the test? Is your SIPp UAC scenario using a single local IP address to send all the INVITEs to a single remote IP address? If so, how many sessions (calls) are in progress when the error occurs?

Pavel

Dne 24.11.2015 v 12:49 Prashanth Devarajappa napsal(a):
>
> Hello,
>
> At times during the load test(2 CPS, using TCP socket) SIPp stops with 
> below errors
>
> /sipp: The following events occured:/
>
> /2015-11-24 02:15:21.167250                1448331321.167250: Unable 
> to send TCP message: Transport endpoint is not connected./
>
> //
>
> /Problem EAGAIN on socket  31 and poll_idx  is 58 /
>
> /Added first buffered message to socket 31/
>
> /Problem EWOULDBLOCK on socket  31 and poll_idx  is 58 /
>
> /Exit problem event on socket 11 /
>
> /Wrote -1 of 640 bytes in an output buffer./
>
> I don?t see this error every time however. Server side don?t log 
> anything suspicious around that time stamp, server is still listening 
> on that port.
>
> How can I avoid/fix this error ?
>
> I can provide further information about the test environment.
>
> Any help would be appreciated.
>
> Regards
>
> Prashanth
>