Hello guys
We setup a new PBX, we do fail2ban and only SIP and RTP ports open to the internet as it has external etc.
We are seing this on the reports.
2012-12-30 11:01:09 5550000 sSIP/5060-099e8590 ANSWERED 0s
2012-12-30 07:52:38 smallgw sSIP/5060-099e8590 ANSWERED 1s
over and over sometimes its 5550000, smallgq, then 101, then 1001, etc.
We show "stuck" channels with sip show peers, but no activity on dahdi, (this pbx does not have SIP trunks)
Is it an attack?
Is elastix ever going to be secure? Its a yum updated 1.6-XX version
all pointers and ideas are welcomed.
We setup a new PBX, we do fail2ban and only SIP and RTP ports open to the internet as it has external etc.
We are seing this on the reports.
2012-12-30 11:01:09 5550000 sSIP/5060-099e8590 ANSWERED 0s
2012-12-30 07:52:38 smallgw sSIP/5060-099e8590 ANSWERED 1s
over and over sometimes its 5550000, smallgq, then 101, then 1001, etc.
We show "stuck" channels with sip show peers, but no activity on dahdi, (this pbx does not have SIP trunks)
Is it an attack?
Is elastix ever going to be secure? Its a yum updated 1.6-XX version
all pointers and ideas are welcomed.
