we are using the sipp to test advanced SIP features like 3PCC scenarios. We found for some scenarios limitation is the sipp with the concept "one Call-Id per one sipp scenario". If we have for example outgoing call which is ended and then we wait for new call from server with different id the sipp complains with following message "Discarding message which can't be mapped to a known SIPp call" and the incoming message is discarded. In fact the same happens also if we put together in one script outgoing REGISTER and incoming INVITE.
Our proposal is to define a new command line switch with following features
- the switch will be valid just together with parameter -m 1
- the scenario will in this case continue further even if the received message has different Call-ID. No discarding or attempt to start the new run of script
- with this switch just 1 call will be active.
Log in to post a comment.