This is not easy to accomplish with a standard script, but if you make the
decision ahead of time about who will hang up you can probably communicate
it from the UAC to the UAS using custom headers or third party call
control.
Charles
[EMAIL PROTECTED] wrote on 08/23/2007 10:48:42 AM:
> Hi,
>
> I want to use sipp to act as a UAC, but both of UAC and UAS can send
BYE.
> What I want is that if UAS sends BYE first, UAC reply "200 OK".
> if UAC sends BYE before UAS, then wait for the response.
> if both send BYE almost at the same time, UAC reply "200 OK" and
> wait for the response.
> In this case, UAC should have higher priority to wait for BYE from
> UAS. That is, sipp can wait for BYE for a while, but as long as BYE
> is received, it must send "200 OK" immediately.
> Can sipp deal with this case?
> If there is a timer for <recv> command, the problem can be solved
somehow.
> Does anyone have an idea?
> Thank you in advance.
>
> Best,
> Zheng Da
>
-------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Sipp-users mailing list
> Sipp-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sipp-users
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
