Hi Paulo,

in the responses to the received initial INVITE, [last_Record-route] is 
the right keyword to use.

The keyword [route] is intended for use in requests which the SIPp 
scenario sends itself later during the dialog (call), e.g. if it would 
send the BYE itself rather than expect it from the PBX.

If you want to give a real try to the example above (an UAS scenario 
sending the BYE), note that there used to be some caveats regarding URI 
order in the route set, which had to be overcome using regexp, see 
http://yuminstallgit.blogspot.cz/2011/03/record-route-and-route-fun-in-sipp.html
 
. As a minimum, you'll need to use regexp to extract the request-uri for 
the BYE from the Contact header of the received ACK.

Pavel


Dne 8.1.2016 v 16:05 Paulo Ferreira napsal(a):
> Hi,
> I was trying to test a iPBx with a sip proxy in front of it with sipp,
> and everything was working fine except the BYE package was not arriving
> to the sipp UAS I configured. After I debug a little, I noticed that the
> sipp UAS changed the Record-Route header field, that the proxy put on
> the INVITE package, for an Route header. In the INVITE I had the
> rrs="true" and in the responses I use the [routes] Keyword as explained
> in the documentation (in there are written that the header filed should
> be Rrecord-Route).
>
> I made a quick search in the RFC and I noticed that this procedure is
> not the correct one.
>
> To test I forced Rcord-Route header filed in the sipp UAS xml file and
> it worked as expected.
>
> Anyone already experienced the same behavior as I described or did I'm
> doing something wrong?
>
> Regards,
> Paulo
>


------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to