Hi Milos,
If you use the -trace_err argument to SIPp, you'll get a log file
containing the exact unexpected message it saw. It may be that your
authentication is wrong and so you're getting a 403 Forbidden instead
of the 200 OK.
Best,
Rob
On 3 April 2014 15:09, Crnjanski Milos
1. when you receive re-invite does it's call-id match to you curren't call's
call-id?
2. after receiving re-invite you are jumping to id 3 using next. after your
label id=3 do you have scenario to expect 200 for the INFO which you sent
earlier.
3. what if 200 for your INFO comes and then re-invite
Hi,
Once call is up, I'm sending INFO message every 5 seconds. After few
minutes, I get a re-invite from far end. The following script terminates
with error.
Please share your thoughts to handle the same.
Thanks,
Shamik
label id=5/
nop increase CSeq count /nop
pause milliseconds =
-users] Unexpected-message.
Hi
I am using SIPP for performance testing. In high call rate I am seeing
more unexpected messages are coming. My call rate is 500 calls per second
and call hold time is 200 sec. I think in this call load sipp is
generating lot of unexpected messages, how can
Hi
I am using SIPP for performance testing. In high call rate I am seeing
more unexpected messages are coming. My call rate is 500 calls per
second and call hold time is 200 sec. I think in this call load sipp is
generating lot of unexpected messages, how can I avoid this?
Thanks
Hi all!
I have a fairly simple scenario which I use for automatic testing.
-- INVITE
-- 180
-- 200
-- ACK
-- INVITE
-- 200
-- ACK
-- BYE
-- ACK
-- 200
[ 4000ms] Pause
The sipp is run i.e.
According to section 3.12.1 of the guide (version 1.1) unexpected 4XX or 5XX
messages before a 200 OK should result in sending an ACK and ending the
call. Below is a log that shows this is not functioning. I am using the
built in UAC senareo, so nothing fancy. Since the 200 is never received,
