From: Bhaskar D. <bha...@gl...> - 2009-02-24 12:17:16
|
The conntrack layer seems to have kicked in here. It assigns ports starting from 1024 since two conntrack entries cannot have the same tuples. Please check netstat output and conntrack dump and you will probably see the old TCP connection still in TIME_WAIT2 state. Bhaskar Dutta | Lead, Engineering | GlobalLogic Inc. The Global Product Development Leader USA | INDIA | UKRAINE | CHINA Office: +91-120-406-2924 | Fax: +91-120-258-5721 www.globallogic.com InfoWorld Award Winner for Agile Innovation Disclaimer: http://www.globallogic.com/email_disclaimer.txt -----Original Message----- From: Andrew Wood [mailto:aj...@ie...] Sent: Tue 2/24/2009 4:58 PM To: sip...@li... Subject: [Sipp-users] -p option being ignored Bhaskar Dutta | Lead, Engineering | GlobalLogic Inc. The Global Product Development Leader USA | INDIA | UKRAINE | CHINA Office: +91-120-406-2924 | Fax: +91-120-258-5721 www.globallogic.com InfoWorld Award Winner for Agile Innovation Disclaimer: http://www.globallogic.com/email_disclaimer.txt -----Original Message----- From: Andrew Wood [mailto:aj...@ie...] Sent: Tue 2/24/2009 4:58 PM To: sip...@li... Subject: [Sipp-users] -p option being ignored Is there a reason why the following command to generate calls is using local port 1026 instead of 5061 which is what i would expect? ./sipp 192.168.254.254:5060 -r 1 -rp 1000 -d 10000 -timeout 5s -s 211 -sf ./uac.sipp.xml -i 192.168.254.201 -p 5061 -t un |