Hi Jason,

The embedded UAS script (-sn uas) does not perform registration (
http://sipp.sourceforge.net/doc/reference.html).

Even if you write your own script to perform registration and expect an
INVITE it will not be able to do both because the first request is outgoing
SIPp infers the mode as UAC.

The following should work unless you will use tcp or tls as transport:


   - Implement a registration script that will only send register. reply to
   authorization challenge and re-attempt.
   - Then run a UAS script (perhaps the embedded one) after the
   registration script is completed making sure that:
      - You bind to the same port recorded as your contact during
      registration.
      - You use the Contact header provided during registration.

You will have to do some logging, parsing if you are behind a NAT but the
way you describe your topology you will not need it.

Regards,
-volkan

On Fri, Jun 5, 2015 at 6:57 PM, Jason Spriggs <jsksw...@gmail.com> wrote:

> Hello SIPp Users,
>
> I have been running into an issue while trying to create a load tester
> using SIPp. Here is our setup:
>
> We have 2 boxes running asterisk and sipp and would like to do a load test
> of our custom tunnel plugin/module. The boxes are located on our network at
> 10.1.1.1 (Box 1) and 10.1.1.2 (Box 2). We initiate the calls from Box 2
> using the UAC built in scenario via the command:
>
> sipp 127.0.0.1 -i 10.1.1.2 -p 8832 -sn uac -l 1 -m 100 -r 1 -s 633
>
> The call is directed through our custom tunnel and ends up at Box 1. The
> dial plan then dials the SIP phone, "sipp".
>
> The issue we are running into is that the UAS server, ran via the command
> "sipp 127.0.0.1:5060 -i 10.1.1.1 -p 8823 -sn uas -au sipp -ap test -s
> sipp", will not register itself as the "sipp" sip phone on Box 1. The
> configuration files in asterisk are correct, and we have tested this by
> connecting a softphone up to the same "sipp" user, and it works.
>
> If anyone is able to help point out what in my UAS server initializer
> command is incorrect, that would be much appreciated.
>
> Many thanks,
> Jason
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Sipp-users mailing list
> Sipp-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/sipp-users
>
>
------------------------------------------------------------------------------
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to