On 28/05/14 19:04, Alejandro Galasso wrote: > Hi All > > This is the first time I am using SIPP (version 3.4.1) and I like to > make an stress test to a lab equipment. I have a problem that is as > follows: > > 1. Client send first INVITE and get 407. > 2. After that, client send second INVITE(cseq=2) With proper credentials > 3. After that Call is established between the endpoints. > 4. Even though the call has been established, the client always > receives 407 (from cseq=1) > From looking at the Wireshark trace you attached, your ACK has a different branch parameter from the INVITE and 407 - and so therefore the peer is presumably not recognising that transaction as acknowledged and retransmitting the 407.
RFC 3261, 17.1.1.3 <http://tools.ietf.org/html/rfc3261#section-17.1.1.3> "Construction of the ACK Request", says "The ACK MUST contain a single Via header field, and this MUST be equal to the top Via header field of the original request." (Note that this section only applies to non-2xx responses.) Best, Rob ------------------------------------------------------------------------------ Time is money. Stop wasting it! Get your web API in 5 minutes. www.restlet.com/download http://p.sf.net/sfu/restlet _______________________________________________ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users