We have been using Freeswitch as our SBC and core switch for many years without issues. Recently we added public facing softphones using an additional server running Kamailio as TLS and webrtc bridge with FS handling media back to our core FS farm. We run a mix of webrtc and Zoiper softphones. All running SIPS (tls) but webrtc is SRTP (PCMU) and Zoiper is RTP (PCMU). We have been ramping up the webrtc traffic and at some magic point at busy times (~150 concurrent calls) the RTT and Packet loss for the webrtc calls goes crazy (as measured in the browser via RTCP and captured back on our logging servers). RTT jumps from 100ms to 2-3 seconds for most or all webrtc users and packet loss jumps from nothing to troubling on the Sending side back to FS only. Packets received are not an issue on webrtc side... webrtc can hear end caller, but end caller cannot hear webrtc well. Non webrtc traffic (Zoiper) have no reported impact. Server CPU (dual socket 6 core) looks great (no core over 20%) according to nmon... packets per second within reason (10Gb NICs). I am assuming the SRTP has some hidden scaling issue since this is the only difference between the two types of softphones. Has anyone seen this or have a workaround? I am at a loss. I assume if it is encryption overhead the CPU would be saturated and it is not. Why a single direction of SRTP traffic is impacted has me up late at night. A side note... does anyone know of a SIPP replacement that does SRTP so I can test load against this to isolate? Thanks, Matthew Meek