Hi Stephen,
Yes I am sure it reaches directly from UAS to UAC.
Anyway I have found the solution. I have used the mechanism sipp
provides to change the original destination to Contact of last message.
In UAS.xml, after receiving BYE, I have included these lines:
<nop>
<action>
<assignstr assign_to="url" value="[next_url]" />
<ereg regexp="sip:.*@([0-9A-Za-z\.]+):([0-9]+)" search_in="var"
check_it="true" assign_to="dummy,host,port" variable="url" />
<log message="BYE receiced from: host=[$host] port=[$port]" />
<setdest host="[$host]" port="[$port]" protocol="UDP" />
</action>
</nop>
In fact, this is the same mechanism I used in UAC.xml after receiving
200 OK (INVITE transaction) to redirect ACK and BYE directly fom UAC to
UAS, bypassing original destination (proxy)
I did not noticed initially this mechanism was valid for sending 200 Ok
(BYE transaction)
Thanks anyway.
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
