I am testing a scenario where SIPp (V3.1) in the TCP transport mode (-t t1)
sends an INVITE, receives the 180/200 and sends the ACK, all through the TCP
connection opened for the call. Once the call is established, the far end
opens a new TCP connection to send a REFER request. Although not recommended
by rfc 3261 (18.8.1), it does allow the client to open a new TCP connection
to send a request. However, SIPp is sending the 202 Accepted using the
previous connection (the one opened for the INVITE), thus violation rfc 3261
(18.2.2), which states that
If the “sent-protocol” is a reliable transport protocol such as TCP or
SCTP, or TLS over those, the response MUST be sent using the existing
connection to the source of the original request that created the
transaction, if that connection is still open.
Is there any way (at the command line or other level) to ensure that SIPp
send the response using the same TCP connection through which the request
was received?
Thanks,
Ricardo
################################################################
Ricardo C. Mastroleo
Interact Incorporated http://www.iivip.com
9390 Research Blvd. Bldg. II Suite 100
Austin, TX 78759
(512) 502-9969 Ext. 112 (512) 502-1157 (Fax)
[EMAIL PROTECTED] http://home.worldnet.att.net/~mastrolr
################################################################
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
