[Sipp-users] Unstable release for sipp 3.1 win32 with authentication!

Hello, For the benefit of users, I have put a version of sipp 3.1 for win32 compiled with ossl support on sourceforge. Though all the new authentication features added after 3.0 may not yet be tested fully for win32, so its still unstable. You can download it from following link:

Re: [Sipp-users] How to accept SIP calls generated by SIPp tool

Hi, I'm not sure what your application is intended to do, but I think it should send 200 OK response to accept a call (and then be ready to receive subsequents requests and respond to them). If you want just to talk between two sipp's running on two computers, run the calling one with uac

[Sipp-users] AKAv1-MD5

Consider the following scenario ... scenario name=AKAv1-MD5_BASIC recv request=REGISTER /recv send ![CDATA[ SIP/2.0 401 Unauthorized [last_Via:] [last_From:] [last_To:];tag=[call_number] [last_Call-ID:] [last_CSeq:] Max-Forwards: 70 WWW-Authenticate: Digest

Re: [Sipp-users] AKAv1-MD5

Sorry for my previous incomplete mail Consider the following scenario ... in this scenario, how can i actually verify if the peer has sent the correct response in Authorization field? in the second REGISTER ? scenario name=AKAv1-MD5_BASIC recv request=REGISTER /recv send ![CDATA[ SIP/2.0

Re: [Sipp-users] AKAv1-MD5

You'll need a recent SIPp trunk version and to use the verifyauth action. It looks something like recv request=REGISTER / verifyauth assign_to=goodauth username=username password=password / /recv username and password can be any message substitution, and you can do branching based on

[Sipp-users] Variable $5 is referenced 1 times!

Hi, I'm trying to find the contact uri from a 200 OK response sent by the UAC, but sipp apparently isn't happy about the scenario file syntax. I keep getting this error: Variable $5 is referenced 1 times! is this correct? recv response=200 rtd=true rrs=true action ereg

Re: [Sipp-users] Variable $5 is referenced 1 times!

Hi, It's probably about an unused vatiable. I had this error in sipp 3.1 when I extracted something with ereg, but never used the variable. It is strange, because it should rather say that it's referenced 0 times. The error goes away if you use every extracted variable somewhere in the

Re: [Sipp-users] Variable $5 is referenced 1 times!

The only referenced once check is there to prevent typos and other similar errors that would have SIPp load a scenario with a variable only used once (the theory being why do you need to read or write to a variable if you never read or write from it again, basically like an unused variable