I can guess that your sip server gets overloaded and doesn't answer as quickly as your scenario expects. However, this is just a guess. As is said in my previous post, you should sniff the sip exchange and figure out if ACK is correct according to SIP. If it is correct then, you should read your scenario and figure out why the scenario doesn't expect ACK.

BR, Dmitry

John Barry wrote:
Hi Dmitry,

I try to run the default scenarios (sipp -sn uas and sipp -sn uac) between 2 machines (no proxy) and I am getting the same results. A lot of unexpected messages and retransmissions errors when reaching 500 cps.

Why the unexpected messages? It seems like a synchronization issue.

JB
------------------------------------------------------------------------
Date: Thu, 12 Feb 2009 20:36:42 +0300
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [Sipp-users] Aborting call on unexpected message error

Hi,

Apparently, your scenario doesn't expect ACK when it comes. You should, probably, follow the sip exchange and figure out if ACK is correct. If it is correct then fix your scenario.
HTH, Dmitry

John Barry wrote:


    Hello,

    I want to measure the performance of a OpenSER (1.3.2)proxy doing
    digest authentication. In my test bed I have an OpenSER proxy and
    two SIPp instances: one running the server scenario (uas), and the
    other one a modified client scenario to support INVITE
    authentication.

    While testing, I have notice that there are a lot of unexpected
    message errors and retransmissions when the load is relatively low
    (400 cps). At 400 cps, the server nor the SIPp instances are close
    to saturate their corresponding hardware resources.  I have done
    the same test before with a similar server, and I was able to
    reach at least 3,000 cps

    In the error log of the uas SIPp, I can see the following error:

    "Aborting call on unexpected message for Call-Id
    '[email protected] <mailto:[email protected]>': while
    pausing (index 6), received
     'ACK sip:[email protected] SIP/2..0"

    I have tested with SIPp versions 3.0 and 3.1 and I get the same
    behavior.

    Any ideas regarding what could be causing this problem?

    Thanks,
    JB


------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to