Hi all,
I'm a student. My group is testing IP PBX based on Asterisk for conformity to
SIP RFC's. We wrote a bash script that uses SIPp 3.1, but we have one problem.
The PBX is sending OPTIONS requests with Call-ID different than in other
messages in our scenarios periodically and it causes SIPp to abort scenario
with result listed below:
"Aborting call on unexpected message for Call-Id '4bad882e732..."
We tried several things, but with no effect:
1. We modified call.cpp file so that SIPP answers 200 OK to OPTIONS when
launched with -aa option. It works, but after sendind 200 OK SIPp ends scenario
with: "Call limit reached (-m 1), 0.172 s period 7 ms scheduler resolution".
How can we make SIPp send 200 OK and continue current scenario as if nothing
had happened?
2. We tried executing out-of-call scenarios with -oocsn and -oocsf options, but
it doesn't work. The call is aborted too. Maybe, we are doing something wrong.
Please help. We can't continue our work without solving this problem. I can
provide more information if necessary. Thank you.
Maciej Sac
------------------------------------------------------------------------------
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
