Hi Oliver,
I have install new version and seems to work fine,
Thanks,
Jev.
On 11/5/07, Jeverson Deggerone <[EMAIL PROTECTED]> wrote:
>
> Hi Oliver,
>
> My apologies to replay only to you
>
> My current version is SIPp v2.0.1-TLS, version 20070516, built Oct 31
> 2007, 11:52:47. I will download the latest one.
>
>
>
> i have also tried to run with 2 instance but it is not really what i want,
> because sipp just start answer notify's after the first instance has
> finished
>
> sipp -inf /tmp/sipp_xml/teste.csv -sf /tmp/sipp_xml/registro1.xml
> remote_host 172.30.57.102 -i 172.30.13.105 -r 10 -t u1 && sipp -
> sipp_xml/notify -t u1
>
>
> Best Regards,
>
> Jeverson Deggerone
>
>
>
> On 11/5/07, Boulkroune, Olivier (Non-HP:Atos Origin) <
> [EMAIL PROTECTED]> wrote:
> >
> > Did you try with the latest trunk version ? This should work (a fix
> > concerning this had been committed).
> >
> >
> >
> > Don't forget to cc to sipp-users when replying.
> >
> >
> >
> > Regards,
> >
> >
> >
> > Olivier Boulkroune
> >
> >
> > ------------------------------
> >
> > *De :* Jeverson Deggerone [mailto: [EMAIL PROTECTED]
> > *Envoyé :* lundi 5 novembre 2007 17:20
> > *À :* Boulkroune, Olivier (Non-HP:Atos Origin)
> > *Objet :* Re: [Sipp-users] Registration scenario.
> >
> >
> >
> > Hi Oliver,
> >
> >
> >
> > It does not work because our sip application server create the NOTIFY
> > with new call-id.
> >
> >
> >
> > Best Regards,
> >
> >
> >
> > On 11/2/07, *Boulkroune, Olivier (Non-HP:Atos Origin)* <[EMAIL PROTECTED]>
> > wrote:
> >
> > Hi,
> >
> >
> >
> > This should work with the –aa option.
> >
> >
> >
> > Olivier Boulkroune
> >
> >
> > ------------------------------
> >
> > *De :* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > ] *De la part de* Jeverson Deggerone
> > *Envoyé :* jeudi 1 novembre 2007 13:14
> > *À :* [email protected]
> > *Objet :* [Sipp-users] Registration scenario.
> >
> >
> >
> > Hi,
> >
> >
> >
> > I am trying to setup a registration scenario but our sip
> > application server does send a notify after the registration steps has been
> > finish, but sipp is unable to recognize the notify because our sip server is
> > not totally complaint according RFC. Is there any way to workaround it? I
> > want sipp answer 200 ok in any case even if the notify is not RFC complaint.
> >
> >
> >
> >
> >
> >
> >
> >
> > ------------------------------ Scenario Screen -------- [1-9]: Change
> > Screen --
> > Call-rate(length) Port Total-time Total-calls Remote-host
> > 1.0(0 ms)/1.000s 5060 7.70 s 1
> > 172.30.57.102:5060(UDP)
> >
> > Call limit reached (-m 1), 0.695 s period 4 ms scheduler resolution
> > 1 calls (limit 1) Peak was 1 calls, after 1 s
> > 0 Running, 1 Paused, 0 Woken up
> > 4 out-of-call msg (discarded)
> > 1 open sockets
> >
> > Messages Retrans Timeout
> > Unexpected-Msg
> > REGISTER ----------> 1 0 0
> > 401 <---------- 1 0 0
> > REGISTER ----------> 1 0 0
> > 200 <---------- 1 0 0
> > NOTIFY <---------- 0 0 0
> > 200 ----------> 0 0 0
> > ------------------------------ Test Terminated
> > --------------------------------
> >
> >
> > ----------------------------- Statistics Screen ------- [1-9]: Change
> > Screen --
> > Start Time | 2007-11-01 13:00:20
> > Last Reset Time | 2007-11-01 13:00:27
> > Current Time | 2007-11-01 13:00:28
> >
> > -------------------------+---------------------------+--------------------------
> > Counter Name | Periodic value | Cumulative value
> > -------------------------+---------------------------+--------------------------
> >
> > Elapsed Time | 00:00:00:698 | 00:00:07:758
> > Call Rate | 0.000 cps | 0.129 cps
> > -------------------------+---------------------------+--------------------------
> >
> > Incoming call created | 0 | 0
> > OutGoing call created | 0 | 1
> > Total Call created | | 1
> > Current Call | 1 |
> >
> > -------------------------+---------------------------+--------------------------
> > Successful call | 0 | 0
> > Failed call | 0 | 0
> >
> > -------------------------+---------------------------+--------------------------
> > Call Length | 00:00:00:000 | 00:00:00:000
> > ------------------------------ Test Terminated
> > --------------------------------
> >
> > 2007-11-01 13:00:25: Discarding message which can't be mapped to a known
> > SIPp call:
> > NOTIFY sip:[EMAIL PROTECTED] SIP/2.0
> > From: < sip:[EMAIL PROTECTED]>
> > To: < sip:[EMAIL PROTECTED]>
> > Via: SIP/2.0/UDP 172.30.57.102:5060
> > Max-Forwards: 70
> > CSeq: 2173 NOTIFY
> > Allow: REGISTER, INVITE, ACK, BYE, CANCEL, NOTIFY, REFER
> > Contact: <sip:[EMAIL PROTECTED]:5060>
> > Call-ID: 8148193911-95937732293911-11-9215663022
> > Event: message-summary
> > Subscription-State:active
> > Content-Type: application/simple-message-summary
> > Content-Length: 24
> >
> >
> >
> > please find bellow
> >
> > --
> > Jeverson Deggerone
> >
> >
> >
> >
> > --
> > Jeverson Deggerone
> >
>
>
>
> --
> Jeverson Deggerone
--
Jeverson Deggerone
-------------------------------------------------------------------------
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
