blanchae
Guru
- Joined
- Mar 12, 2008
- Messages
- 1,910
- Reaction score
- 9
I'm playing around with SIPp and its various support programs such as SIPGUI and WebFrontEnd. Interestingly, Ubuntu installs SIPp V3.1 under the name sip-tester. You can play around with it but really need the WebFrontEnd GUI to control it. SIPp is a command line tool.
I'm thinking of testing along these lines:
1. Stress test the PBX's hardware capacity by testing directly across the LAN. First testing using a dedicated SIP trunk then using multiple clients with their own IP addresses.
2. Stress test the incoming bandwidth by going across the Internet.
Another option is to use two Cisco routers connected together via a serial link and test by lowering the clock rate (bandwidth) between them.
3. Also I should be able to select the codecs used and stress for the PBXs ability with different codec plus transcoding.
Any suggestions? Or comments?
I've tried V3.2 but couldn't get it working properly. V3.1 seems to be rock stable. These are Unix versions. There is a V3.1 for Windows which works well - (couldn't get V3.2 to work either). The Windows version maxs out on my laptop at 80 calls per sec, after that the program crashes. The docs recommend using Linux for high rates in the 10,000 calls per min range.
They also have an IMS version which seems more developed for testing to TIA standards but it requires some recompiling of the kernel and other issues.
I'm thinking of testing along these lines:
1. Stress test the PBX's hardware capacity by testing directly across the LAN. First testing using a dedicated SIP trunk then using multiple clients with their own IP addresses.
2. Stress test the incoming bandwidth by going across the Internet.
Another option is to use two Cisco routers connected together via a serial link and test by lowering the clock rate (bandwidth) between them.
3. Also I should be able to select the codecs used and stress for the PBXs ability with different codec plus transcoding.
Any suggestions? Or comments?
I've tried V3.2 but couldn't get it working properly. V3.1 seems to be rock stable. These are Unix versions. There is a V3.1 for Windows which works well - (couldn't get V3.2 to work either). The Windows version maxs out on my laptop at 80 calls per sec, after that the program crashes. The docs recommend using Linux for high rates in the 10,000 calls per min range.
They also have an IMS version which seems more developed for testing to TIA standards but it requires some recompiling of the kernel and other issues.