Thanks for the input Tony. > you should rate limit at your firewall the cps (connections per second).
This came up a while back. I'll take another look at this firewall, might have overlooked this. Other than the cps setting, since sipx seems to be fine otherwise, there should be no need to raise the RTP ports right? Mike > There are also voip-abuse and other blacklists your firewall might be able > to employ to curtail access to the system. > > in the meantime the setting you are seeking is in: system>servers> yours> > nat (advanced). Just remember to also increase the range in the firewall > too. > > On Sat, Dec 24, 2011 at 12:40 PM, [email protected] <[email protected]> > wrote: > >> Someone was hacking away at my system again trying to usable accounts, >> which they didn't. >> > However, the following error showed up which I've not seen before. > The error suggests a fix but is it needed for normal use or is the fix for > a highly busy server that would get lot's of hits similar to an attack. > > Mike > > > Message from sipXecs > Alarm: SPX00028 > Reported on: uc.mydomain.com > Reported at: 2011-12-24T09:21:21.142855Z > Severity: CRIT > Alarm Text: SipXproxy could not allocate the Media Relay Session required > for a call likely resulting in speech path issues. > Suggested Resolution: Not enough RTP ports are allocated to the Media > Relay. Increase the RTP port range allocated to the Media Relay using > sipXconfig (under System->Servers->(click on server)->NAT->Show Advanced > Settings > >> _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
