Santiago Gimeno wrote: > Hello, > > I'm using sipp as a subscriber: it sends SUBSCRIBE's to a server and > receives NOTIFY's from the server. The transport used is TCP. > In a typical scenario I will have two tcp connections: > - Connection 1: One ongoing connection from the sipp-subscriber > through which SUBSCRIBE's are sent to the server and responses to > these SUBSCRIBE's are received. (1) > - Connection 2: One incoming connection from the server to the > sipp-subscriber port I put in the Contact header of the SUBSCRIBE, > through which NOTIFY's are received from the server and responses to > these NOTIFYS's are sent. (2) > > I have noticed that if the Server closes the Connection 1, the > sipp-subscriber starts sending SUBSCRIBE through the Connection 2. Is > this the expected behaviour?? > > Best regards > > Santi > ------------------------------------------------------------------------ SIPp doesn't have a fine grained control over TCP connections. You have currently those possibilities: - One TCP socket is created for each new execution of a scenario and closed at the end of it (-t tn) - One TCP socket is created at the beginning of the traffic and re-used all the time (-t t1) - Same as -t tn, but limiting the number of sockets that are used simultaneously (-max_socket option)
Hope this helps. -- Olivier HP OpenCall Software http://www.hp.com/go/opencall/ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
