Bugs item #1592593, was opened at 2006-11-08 12:09 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=637564&aid=1592593&group_id=104305
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Scenarios Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Steve (stevebaldwin) Assigned to: Nobody/Anonymous (nobody) Summary: Generated call-id is not unique enough Initial Comment: The call-id generated by SIPp is based on the process- id of the SIPp executable, as well as the IP addres of the host. Over time, if multiple SIPp executables are run (in sequence) on the same host, then a call-id may be re- used in the case that a process-id is re-used between SIPp instances. In certain scenarios this can cause a SIP 482 Loop Detected response to be sent back to the SIPp instance which re-uses the process-id, and hence call- id. The generation of call-id should use a more unique method for call-id generation to prevent re-use of call-ids. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=637564&aid=1592593&group_id=104305 ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
