This has a whole lot more to do with interconnect agreements than how many CAPS one solution can send versus another. Frankly any old piece of SIP gear has the potential to send more CAPS than your average provider would expect to receive. Many telcos, especially tier one's will establish an upper limit on the number of attempts per second that any interconnect can initiate, for example BT in the UK limit it to one CAPS per 30 channels approximately. It's not fair to allow one customer to use the whole available capacity at the expense of other customers. We're forever clamping customers because their rubbish dialler software has no understanding of a 503 with Retry-After response and have gone to lengths to automate this to protect our network, as even FS can get crippled by a device which relentlessly initiates call after call (in some cases we've seen well over 100 CAPS from a single device). So when we detect a killer trunk we'll raise a critical event in the FS logs and use Fail2Ban to ignore requests from the customer's IP. -- View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Kudos-to-the-FreSWITCH-team-tp... Sent from the freeswitch-users mailing list archive at Nabble.com.