Hi Sindelka,
yes you understood perfectly.
I will start to read message suggested.
thanks
Marco
2017-11-08 18:09 GMT+01:00 Šindelka Pavel <sinde...@ttc.cz>:
> Not sure I got what you mean by "across", English is not my native
> language. If you have in mind that A and B are both local subscribers of
> CUCM and the call between them has to pass through CUCM, then to do this,
> you need much more complex scenarios than the embedded ones. In particular
> you need that both register in one thread (a "call" in SIPp terminology),
> and then A them initiates a session in another thread, while B is ready to
> accept it.
>
> If this is the case: to implement this, you need conditional execution at
> UAC side (to take a different branch of the scenario depending on call
> number) and an auxiliary timer instance of SIPp at the UAS side, as the UAS
> needs to receive an impulse from outside to start a thread. So while the
> INVITE-awaiting branch of the scenario is a regular one, the
> REGISTER-sending one is triggered by receiving a SIPp inter-instance
> command.
>
> I have described this here in deeper detail several times in the past.
> Maybe you could start from this message
> <https://sourceforge.net/p/sipp/mailman/message/34707334/>.
>
> If it is not the case, e.g. if A or B or both are trunk peers, please
> provide a rough flow diagram of what your scenario should look like,
> similar to the following one, and indicate which elements should be
> replaced by SIPp scenarios and whether they are trunk peers or registering
> subscribers. And consider whether we should continue on the mailing list or
> whether to move away from there.
>
> A proxy B
> |--- INVITE --->| |
> | |--- INVITE --->|
> : : :
> | |<--- 200 ------|
> |<--- 200 ------| |
> : : :
> |------------- ACK ------------>|
> : : :
> P.
>
> Dne 8.11.2017 v 17:47 Marco Menozzi napsal(a):
>
> Have you ever tried across a Cisco CUCM ?
>
> Marco
>
> 2017-11-08 17:23 GMT+01:00 Šindelka Pavel <sinde...@ttc.cz>:
>
>> Yes, provided that you bind each instance to a different port on the
>> loopback interface (127.0.0.1). This is relevant for UDP, for TCP the
>> client will choose an ephemeral port for establishing connection so it
>> won't conflict, but there are other caveats.
>>
>> Pavel Šindelka
>>
>> Dne 8. 11. 2017 5:18 odpoledne napsal uživatel Marco Menozzi <
>> mmenozz...@gmail.com>:
>>
>> Understood.
>>
>> Is it possible to perform it running uac.xml and uas.xml from same laptop
>> ?
>>
>> Marco
>>
>> 2017-11-08 17:17 GMT+01:00 Šindelka Pavel <sinde...@ttc.cz>:
>>
>> In your scenario, sipp running uas.xml replaces the B party and sipp
>> running uac.xml replaces the A party.
>>
>> Depending on which of the parties you want to simulate or whether you
>> want to simulate both, you need to run one or two instances of sipp and to
>> choose the uas /uac behaviour for it/them.
>>
>> The embedded uac.xml will not send the BYE to an IP address extracted
>> from any uri received in a response unless you explicitly tell it to do so
>> and point it to a particular uri from which it should extract the address.
>> Similarly, the embedded uas scenario will send the response to BYE to the
>> same IP from which it has got the initial INVITE, even if the BYE comes
>> from another one, unless you explicitly ask it to do do.
>>
>> Omlouvám se za stručnost, píšu z mobilu.
>>
>> Pavel Šindelka
>>
>> Dne 8. 11. 2017 4:49 odpoledne napsal uživatel Marco Menozzi <
>> mmenozz...@gmail.com>:
>>
>> Hi
>>
>> thanks for your feedback.
>>
>> the purpose is to reproduce a situation where
>>
>> A calls B
>>
>> B answer to A without Contact Header and with Record Route set.
>>
>> My questions is: would it be enough to use uas.xml script to reproduce
>> the above or I need to also trigger a uac.xml too ?
>>
>> Marco
>>
>> 2017-11-08 16:29 GMT+01:00 Šindelka Pavel <sinde...@ttc.cz>:
>>
>> Can you be more specific regarding for which of the following steps you
>> need assistance?
>>
>> 1) run the sipp binary with a single command line parameter -sd uas ,
>> thus asking it to dump the embedded uas.xml to stdout while redirecting
>> stdout to file my_uas.xml:
>>
>> sipp -sd uas > my_uas.xml
>>
>> 2) edit my_uas.xml the required way (remove Contact:.., add
>> Record-Route:...)
>>
>> 3) run sipp with all the command line parameters you use normally plus -sf
>> my_uas.xml , thus telling it to run your modified UAS scenario rather
>> than the embedded one
>>
>> ?
>> P.
>>
>> Dne 7.11.2017 v 13:15 Marco Menozzi napsal(a):
>>
>> Hi
>>
>> sorry but I'm pretty new with scripting with this tool.
>>
>> I would need to reproduce a scenario where sipp is used to answer a phone
>> call, removing Contact Header and adding a Record Route field with option
>> "lr" (loose routing).
>>
>> A calls B (sipp) . B answers with 180 ringing without Contact Header and
>> adding Record Route .
>>
>> I thought to manipulate uas.xml script to perform that but I don't know
>> how to perform the action above.
>>
>> thanks
>>
>> cheers
>> Marco
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>>
>>
>> _______________________________________________
>> Sipp-users mailing
>> listSipp-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/sipp-users
>>
>>
>>
>> ------------------------------------------------------------
>> ------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Sipp-users mailing list
>> Sipp-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/sipp-users
>>
>>
>>
>>
>>
>>
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
