Hello,
It can be handle within scenario.
1. INVITE ------------------> === SIPp sends INVITE to UAS
2. 100 Trying <------------- === attribute ‘optional=true’
3. 180 Ringing <----------- === attribute ‘optional=true’
4. 200 OK <---------------- === receive 200 OK from UAS
4.1 ACK --->
5. Waiting for BYE request from called party until timeout (45s)
If BYE request is received, jump to "label id=3"
<recv request="BYE" timeout="45000" ontimeout="2" next="3">
</recv>
6. Send BYE request in case of ontimeout
<label id="2"/>
BYE --->
7. Handle incoming Response and jump to End of scenario
<recv response="200" crlf="true" next="99">
</recv>
8. if BYE received from Called party, send Response
<label id="3"/>
200 OK -->
9. End of scenario
<label id="99"/>
10. Pause(30seconds)------
Regards
Zsolt
2014-05-05 14:02 GMT+02:00 Mahudeswaran A <mahudeswara...@acqueon.com>:
> Hello All,
>
>
>
> In SIPp load testing, how to make the BYE request as optional;
>
> Call scenario:
>
> 1. INVITE ------------------> === SIPp sends INVITE to UAS
>
> 2. 100 Trying <------------- === attribute ‘optional=true’
>
> 3. 180 Ringing <----------- === attribute ‘optional=true’
>
> 4. 200 OK <---------------- === receive 200 OK from UAS
>
> 5. Pause(45seconds)-----
>
> 6. BYE ---------------------->===send BYE to drop the call
>
> 7. 200 Ok <-----------------====receive 200 ok from UAS
>
> 8. Pause(30seconds)------
>
>
>
> In the above scenario; at step-5 while SIPp is in pause mode sometime the
> UAS sends BYE message to SIPp.And SIPp treats this as unexpected message
> which is OK in SIPp perspective;
>
>
>
> If SIPp receives unexpected BYE message, then will it proceeds in normal
> flow or it will treat this as failure call;
>
> Is this an issue,
>
> Or
>
> IS there any option available to handle this situation!!
>
>
>
> Regards
>
> Mahu
>
>
>
>
> ------------------------------------------------------------------------------
> Is your legacy SCM system holding you back? Join Perforce May 7 to find
> out:
> • 3 signs your SCM is hindering your productivity
> • Requirements for releasing software faster
> • Expert tips and advice for migrating your SCM now
> http://p.sf.net/sfu/perforce
> _______________________________________________
> Sipp-users mailing list
> Sipp-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sipp-users
>
>
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users