Hey All,
Thought I'd share this update. Although the error log was empty, I enabled
the "-trace_stat" flag and reviewed the CSV file that was created. The
calls were failing due to the TCP socket timing out, therefore I
subsequently enabled the flag "-reconnect_close false" which allowed SIPp
to wait for the incoming UPDATE. The issue now is that when the the "UAS"
(SIPp acting as UAC) attempts to open up a new socket with SIPp, the
following error is being generated (behaving as expected):
2013-03-24 01:32:49:266 1364106769.266590: Returning EPIPE on
invalid socket: 0x2639070 (-1).
2013-03-24 01:32:49:266 1364106769.266773: Broken pipe on TCP
connection, remote peer probably closed the socket.
This makes sense since the TCP connection was originally SIPP:ephermeral>
UAS:5060, and now it is the UAS:ephermal > SIPp:5060 for the new
connection. I've attempted to work around this by executing the SIPp
application as a UAC, exiting SIPp, then immediately opening up another
instance of SIPp as a UAS to wait for the incoming UPDATE. As you imagine,
there are some inherent issues with this that I'm still trying to work
out. If you have any other suggestions, please let me know.
Cheers,
Matt Chung
On Sat, Mar 23, 2013 at 12:22 PM, Matt Chung <itsmemattch...@gmail.com>wrote:
> Thanks for the response Rob. I have attached the xml file to the e-mail,
> listed the version, and command to start SIPp below. Please let me know if
> you need anything else or if you have any suggestions. Thanks again!
>
> ./sipp -sf ctx_onestringdial_refresh.xml 10.88.87.216 -t tn -m 1
> -trace_logs -trace_msg -rtp_echo -trace_screen -trace_err
>
> SIPp v3.3-PCAP, built Mar 7 2013, 11:51:40.
>
>
>
>
> On Sat, Mar 23, 2013 at 5:49 AM, Rob Day <r...@rkd.me.uk> wrote:
>
>> On 23 March 2013 04:21, Matt Chung <itsmemattch...@gmail.com> wrote:
>> > My main question is SIPp hard coded to exit
>> > after 2 minutes of not receiving a request, regardless of pause/timeout
>> > being set to greater than 2 minutes (i.e pause milliseconds="840000" or
>> > timeout="840000") ?
>> >
>> > Essentially, I'm waiting for the session to be refreshed by the UAS at
>> the
>> > 15 minute mark (half of session-expires: 1800); call setup is
>> successfully
>> > however when SIPp reaches the following element), SIPp will exit after 2
>> > minutes:
>>
>> This surprises me, and doesn't match what I've seen in my use of SIPp.
>> I certainly don't think there should be a hard-coded limit of 2
>> minutes.
>>
>> I'd like to see, if possible, the command line you're using to start
>> SIPp, the XML file, and the version of SIPp (i.e. the first line of
>> `sipp -v`). That should let me try and reproduce it.
>>
>> --
>> Robert K. Day
>> robert....@merton.oxon.org
>>
>
>
>
> --
> -Matt Chung
>
--
-Matt Chung
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
