I have an interesting issue with multi-socket. Using a scenario to simulate a presence endpoint. It sends a register, subscribe and publish, and that SUBSCRIBE results in a NOTIFY for his state information. So I have essentially:
<send> REGISTER <recv response="200"> <send> PUBLISH <recv response="200"> <send> SUBSCRIBE <recv response="200"> <recv request="NOTIFY"> <send> 200 OK The issue is, I believe, that the <recv request> command tells SIPp to open up a server socket and listen on 5060 for the response - correctly so. But when using multi-socket (-tn) the second call attempts to do the same, and fails out with a ' Unable to connect a TCP socket, errno = 111 (Connection refused)' error, cause the first one still has it open. (incidentally - same issue with using -aa with a uac) Does anyone have a suggestion/patch on how to address this? I assume we can add some code, or a switch, to tell it to use multi-socket for sends, but nail up the 5060 listen socket and re-use it, but I am woefully unfamiliar with SIPp socket code. It all looks like spaghetti to me ;) t ------------------------------------------------------------------------- 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
