From: Bharath M. <Bharath.Mundlapudi@Sun.COM> - 2007-12-14 16:46:28
|
Aha... I missed this attribute. Thanks. >Bharath, > >Add repeat_rtd="true" to the 200 response, and you should get the >information you need. > >Charles > >Bharath.Mundlapudi@Sun.COM wrote on 12/14/2007 04:36:37 AM: > > > >>I got the refresh working along the same lines. Thanks for the >> >> >suggestion. > > >>Now, I am seeing some issues with response time reporting. >> >>For Example: >>The following sketch does sending 100 calls and refreshes those hunderd >>calls with the given call rate in the infinate loop. I want to track the >> >> > > > >>response times for the refreshes. >> >><send> >> INVITE >></send> >> >><pause> >> >><label id="1"> >> >><send start_rtd="1" > >> INVITE >></send> >> >><recv response="200" rtd="1" /> >> >><pause next="1"> >> >>And lets say we run with -r 1 -m 100 and -d 100000 (100 sec) >> >>In the reporting, i see everything what i wanted except response times. >> >>Sipp indeed does report the response times for the first 100 >>refreshes but not the subsequent refreshes in the loop. Am i missing >>something? Or Is this not supported? >> >> >>-Bharath >> >> >> >> >>>Instead of thinking of it as repeating N calls, why can't you just use >>> >>> >the > > >>>existing call, which has all those parameters available. A brief >>> >>> >sketch: > > >>><send> >>> INVITE >>></send> >>><recv response="100" /> >>><recv response="100" /> >>><recv response="200" /> >>><send> >>> ACK >>></send> >>> >>><pause milliseconds="60000" /> <!-- give it enough time to finish >>> >>> >>the >>original calls --> >> >> >>><send> >>> REFRESH >>></send> >>> >>>If you can't do that, you can probably use the -cid_str option together >>> >>> > > > >>>with an injection file for the tags that is shared across two SIPp >>>instances. >>> >>>Charles >>> >>> >>> >>> >>>Bharath Mundlapudi <Bharath.Mundlapudi@Sun.COM> >>>Sent by: Bharath.Mundlapudi@Sun.COM >>>12/06/2007 02:22 PM >>>Please respond to >>>Bharath.Mundlapudi@Sun.COM >>> >>> >>>To >>>Charles P Wright/Watson/IBM@IBMUS >>>cc >>>sip...@li... >>>Subject >>>Re: [Sipp-users] Refresh Requests using SIPp >>> >>> >>> >>> >>> >>> >>>Comments inline... >>> >>>1. Does SIPp ( 2.1 or 3.0 version) support sending refresh requests >>> >>> >(NOT > > >>>loops)? >>>If you write the XML for it, SIPp can send any kind of SIP request. You >>> >>> > > > >>>basically need to know what the message text looks like on the wire and >>> >>> > > > >>>paste that into SIPp (or more realistically modify an existing scenario >>> >>> > > > >>>message). >>> >>> >>>2. Is it possible to do just with XML config files like if i had to >>> >>> >send > > >>>'N' calls and repeat these 'N' calls using refresh requests on same >>> >>>dialogs? >>> >>> >>>I don't know quite what you mean here. >>>The problem with the refresh requests is that they have to be in the >>> >>> >same > > >>>dialog with the from-tag, to-tag and call-id. >>>Lets say we want to send N calls using '-m N' and once SIPp makes N >>> >>> >calls > > >>>we want to send refresh requests on these N calls before they expires. >>>To do this, SIPp will have to store from-tag, to-tag and call-id for N >>>calls. I beleive it is doing in the call_maps structure. But then how >>>could we tell from the XML scripts to repeat the same N calls as a >>> >>> >refresh > > >>>request? >>> >>>-Bharath >>> >>> >>> >>> >>> > > >------------------------------------------------------------------------- >SF.Net email is sponsored by: >Check out the new SourceForge.net Marketplace. >It's the best place to buy or sell services >for just about anything Open Source. >http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace >_______________________________________________ >Sipp-users mailing list >Sip...@li... >https://lists.sourceforge.net/lists/listinfo/sipp-users > > |