On Mon, Oct 10, 2011 at 10:54 PM, Michelle Kearney <
[email protected]> wrote:
>
> Hi,
>
> I am new to SIPp. I have a call scenario set up where I send an invalid
> message and expect to receive a "400 Bad request".
>
> This "400 Bad request" is received by SIPp but is seen as an unexpected
> message and the call is aborted:
> "while expecting '400' (index 1), received 'SIP/2.0 400 Bad Request"
>
> The xml scenario for the 400 response is:
> <recv response="400">
> <action>
> <log message="[timestamp] - Call-ID [call_id]: - 400 Bad
> Request"/>
> </action>
> </recv>
>
> How can this 400 bad request be handled better so the call is not aborted.
> I have tired several way and am having no joy.
>
I did a quick test here with SIPp version svn590 and I am not able to
reproduce this.
Please check which version you are using as it could be a bug in a older
version.
Other than that, maybe there is an error in the xml file. Please show us the
full scenario.
regards,
Takeshi.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
