From: <mar...@be...> - 2007-12-12 10:52:01
|
Hello all, a bug report, no (time for) fix yet: I just plugged in sipp version 3.0 (2.0 of 20071128;-) into my register load script, and noticed that the [local_port] in the SIP message becomes 0 instead of the port number when sipp starts to reuse the UDP socket. I don't have time now to dig deeper in the code, but the version dated 20071026 didn't have it yet. Some more info: I'm running a thousand simultaneous registration sessions with "-t un -max_socket 335", so trying to use each socket around 3 times. The first 334 sessions run fine, from then on, sipp starts reusing the UDP sockets but the [local_port] in the via and contact headers are "0" instead of the port number. A small test with max_socket=3D3 has two correct sessions, the third = goes wrong.=20 Same conclusion with max-socket=3D4: he cycles through max_socket-1 sockets, and substitution fails after the first round. Best regards, MarcVD (-: from Marc VAN DIEST (BELGACOM) ;-) |