Thanks. It works.

Zheng Da

On 8/24/07, Peter Higginson <[EMAIL PROTECTED]> wrote:
>
>  You don't really need a timeout at all in your script, but you do need a
> second next. This should do:
>
>
>
> <send retans="500">
>
>     …BYE..
>
>
>
> <recv request="BYE" optional="true" next="1">
>
>    …..
>
>
> <recv response="200" next="2"/>
>
> <label id="1"/>
>
> <send>
>
>   …..
>
>  <label id="2"/>
>
>
>
> You would only use timeout if you wanted to wait for a bit to see if a BYE
> arrived before deciding whether to send one. In that case you would have
> something like:
>
>
>
> <recv request="BYE" timeout="10000" ontimeout="1">
>
>    …..
>
>
>
> <send next="3">
>
>   …200 OK..
>
>  <label id="1"/>
>
>
>
> <send retans="500">
>
>     …BYE..
>
>
>
> <recv request="BYE" optional="true" next="2">
>
>    …..
>
>
> <recv response="200" next="3"/>
>
> <label id="2"/>
>
> <send>
>
>   …200OK..
>
>  <label id="3"/>
>
>  Both of them get more complex if you want to allow for a response
> (potentially not 200) to your BYE as well.
>
>
>
> I'm sorry I cannot answer the "which version" part of your question – I
> submitted the features but have never re-synced to the public version.
>
>
>
> Peter Higginson
>
> Newport Networks Ltd,
>
> http://www.newport-networks.com/
>   ------------------------------
>
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Zheng Da
> *Sent:* 24 August 2007 09:40
> *To:* Peter Higginson
> *Cc:* [email protected]
> *Subject:* Re: [Sipp-users] How to use sipp to deal with the following
> case?
>
>
>
> I didn't see timeout option in sipp v2.0 reference document.
> Which version are you talking about?
> I write it as follow, but it doesn't work as I expect.
>
>   <send retrans="500">
>     <![CDATA[
>
>       BYE sip:[EMAIL PROTECTED]:[$2] SIP/2.0
>       Via: SIP/2.0/[transport] [local_ip]:[local_port];branch
>
> =[branch]
>       From: sipp <sip:[EMAIL PROTECTED]>;tag=[call_number]
>       To: sut <sip:[EMAIL PROTECTED]>[peer_tag_param]
>       Call-ID: [call_id]
>       CSeq: 2 BYE
>       Contact: sip:[EMAIL PROTECTED]:[local_port]
>       Max-Forwards: 70
>       Subject: Performance Test
>       Content-Length: 0
>
>     ]]>
>   </send>
>
>   <recv request="BYE" optional="true" timeout="10000" next="1">
>     <action>
>       <ereg regexp="[0-9]+ +BYE" search_in="hdr" header="CSeq:"
> assign_to="6" />
>     </action>
>   </recv>
>
>   <recv response="200"/>
>
>   <label id="1"/>
>
>   <send>
>     <![CDATA[
>
>       SIP/2.0 200 OK byebye
>       [last_Via:]
>       [last_From:]
>       [last_To:]
>       [last_Call-ID:]
>       CSeq: [$6]
>       Contact: <sip:[local_ip]:[local_port];transport=[transport]>
>       Content-Length: 0
>
>     ]]>
>   </send>
>
> Zheng Da
>
>
>
> On 8/23/07, *Peter Higginson* <[EMAIL PROTECTED] >
> wrote:
>
> Yes there is a timeout option on receive (and optional receive – you need
> to set both) and using both of them I'm sure you can do what you want.
>
>
>
> Peter Higginson
>
> Newport Networks Ltd
>
> http://www.newport-networks.com/
>   ------------------------------
>
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Zheng Da
> *Sent:* 23 August 2007 15:49
> *To:* [email protected]
> *Subject:* [Sipp-users] How to use sipp to deal with the following case?
>
>
>
> 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 e-mail may contain confidential and/or privileged information.
>
> If you are not the intended recipient (or have received this e-mail in error) 
> please
>
> notify the sender immediately and delete this e-mail. Any unauthorized 
> copying,
>
> disclosure or distribution of the contents in this e-mail is strictly 
> forbidden.
>
> ---------------------------------------------------------------------------------------------
>
> Newport Networks Limited is registered in England. Registration number 
> 4067591.
> Registered office: 6 St. Andrew Street, London EC4A 3LX
>
> ---------------------------------------------------------------------------------------------
>
>
>
>
> ------------------------------
>
> ---------------------------------------------------------------------------------------------
> This e-mail may contain confidential and/or privileged information.
>
> If you are not the intended recipient (or have received this e-mail in error) 
> please
>
> notify the sender immediately and delete this e-mail. Any unauthorized 
> copying,
>
> disclosure or distribution of the contents in this e-mail is strictly 
> forbidden.
>
> ---------------------------------------------------------------------------------------------
>
> Newport Networks Limited is registered in England. Registration number 
> 4067591.
> Registered office: 6 St. Andrew Street, London EC4A 3LX
>
> ---------------------------------------------------------------------------------------------
>
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to